requirements
|
Embrace Changing Requirements or Work Hard to Reduce Uncertainty?Agile development teams and practitioners can welcome changing requirements all they want—but how hard should they work to reduce the uncertainty that accompanies changing requirements? Experts have mixed opinions on the topic, and each side makes a pretty convincing argument. | 
|
|
How Agile Can Deliver on a Fixed-Budget (Not Fixed-Price) PromiseDevelopment projects run into problems any time they attempt to stick to a fixed-price, fixed-scope, and fixed-completion contract. Learn why this fixed iron-triangle sets projects up for failure and what agile teams can do to solve the problem and make the customer and the developers happy. | 
|
|
The Latest Software Configuration Management Technology Joe Farah explains that if you are using 2nd-generation or even 1st-generation software configuration management technology, you are stuck in the past. To learn what is possible today, you need to look at the capabilities of the latest 3rd and 4th generation tools. Then, you need to get going! |
|
|
When Are Lean Software Requirements Too Lean?Most people know that agile doesn't completely eliminate documentation, but it's a little less clear just how lean we can really make our requirements without sacrificing quality. Mickey Merritt shares how to stay agile with requirements that are just the right fit for getting the job done. | 
|
|
What Role Does Configuration Management Play in Requirements Analysis? Once the inception phase of your project has been completed, a project will enter the requirements analysis phase. Joe Townsend explains the role that configuration management (CM) and quality assurance/control (QA/QC) plays during this phase of a project’s lifecycle. |
|
|
Book Review: Discover to Deliver—Agile Product Planning and AnalysisDiscover to Deliver—Agile Product Planning and Analysis, Ellen Gottesdiener's and Mary Gorman's book, is for software teams that are good at creating software but struggle to create the right value. The authors show techniques to help you adapt to the specific delivery method you're using. | 
|
|
The Importance of "Occasional User" RequirementsOccasional users are likely to go back to more traditional, offline methods if the online equivalent isn’t immediately intuitive. There is little benefit for taking time to learn the system—as they’ll only be using it occasionally. This could impact the business case for moving a process to the web. | 
|
|
Book Review: Lean UX—Lean Principles to Improve User ExperienceSteve Berczuk reviews Lean UX: Applying Lean Principles to Improve User Experience by Jeff Gothelf and Josh Seiden. Through its stories, templates, and guidelines on agile user-experience design, this book will help your team do a better job of building in the best user experience possible. | 
|