Conclusion

Job drivers

Attitudes - personality traits that affect behavior and decision-making (e.g. social pressure, corporate culture, personality, expectations of others)
Background - long-term context that affects behavior and decision-making (e.g. geographic/cultural dynamics)
Circumstances - immediate or near-term factors that affect behavior and decision-making (e.g. environmental factors, work schedule, unexpected events)

Attitudes
- Some agile practitioners may question putting completion dates on features as they feel it may drive more “push” behavior than the “pull” model of agile
Background
- Sometimes, instead of quarterly timeboxes, program leadership will use rolling wave planning models which allow feature delivery to span across many iterations/sprints
Circumstances
- Adding more timeframe delivery details with target iterations/sprints and even delivery dates can help support potential business needs
- The specification of delivery execution is managed on the program board with target sprint delivery to reflect the validated plan by the program leadership team

Attitudes
- Business stakeholders may give aggressive completion dates because they feel they need to in order to get the functionality they need on time
Background
- In some environments, more specific requirements to track dates are required due to regulations and and other factors associated with an organization
- Agile releases should generally evolve to occur more frequently for a delivering organization
Circumstances
- The initiation and target completion dates should be used primarily for product management targeting purposes
- In some cases, business planning may require requesting a specific sprint start and/or end for a feature
- It is important to understand that key results with dates will primarily be used for data collection post-release once the positive (or negative) impact from launch can be assessed

Attitudes
- Without specifying delivery dates, business stakeholders feel they can’t provide their customers information on when expected value will be delivered
Background
- Understanding the organization's current state environment, including strategic direction, technology platform, and organizational readiness is critical to being able to properly target delivery dates (i.e. how quickly can we release value?)
Circumstances
- In immature environments, just leveraging Jira Align to manage the chaos around making & meeting feature delivery commitments in a timebox may be a great first step

You successfully completed this blueprint!

Previous step:

Was this content helpful?

Connect, share, or get additional help