The HCM-F Program's Proposed Rally to Support Agile Value-Driven Backlog activities.

1. HCM-F / HCBU Agile Evolution / – Rally
Structure Proposal
Mohammed Al-Taraireh and Alejandro Perez

2.  Intro
 Requirements
 Goal
 Proposal Rally Structure Layout
 Rally Workflow
 Tracking Infrastructure
 Release Management
 Next Steps
2

3.  HCM-F‟s response to HCBU Agile Evolution
3

4.  Support the “HCS-Fulfillment Backlog” requirements
• Structure Rally and its various tools to reflect and complete requirements
4

5.  Structure Rally to support ask
 Produce quickly available information for all stakeholders
 Reduce Admin OH
• Automate processes
• Use Rally Apps
• Build dashboards
 Educate HCM-F personnel
5

6.  HCM-F Project Structure
• HCS: HCM-F Main Backlog
Scrum Teams
will determine
their team name
o HCM-F BLR Backlog
 BLR Team 1 – (Team Name)
 BLR Team 2 – (Team Name)
 BLR Team 3 – (Team Name)
o HCM-F RCDN Backlog
 RCDN Team 1 – (Team Name)
 RCDN Team 2 – (Team Name)
 RCDN Team 3 – (Team Name)
 RCDN Team 4 – (Team Name)
 RCDN Team 5 – (Team Name)
 RCDN Team 6 – (Team Name)
o HCM-F RTP Backlog
 RTP Team 1 – (Team Name)
 RTP Team 2 – (Team Name)
 RTP Team 3 – (Team Name)
6

7.  Main Backlog to Site Backlogs
• HCS: HCM-F Main Backlog PBIs
Use CBABU
terminology
o PBI = Product Backlog Items
o MMF – Minimal Marketable Feature
PBIs: Features &
EL1 ENG/MTK
o PBIs – 20% Confidence
 Portfolio Item: HCM-F Features (MMF)
• Features & Architectural Features (SAFe)
•
http://scaledagileframework.com/feature/
•
http://scaledagileframework.com/architectural-feature/
Child PBIs
• AC Commitments- Business Requirements
 EL1-ENG/MKT USn
• Epics
Child PBIs
• AC Commitments- Functionality Plan
 Technical Debt USn
• CDETS defects = Sub-PBIs
Movement
by „Project‟
[Field]
Child PBIs
o Action: Add PBIs to Site Backlog
 Move Sub-PBIs to Site backlog
• Use “Project” [Field]
o Action: Reorganize PBIs in Main Backlog
 Re-assigning Sub-PBIs order
• Use “Local Priority” [Field]
7

8.  Site Backlogs to Sprint Backlogs
o HCM-F Site Backlog – 50% Confidence
 PBIs: Children & Sub-Children PBIs
 Children PBIs to Sprint Backlog in Scrum Team
Child PBIs in
Sprint
Backlogs
o Action: Add PBIs to Site Backlog
 Move Sub-PBIs
• Children & Sub-Children PBIs of EL1s
 Assigning Sub-PBIs to Site backlog
• Use “Project” [Field]
Movement by
„Project‟ [Field]
o Action: Reorganize PBIs in Site Backlog
Child PBIs in
Sprint
Backlogs
Child PBIs in
Sprint
Backlogs
 Re-assigning Sub-PBIs order
• Use “Local Priority” [Field]
8

9.  Sprint Backlogs to Iteration/Sprint
o Sub-PBIs @ a 80% Confidence
o Action: Add PBIs to Iteration
Production
Iteration
# n+2
 Assigning Sub-PBIs to Iteration
• Use “Iteration” [Field]
• Note*- Iteration/Sprints are Timeboxes
o Action: Reorganize PBIs in Iteration
 Re-assigning Sub-PBIs order
Iteration
# n+1
Sub-PBIs in
iteration
Iteration
#n
• Use “Local Priority” [Field]
Movement by „Iteration‟ [Field]
9

10.  Finished Sub-PBIs
o Sub-PBI reached DOD
o Action: None
 Teams keep PBIs in Rally “Team” Project
 Accepted PBIs = Achievement
Production
Sub-PBIs to
return to
Sitebaclog
 Accepted PBIs =produce=> Velocity
 Accepted PBIs = history for relative estimating
 Unfinished Sub-PBIs
• PBI did not reach DOD
• PO Options:
Movement
by „Project‟
[Field]
Iteration
# n+2
Iteration
# n +1
Iteration
#n
o Action 1: Return to Site Backlog
 Move Sub-PBIs to Site Backlog
• Use “Project” [Field]
Sub-PBIs to
new Iteration
• Clear “Iteration” [Field]
o Action 2: Reassign to New Iteration
 Move Sub-PBIs to new iteration
• Use “Iteration” [Field]
10

11.  Archiving PBIs
o Unfinished PBIs that are no longer relevant
o Action: Move PBIs to HCM-F Archive
 Move Sub-PBIs to Site Backlog
• Use “Project” [Field]
Movement
by „Iteration‟
[Field]
Achieving irrelevant
PBIs & Sub-PBIs
11

12.  Tracking Mechanisms
• Use Rally Apps
• Build Dashboards for Stakeholders
• Create [Field]s necessary to quickly
collect and express information
 Focus:
Dashboards &
Rally Apps
o Admin Automation
o Increase decision making
o Information availability
o View Production
o Forecasts Enhancements
o Estimates Enhancements
o Work Allocation Enhancements
12

13.  Selecting PBIs for Release
o Requirements:
 Adding Project [Field] for PBIs
• [Field] – Product Release
• [Field] – Release (Native Field) – connects to
Rally‟s Release Tool
PBIs & Sub-PBIs to
Releases
o Action: Select PBI for Release (Product/SOL)
 From any Rally Project:
• Main Backlog
• Sprint Backlog
• Teams
Select to Release
using „Product
Release‟ [Field] &
„Release‟ [Field]
Release
# n+2
Release
# n +1
Release
#n
 Move PBIs & Sub-PBIs?
• Select Product Release [Field]
• Select (Solution) Release [Field]
13

14.  Obtain Feedback HCM-F Key Leader
• Incorporate Feedback
 Gain HCM-F Key Leader Approval
 Migrate data
• From: HCS: Engineering
• To: HCS: HCM-F Main Backlog
14

15.  Meeting Transcript for HCM-F Backlog Proposals / Rally Porfolio Manager
Meeting
 Basic Meeting Information:
Meeting Topic: HCM-F Backlog Proposals / Rally Porfolio Manager
Meeting
Host: Alejandro Perez
Meeting number: 207 092 328
Start Time: Tuesday, February 04, 2014 12:22:50 AM(GMT -8:00)
End Time: Tuesday, February 04, 2014 01:03:59 PM(GMT -8:00)
Meeting URL: https://cisco.webex.com/cisco
 Attendee List:
Alejandro Perez, Navin Manohar, Chuck Homola, Tom Hill (tomhill),
Subodh Shah, Chris Claytor, Shankar Govindasamy, Craig Miller,
 Record:
https://cisco.webex.com/ciscosales/lsr.php?RCID=61e6ebc68b7643b186f2
858ef8228665
15

16.  Meeting Transcript for HCM-F Backlog Proposals / Rally Porfolio Manager
Meeting
 Basic Meeting Information:
Meeting Topic: HCM-F Backlog Proposals / Rally Porfolio Manager
Meeting
Host: Alejandro Perez
Meeting number: 207 092 328
Start Time: Monday, February 03, 2014 09:20:45 AM(GMT -8:00)
End Time: Monday, February 03, 2014 10:09:02 AM(GMT -8:00)
Meeting URL: https://cisco.webex.com/cisco
 Attendee List:
Alejandro Perez, Mo A, Herb Sayre, Chris Claytor,
 Record:
https://cisco.webex.com/ciscosales/lsr.php?RCID=d14304f698aa463bb51
67c1aff28dbcf
16