Code/Schema Analysis | Glossary

Definition:

In Disciplined Agile Delivery (DAD), it is important to capture metrics using taskboards and burndown charts. For more advanced metrics such as defect rates, status of builds, and work item management, an advanced analytics tool is worth while. Because it detracts the developers from their primary task of creating solution. To avoid developers from maintaining and tabulating the metrics, a modern tool that enables in-depth reporting of many important metrics simultaneously via dashboards while the team works on the solution. This analysis tracks the performance when each time a UI test suite is built, and if this test fails Schema Analysis is performed to rectify the potential quality problems as opposed to quality defects raised by the stakeholders.

For an example, if you are not following certain coding conventions in some places that you have cyclomatic problems in your code or a database schema that might not be adequately normalized. In such case the problems that you may be concerned about may not be serious enough to stop you from releasing into production.

Further Reading:

Book: Disciplined Agile Delivery by Scott W. Ambler and Mark Lines

Glossary

Value-Driven Lifecycle | Glossary

Definition:

In Disciplined Agile Delivery (DAD) process framework, value-driven lifecycle is a lightweight strategy used to address common project risks such as having a concurrent vision with stakeholders and proving the architecture early in lifecycle. This value-driven strategy reduces delivery risks associated with DAD teams during producing consumable solutions on a regular basis.

Value-driven lifecycle approach is philosophy consistent with DAD approach which is adopted as an extension to some value-driven methods like XP and Scrum. With a value-driven lifecycle you produce potentially shippable software every iteration or, more accurately from a DAD perspective, a potentially consumable solution every iteration. Value-driven lifecycles address three important risks—the risk of not delivering at all, the risk of delivering the wrong functionality, and political risks resulting from lack of visibility into what the team is producing.

Further Reading:

Book: Disciplined Agile Delivery by Scott W. Ambler and Mark Lines