| Deutsche Übersetzung | |
| Context | Overview requirements are available as Product Backlog Items, but they are not specific enough to start implementation without further information. |
| Problem | Requirements are not specific enough to start implementation. Using an agile approach usually relieves Product Owners and their supporting organization of a number of tasks as developers are supposed to fill in gaps based on their experience and knowledge. However, product-related decisions still need to be done by product management, especially as they are strengthened in their role Product Owners. |
| Forces | too little/too much detail in written requirements specification too little/too much detail in communicating requirements verbally |
| Solution | Keep the requirements themselves lightwheight and add supporting specifications. Requirements can be communicated successfully if they are short and focussed. However, supporting specifications are required in a lot of cases to show the way when developers dig into the details. Usual formats for agile requirements are user stories and use cases. Especially the user story format allows to write very short requirements and may lead to incomplete analysis by the Product Owner. So ensure that the requirements are fully analyzed before they are communication to the team and that enough information is available to start implementation without additional business analysis by the team. |
| Resulting Context | Fully specified Product Backlog Items are available and implementation can start without the need for immediate clarification. |
Dieser Artikel wurde von Andreas Heilwagen am 13.04.2011 um 08:30 gepostet und unter Scrum eingeordnet. Sie können Kommentaren über den RSS 2.0-Feed folgen. Das Posting steht unter der Creative Commons-Lizenz wenn nicht anders vermerkt.
