Deliver Early and Often

Our development approach generally follows a hybrid Scrum/XP methodology. A few key portions of the Scrum project management model include:

  • JIT Requirements Definition (Product Backlog / Sprint Backlog)
  • Delivering “working software” on a regular basis
  • Daily Sprint “Stand-Ups”
  • “Sprint” increments should be of short duration (1-4 weeks, 2 weeks being preferable)

There are many reasons to adopt a development approach that employs short iterations, providing working software at the end of each Sprint. A few of the more important reasons:

  • Investment of the business stakeholder community; stakeholders are more interested in working software than specifications
  • Accurate metrics; many executives consider the only accurate measure of a project’s progress is based on the delivery of working software
  • Improved understanding; as the system evolves through a series of “Sprints”, each “Working Increment of Software” helps to improve an organization’s understanding of what has been built, and improves the JIT Requirements definition of what is yet to come
  • Sustainable Development Tempo; by delivering Working increments of Software, forecasting metrics become more accurate and predictive over the course of the program. This helps to create a sustainable development “tempo” for the team, which helps to avoid “development burnout” and diminishes overall delivery risk