An Overview of the Development Stage

What happens in the Development Stage in our Way of Working.

The purpose of the development phase is to build software that meets the scoped requirements, in a manner that delivers value early and often to the customer. The development of a product can commence at any point after the scope has been fully delivered.

The cycle is comprised of many iterations which continue until the development has been completed to the product owner’s satisfaction. Every iteration includes meetings, checkpoints and software releases to ensure the delivery of functional software and that customer satisfaction is maintained. 

The development workflow is underpinned by many development iterations that result in a releasable product version, typically called a build. An iteration is a short, time-boxed period when a delivery team works to complete a defined set of requirements. Iterations generally have project related goals associated with them, but in general should deliver an increment that can be used and tested. Defining the work to be completed during an iteration is a shared responsibility between the product owner and the delivery team. 

The length of development varies between projects and depends heavily upon the scale and complexity of the solution. As mentioned in scope, there is a preference toward shorter scopes, which tend to create smaller and more manageable development cycles. Reducing the size of a build not only allows for increased certainty around estimations, but also lets the Product Success team incorporate user feedback into subsequent scopes. 

 

Customer commitment 

Generally, the level of commitment for a Product Owner is high during the development phase. Per iteration they are expected to be available for the planning, review and elaboration sessions, as well as any UAT sessions that are required. Beyond this, the Product Owner is the key decision maker for the project and should expect to be contacted often in relation to factors effecting or blocking an iteration’s progress. 

Other stakeholders in the business can generally remain reasonably hands off, however it is recommended to check-in on review sessions from time-to-time. It’s crucial that the Product Owner understands how important it is to keep all relevant stakeholders updated of the project’s progress. As the primary contact for the development team, aligning the delivery expectations through their business is a core part of their dedication to working with us.