Disciplined Agile

Accelerate Value Delivery

This Construction process goal describes how your team will ensure your solution is ready to be deployed. This goal addresses testing, configuration management, configuration management, automation, and deployment aspects of development. To be effective, we need to consider several important questions:

  • How can we organize our team structure to improve our overall effectiveness?
  • How can we optimize our overall way of working (WoW)?
  • How can we do to improve the flow of work?
  • How will we deploy our solution?
  • How can we automate our technical infrastructure?
  • How will we manage the assets that we produce?
  • How will we manage the configuration of our assets?
  • What strategies will we follow to validate our work?
  • What types of testing will we need to perform?
  • How will we assure stakeholders that the quality of our work is sufficient?
  • How will we maintain traceability, if at all? 
Copyright Project Management Institute All Rights Reserved Accelerate Value Delivery v5.5 Optimize Team Borrow team member Drop team member Focused solution team (FST) Generalizing specialists Utilize existing talents Optimize Work Avoid over production Make work visible Make workflow visible Quality checklist Optimize Flow Align cadences Introduce slack Reduce batch size Focus on finishing Reduce work in process (WIP) Remove delay Remove handoff Remove handback Choose a Deployment Strategy Continuous deployment (CD)/release stream Continuous deployment (CD) - internal only Regular releases/release train External release as appropriate Internal release as appropriate Single release Plan Deployment Continuous deployment (CD) Continuous deployment (CD) - internal only Active stakeholder participation Continuous planning Plan late Automate Infrastructure Automated regression tests Continuous integration (CI)/Continuous deployment (CD) pipeline Feature access control Feature toggles Monitoring instrumentation Self-recovery Self-testing Manage Assets Configuration management (CM) Version control Shared folders Choose an SCM Branching Strategy Branch by customer/organization Branch by developer/workspace Branch by module/component Branch by phase/quality gate Branch by purpose Branch by task/story Branch by version/release Single branch (trunk based) Choose Testing Strategies Automated regression testing Behavior-driven development (BDD) Continuous integration (CI) End-of-life-cycle testing Integration tests first Manual testing Parallel independent testing Test-after development Test-driven development (TDD) Choose Testing Types Accessibility testing Alpha/beta/pilot/canary testing Component testing Database testing Exploratory testing Functional testing (FT) Performance testing Prototypes Quality attributes (ility) testing Security testing Simulations Split (A/B) testing Story testing System integration testing (SIT) Unit testing (UT) User acceptance testing (UAT) User experience (UX) testing User interface (UI) testing Workflow/scenario testing Verify Quality of Work Static analysis Dynamic analysis Nonsolo work Definition of done (DoD) Informal reviews Formal reviews Maintain Traceability Generate from tools Generate from test code None Maintain manually

Figure 1. The Accelerate Value Delivery process goal diagram (click to enlarge).

You can use the DA Browser to learn more about the options in the goal diagram of Figure 1. 

Why This is Important

This process goal is important because it enables us to: 

  • Streamline deployment. For our deployment efforts to be effective, we must choose the best strategy that our team is capable of and actively plan our approach with applicable stakeholders such as operations engineers and release managers. We will need a strategy for how we release internally, such as into a demo environment or testing environment(s), and how we will release into production.
  • Support a DevOps strategy through streamlining and automation. A key component of any DevOps strategy is automation of operational functionality to monitor and control running systems. In combination with automating your continuous integration (CI)/continuous deployment (CD) pipeline, this is often referred to as an “infrastructure as code” strategy.
  • Build quality activities into our process. We want to build quality into our process from the very beginning of the life cycle, including both validation and verification (V&V) strategies. Ideally, we want to avoid injecting quality problems to begin with, typically through continuous collaboration, but failing that we want to find any potential defects as early as possible to reduce the average cost of fixing them. This is often referred to as a “shift left” strategy. 

Key Points

  • Teams actively streamline development through automation.
  • When deployment isn’t (yet) fully automated, it will need to be planned for with appropriate stakeholders from operations.
  • Teams actively test their work throughout Construction, building quality into the entire life cycle.