- Telling Stories and User Role Modeling
- May 21, 2004
- Agile software development is based on "telling stories." In this sample chapter, you'll learn about user roles, role modeling, user role maps, and personas. You'll also find out how taking these initial steps leads to better stories and better software.
|
- Agile Software Management Accounting for Systems
- Feb 20, 2004
- Throughput Accounting can be generally applied for the management, control, and reporting of any system. Throughput Accounting is appropriate for managing general systems because it focuses on Throughput, which is the desired adaptive behavior of the system.
|
- Agile Management for Software Engineering: Dealing with Uncertainty
- Jan 30, 2004
- There are five main constraints in software development management people, time, functionality, budget, and resources which all must be protected from uncertainty. Uncertainty manifests itself when the unplanned happens. David J. Anderson explains how a system can absorb uncertainty with the provision of buffers, and how and when these buffers should be used.
|
- Software Development: Iterative & Evolutionary
- Jan 9, 2004
- Iterative and evolutionary development is a foundation not only of modern software methods, but of methods used as far back as the 1960s. Agile methods are a subset of iterative and evolutionary methods. This chapter summarizes key practices of iterative and evolutionary software development.
|
- Keys to Successful Venture Capital Investing: Due Diligence
- Dec 23, 2003
- This chapter starts the beginning of what venture capitalists (VCs) call the due diligence process. That is, it describes the steps that an investor should take in researching an investment opportunity. This is a detailed process that takes weeks—sometimes months—of work. It begins when an investor is confronted with a business proposal and must decide whether the idea warrants further investigation.
|
- Software Development: Agile vs. Disciplined Methods
- Oct 24, 2003
- So what does it feel like to develop software according to plan-driven or agile methods? In this chapter we try to portray the activities in a typical day on a software development project as performed by a plan-driven, PSP/TSP-trained team and by an agile, XP-trained team.
|
- Keeping the Code Clean
- Sep 19, 2003
- Is your kitchen a wreck? Your code probably is, too. "Uncle Bob" Martin explains why it's a bad idea to leave last week's "code spaghetti" drying on the dishes for cleanup later.
|
- Agile Modeling
- Jan 3, 2003
- Modeling and design skills still have a part to play in the XP world. The difference is that tools and models become simpler and more dynamic. Learn how to use your modeling skills in an Agile way.
|
- art_gore_outsourcing
- Jan 1, 2003
|
- Which Agile Methodology Should You Use?
- Nov 22, 2002
- At last you have decided that agile methodologies are worth a try, and now you are looking for the right methodology to introduce in a pilot project at your firm. Which one should you use?
|
- Agile Development: Weed or Wildflower?
- Aug 30, 2002
- Despite outward appearances, agile development doesn't mean a return to the days of the cowboy programmer. Learn how agile methods can be implemented in a manner that satisfies the CMM-SW or the CMMI.
|
- The Principles of Extreme Programming
- Apr 5, 2002
- The XP solution is simple: Stay flexible, do the Zen thing, and be like water, adjusting your course as required. The authors of A Practical Guide to eXtreme Programming explain these and other principles behind extreme programming.
|
- A Human Being Is Not Equivalent to a Tool: Working with the Dynamic Systems Development Method
- Mar 22, 2002
- Working with the DSDM philosophy means adopting an attitude of collaboration, cooperation and commitment from everyone involved. This includes end-users, management and technology professionals. The benefits go beyond a good piece of software.
|
- Communication: the Key to Successful Software Development
- Mar 22, 2002
- Everyone on the product team has to speak in compatible terminology, or nothing will get done (or done correctly, anyway). In this article from The Coad Letter, Stephen Palmer provides groundwork for good communications within and outside the team.
|
- Continuous Integration in XP
- Mar 22, 2002
- Does your hard work on a development project get pitched because someone else on the project saved conflicting changes? In this article, William C. Wake describes methods XP developers use to keep their efforts from going to waste.
|
- Document-Weary? Try Chief Programmer Work Folders
- Mar 22, 2002
- Chief programmer work folders are a simple, effective solution for document-weary development teams. In this article from The Coad Letter, Stephen Palmer explains how the work folder concept functions.
|
- Driving Software
- Mar 22, 2002
- In this chapter from Planning Extreme Programming Kent Beck and Martin Fowler explain how extreme programming is like driving a car: it's not about pointing the car in one direction and holding to it; it's about making lots of little course corrections.
|
- Extreme Programming and the Economics of Software Development
- Mar 22, 2002
- Kent Beck shows you how to maximize the economic value of a software project by paying attention to cash flows, interest rates, and project mortality, from his book Extreme Programming Explained.
|
- Extreme Programming for the Customer, Programmer, Manager: What's a Typical Day
- Mar 22, 2002
- In this chapter from his book, Extreme Programming Explored, William Wake gives a practical, you-are-there glimpse into what happens in a typical day during an XP iteration from the perspective of customer, programmer, and manager.
|
- Feature-Driven Development and Extreme Programming
- Mar 22, 2002
- Superficial similarities between Feature-Driven Development (FDD) and Extreme Programming (XP) hide a number of very important differences between the two processes. This article provides a short comparison of FDD and XP.
|