You are adopting Agile practices throughout your organization, and you set up a shiny new set of tools to support it.  All of your teams have captured their backlog and are running their Sprints (Scrum) or continuous-flow (Kanban) process.  Great!  There is only one problem.  How can management see at a glance what is going on in each effort?

  • How do we know if each effort is “on track” or headed for disaster?
  • How do we know when we have capacity to take on new initiatives?
  • If a new high priority/urgent initiative is proposed, how can we quickly see if it would impact other efforts at the same or higher business priority?
  • If a new high priority/urgent initiative must be undertaken, how can we quickly analyze resources and schedules for what is happening currently, so we can do an impact analysis?
  • How can we avoid getting bogged down in the day-to-day minutiae of user stories, story points, and bugs and quickly identify important blockers, major risks, or emerging trends that could have ripple effects?

Through a case study involving a $1B municipal government agency, we will describe the process of configuring a set of tools to feed a one-page dashboard displaying current and proposed initiatives – enabling management decision-making.  The tools include Atlassian JIRA, BitBucket, Bamboo, and LeanKit, but the lessons may be applied to other similar toolchains.   We analyze both the technical work involved, as well as the important process and cultural changes we had to make in order for this to happen.   All changes automatically roll up from the team level to the portfolio level, so that progress, blockages, and risks are always visible.   Senior management can drill down to get details if needed.

Perhaps “Agile PMO” is not an oxymoron, after all.

 
1 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

The Problem

Solution:

  • Tools
  • Processes

Cultural Issues

Implementation

Limitations

Lessons Learned

Next Steps

Learning Outcome

  • Understand the scope of effort involved to set up an “agile PMO” and why it’s important
  • Know what kinds of cultural resistance may be encountered, setting up portfolio-level processing and how to work around it
  • Understand the modifications that may have to be made to development processes in order to support automated roll-up to the portfolio level
  • Have a high-level grasp of the steps involved to connect a Kanban tool such as LeanKit to an application lifecycle management tool suite such as Atlassian JIRA to support Portfolio Kanban process

Target Audience

IT Managers, CTO, CIO, Coaches, Scrum practitioners, Traditional project and portfolio managers

Prerequisite

n/a

schedule Submitted 1 week ago

Comments Subscribe to Comments

comment Comment on this Proposal