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
- Sometimes stakeholders are not shown functionality until it is done, which can lead to negative feelings between the stakeholders and teams if the functionality is not what was expected
- Teams feel pride in their work when given the chance to demo functionality developed to stakeholders and customers
Background
- Sometimes an organization doesn’t have a formal ceremony to bring together internal/external stakeholders to review progress on the functionality and see it working
- Sometimes demos are only focused on the team level, with cross-team demos showing integrated functionality only happening occasionally
- Sometimes organizations measure progress by the number of work items completed and not the working software itself
Circumstances
- Demos in an integrated environment will create a better sense of the completeness of functionality
- Demos should be focused on features and less on teams in order to show the holistic business functionality

Attitudes
- Sometimes teams feel pressure from stakeholders to rollover incomplete work from one planning period to another without reevaluating the merits of the work
Background
- In order to build and maintain trust between the stakeholders and technology, programs must do their best to hit their commitments
Circumstances
- When functionality is not complete and/or objectives not met, immediate communication with stakeholders is needed

Attitudes
- Without taking action on items that come out of a retrospective, team members will feel discouraged and the event will just feel like group therapy
Background
- Sometimes organizations will hold retrospectives, but they are qualitatively focused (how do you feel) vs a mixture of qualitative and quantitative (how do you feel and how did we perform)
- Sometimes retrospectives only happen at the team level, meaning systemic, cross-team issues go unanswered
- Sometimes organizations don’t know how to track improvement items and ensure they are getting done to help them improve
Circumstances
- Ensuring everyone from the program can participate is critical, as feedback from the entire program is necessary to gather the best ideas
- Once ideas are aligned on, add them to the program backlog to ensure they are not lost

You successfully completed this blueprint!

Previous step:

Was this content helpful?

Connect, share, or get additional help