All for One, One for All! Approach to Managing Agile Projects with Shared Services

Yours is an organization delivering multiple projects for different customers through your various teams – shared services.  Though your teams practice agile – and enjoy it! – they do not truly have a dedicated backlog; their efforts are helping deliver value to multiple streams.

Consider the following approach to in setting up VersionOne to help you:

  • Capture multiple project backlogs
  • Assign work to several teams
  • Track progress against project timeframes
  • Allow teams to manage and track their work independently

The Project Tree

  • A root node represents your organization or group’s project repository – here you will capture your projects (more about that in just a moment).
  • Child nodes represent your shared services teams, working at their own agile cadence.
Root node is the organization's project intake/repository, child nodes are team-level backlogs.

Root node is the organization’s project intake/repository, child nodes are team-level backlogs.

The Projects (VersionOne Epics)

  • Captured at the root node level, each VersionOne Epic represents a distinct project, with their own start and end dates.
  • Child VersionOne Epics can be used to define features, capabilities or team level groupings of user stories.
  • Child VersionOne Epics and/or user stories within these are assigned to teams across the Project Tree.

VersionOne Epics at the root node represent projects.  Child Epics and Stories are associated to the shared services teams.

V1 Epics at the root node represent projects. Child Epics and Stories are associated to the shared services teams.

 The Planning Room (V1 Ultimate)

  • The Epic Tree shows the list of Projects (VersionOne Epics) and allows for quick inspection through drill-down.
  • The Epic Timeline tracks progress made on these Projects against a calendar view.
  • The Planning Room can be used to combine views such as the Epic Tree and Epic Timeline for a super charged perspective for project tracking.

Combine VersionOne Epic views such as the Epic Tree and Epic Timeline for a single view into project progress.

Combine V1 Epic views such as the Epic Tree and Epic Timeline for a single view into project progress.

 The TeamRoom

  • The TeamRoom is the dashboard of tools and visuals for tracking team project progress.
  • Displays work allocated to the team.
  • Allows configuration of views for managing project work that matches their team workflows.

Teams use their team dashboard - the TeamRoom - to configure, manage, and track their project work.

Teams use their team dashboard – the Team Room – to configure, manage, and track their project work.

Most progress-tracking reports – e.g., Burndown, Estimate Trend, Velocity, etc. – can be filtered by a VersionOne Epic (your project), so metrics are readily available at any level of granularity.

So, are you an organization with all teams contributing to a project – All for One?  Try this approach, a simple project tracking approach – One for All!

Cheers!

About Victor Hernandez

Technology generalist, visual thinker, perennially curious - Inspect and Adapt!
This entry was posted in Admin, Backlog Management, Getting Started, Kanban, Product & Release Planning, Product Owner, Product Tips & Tricks, Program Management, Program Manager, Project Manager, ScrumMaster, ScrumMaster, Stakeholder. Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>