Agile Planning Business Roadmaps, Architecture Standards, and DevOps Releases

Agile planning doesn't end when stories are written, accepted by the team, sized, and ready for development.

Story writing is one aspect of agile planning, but it's not the only one. At StarCIO, agile planning is done at several levels depending on the complexity of the requirement.

Agile planning at business, engineering, and operations levels

If you consider the main deliverable of an agile team is a release, then agile planning is done in several areas

  • At the portfolio level where new ideas are introduced, reviewed for business value, and evaluated whether to commit planning teams to dive deeper.
  • At the business level, where strategic drivers, product visions, and roadmaps are developed and releases are communicated.
  • At the engineering level, where agile planning is predominantly about writing and sizing user stories but mature teams go further by defining data, architecture, and other standards.
  • At the devops level, where testing, pipeline, and other release management are considered.
  • At the organization level, where teams monitor releases at the business, functional, and system levels to ensure the release is performing as expected.
  • At the culture level, where organizations learn from their experiences and celebrate their wins.

Over the next few months, I'll be sharing a lot more details on StarCIO's Agile Planning programs including workshops, training, and how to become certified. 

No comments:

Post a Comment

Comments on this blog are moderated and we do not accept comments that have links to other websites.