Anti-patterns seen in the organization at team, program, portfolio level.
Build the right thing
- Alignment of product with portfolio not well understood
- Skip product chartering
- Not listening to the customer / stakeholder voice over own voice.
- Not doing “why this, why now?” prioritization before taking on work
- Not having a clear, measurable hypothesis before picking up major work.
- Not completing the “learning cycle”
Build the thing right
- Pushing code-debt down the road, be reactive, rather than pro-active.
- Deep silo is a major issue. Major subsystems owned by a single person, sometimes resistant to relinquish control.
- Code not in repo.
- Database scripts are out of repository.
- Database and Code are not versioned together.
- Change management not in place. No discipline around release of versioned software to different environments, to facilitate roll back, roll forward, bug tracking etc.
Built the thing fast
- Ditch retrospective.
- Skip team chartering
- Output tracking over Outcome tracking at the leadership level
- Lack of output tracking at the team level
Funding and Budgeting (PMO stuff)
- Output, not outcome, driven funding, commitment
- Year-long Commitment around old recommendations (70/70 items in recommendations done 3 years back will be delivered.)