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.
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.
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.
- 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.
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!