The business value statement and points are derived on the basis of a detailed analysis of the business landscape, competition and stakeholders.

Kuliza takes this up jointly with clients and brings in its experience in handling multiple product lifecycles.

The product backlog is a set of deliverables (features to be a part of various releases), user stories and feature priorities

• The product backlog is communicated to the team
• Sprint cycles are agreed up – these are of either two or four weeks duration. A working software release is planned at the end of each cycle
• The team prepares the sprint backlog based on the then product backlog and the cycle
• Kuliza’s ScrumMasters coordinate the entire process and address issues that come up in the daily 15 minute scrum meetings
• Progress is tracked on a daily basis through burndown charts and cumulative flow diagrams

• The velocity of the development process is measured as the rate at which the product backlog reduces every day and in every sprint
• Working software is released to clients so that they can use it and provide feedback
• Requests for new requirements and feedback on deliverables is incorporated
• The feedback is included in subsequent sprint cycles
• The uber timeline of the project and quality are fixed for the set of resources allocated to the development effort