A key first step in product-level agile development: Setting the pace of release releases

Objective:

Product-level Agile development The main goal is to achieve: with the least output, but can have the most positive impact on customers?

PI (program Increment) is the rhythm of the release to enable the team to produce the most valuable product features or functionality for the customer during the shortest version development cycle.

Therefore, the key first step in product-level agile development is to develop a PI (program Increment) that is reasonable and capable of satisfying external customer requirements, in accordance with the status of product quality and team capacity.

This paper:

Develop a reasonable and able to meet external customer requirements of the Pi (program Increment), the need for comprehensive product quality background, pi delivery purpose, the nature of demand and team members of the status assessment?

1. Background of product quality:

The quality of a product has been unable to satisfy the customer? The main factor is that the team has been taking on too many demands, and the project manager has failed to control the scope and development of the requirements, so that the team often delays delivery of the customer commitment to the requirements? Customer confidence in the product is not enough?

2. The purpose of PI (program Increment) Delivery:

Because of the quality of products, so that customers lack of confidence in the product, so, PI (program Increment) delivery is to regain customer confidence in the product as the most important purpose?

3. Properties of requirements:

The demand for deferred delivery to customers is mostly "functional enhancement" rather than "feature" level requirements.

4. Status assessment of team members:

Development backbone staff to assess the "functional enhancement" requirements, can be in "two weeks" can have the development progress of the sit test?

Test backbone personnel evaluate the developer's "Two Week" development effort, and testers can complete the sit test "within a week"?

reasonable and able to meet the requirements of external customers PI (program Increment):

To regain customer confidence in the product, and the delayed delivery of the customer commitment to the requirements of most of the "functional enhancement" requirements, and by the development of the backbone and testing staff of the joint assessment, the team for "functional enhancement" requirements, the "3 weeks" cycle delivery?

The initial team developed the PI (program Increment) as a "3 Week " for rapid delivery of the requirements to the customer and the ability of the team members. ?

Conclusion:

Integrated product quality background, pi delivery purpose, demand properties and the team member's status assessment are initially developed by the team version of Pi (program Increment), it is necessary to re-confirm the Pi (Increment) According to the scenario of the requirement item Rationality and continuously optimize the team's development efficiency and quality based on the measurement data of each sprint's development efficiency and quality?

Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.

A key first step in product-level agile development: Setting the pace of release releases