Pantha Corp Agile Product Development Lifecycle

The iterative development ("sprints") process explained

See also: user story life cycle

• Client requirements are specified in the form of user-stories by a Pantha Corp business analyst, in collaboration with the client business contact
• A user Story includes an overview, use cases, wireframes, assumptions
• Based on this initial input, Pantha Corp tester will write acceptance tests
• Upon completion of the writing of a user story, it can be signed off by the client
• Once client provided its sign-off, Pantha Corp will sign-off as well
• All signed-off stories will go into the sprint planning session where they will be presented to and reviewed by the Scrum team
• The outcome of the planning session will be a confirmation of which user stories can be worked during a given Sprint (~2 weeks cycle)
• The Scrum team - composed of a PM/ Scrum Master, developers & testers - provides detailed technical tasks, estimation per task (in hours) and overview of technical solution
• The technical solution design is then reviewed and signed off by client and/or Pantha Corp technical owner
• Implementation can commence once a story received business and technical sign-off and was scheduled for the current iteration
• It then goes through the cycle of development, continuous integration and quality assurance (testing, defect filing and prioritization, bug-fixing) standard for each sprint
• All developers and testers will update their time spent using our agile project management tracking tool
• Based on this input, PanthaCorp will generate daily and weekly progress reports which are circulated to the core team
• At the end of each sprint, the sprint handover meeting occurs in which the past development cycle is reviewed (retrospective) and the outcome demo-ed to the client