Extreme programming practices: Difference between revisions

Revision as of 20:21, 5 April 2007

Revision as of 20:48, 6 April 2007

Line 26:

*Get Requirement from Customer: Business has come with a problem; during a meeting, development will try to define this problem and get requirements.

*Write a Story: Based on the business problem, a story has to be written. This is done by business, where they point out what they want a part of the system to do. It is important that development has no influence on this story. The story is written on a [[user story|user story card]].

*Split a Story: Every design critical complextiycomplexity has to be addressed before stating the iteration planning. If development isn't able to estimate the story (next item), it needs to be split up and written again. Development can also create spike solutions to analyze or solve the problem. These solutions are used for estimation and discarded once everyone gets clear visualization of the problem. Again, this may not influence the business requirements.

*Estimate a Story: Development estimates how long it will take to implement the work implied by the story card.