Waleed Zaki
Release Train Engineer
30-60-90 days plan
Approach
Objectives of 30-60-90 plan
❖
This list of expectations clearly the plan to communicate and set to accomplish during this
period.
❖
The 30-60-90 plan also gives a clear way to track the progress and demonstrate successes.
❖
With a clear list of objectives, it keeps you focused on taking initiative and completing training
and set tasks.
❖
This plan is a framework of what they can expect in the coming weeks and what is the plan to
tackle those tasks.
1
Interview and Explorations
Meetings with all needed individuals and teams to
know everything and what is needed to be known
2
Understanding of Business
3
Strengths
Knowing the client, business owners, Epic owner
context is the key
Includes – purpose, start date, the releasing
habits
Client expectations
Tech Stack and deployment environments
This is on what we will capitalize on
4
Areas of Improvements
This is where the improvements are needed to
begin with
5
Next Steps
Focused workshops
Key initiatives and suggestive changes
Metrics for key changes and how to measure
30 Days
❖
Learning the company. Get a greater understanding of the company’s mission, values, and
culture. Research competition or future growth opportunities and think of concepts that you
think will give the employer a leg up to achieve future goals. Learn the company’s tools and
methodologies, digital or physical boards, and how are things done.
❖
Meeting the team. Introduce yourself to the team members. Learn their work styles and
preferred methods of communication. organise team building activities; team lunch, brownbag
sessions, ..etc. Make sure the team knows that the goal is to guide you and the staff to success.
❖
Actively engaging. Become a consistent participant during meetings, contributing educated
and constructive information based on what you have learned about the company and its
processes. As you gain a better understanding of the company’s current direction and needs,
start initiating projects after you’ve consulted the manager and team members.
Discovery in first 30 days
❖
Process and tools
❖
Last PI planning retro
❖
Meet Product managers, business owners, PO, Scrum masters, ..etc
❖
Review Program boards (Program Kanban, PI boards)
❖
Review ROAM
❖
Review Burn up , burn down charts
❖
Tools (Jira, Confluence, Teams channels, Document management systems,
..etc)
60 Days
❖
Improving processes. Identify what the team is doing well and capitalize on it. Use
concepts from effective methods to enhance processes that need updates. Where there
is room for improvement, make a list of suggestions that can increase employee
productivity, promote collaboration, and spark innovation.
❖
Solving problems. Learn the company’s protocols for situations like making
company-wide decisions and handling conflicts among employees. As situations and
decisions arise, practice utilising these approaches with the manager’s guidance.
❖
Strategising. Develop strategies that can help employees more efficiently approach
tasks and complete projects. Merge these strategies with existing company approaches,
and teach employees how they can use them to enhance their work productivity.
Discovery in next 30 days
❖
Identify gaps in process
❖
Identify any issues or impediments
❖
❖
Team or individual conflict to resolve through problem solving workshops
❖
Platform dependencies
❖
Dependencies on other Initiatives / Epics
Develop Strategies to
❖
Increase Velocity
❖
Increase DRE
90 Days
❖
Working with multiple teams. Some projects will require complex strategies
and cross-functional collaboration between teams. As an RTE, will be
responsible for overseeing these projects and managing communication
between participating teams. Familiarise yourself with these types of projects
and how the company works to address them. Collaborate with the
supervisor to learn the ins and outs of these more elaborate systems.
❖
Setting performance standards. Set specific goals and performance
milestones for team members to strive to hit.
Define Success Criteria
Metric
Criteria
1
Commitment or Productivity
Average commitment variance – Delivered/
Committed velocity
Control limits: 80% – 120%
Tools : Jira reports
2
Consistency or Reliability
=Current sprint velocity / previous sprint
velocity
Control limits: 80% – 120%
Jira Align reports or Jira plugins
3
For Team and ART
Quality (DRE)
Escaped defects
4
Agility Health Assessment
DRE (Defect removal Efficiency) 0.8 to 0.9
80% Maturity
Improvement in Roles
Effective Ceremonies
challenges or
opportunities
Transparency
Predictability
Physical boards for the
collocated teams
Short term goals –
Burndown chart
Online tools for
Knowledge
management
Long term goals Velocity graph
Discovery sessions
to bring future
visibility
Review &
Retrospective events
for continuous
improvement loops
Story points
estimation for
knowing size of
backlog
Client
Discovery
Timely Delivery
Program board
(iterations)
Teams dependencies
ROAM
Feature / capabilities
roadmaps
Program backlog /
Kanban board
Committed features vs
achieved in previous PI
PI demos
Quality of
Work
Well defined DoD
Well defined teams
charter
Well defined DoR
SoS actions and
boards
Improvind Retros
Productivity
Continuous
improvement of
velocity
Productivity
What future challenges or opportunities do you anticipate?
❖
Prepare for next Pre-PI planning
❖
Deliver customer centric value
❖
ART sync to review program backlog priorities
❖
Last System Demo feedback / MoM
❖
High priority projects in pipeline
❖
Actions from Retros and SoS for improvements
What sorts of indicators would you look for to judge the early performance in the role?
ART metrics
❖
Actual percent complete(APC) = Complete Story Point/ total Story points
❖
Expected Percent Complete (EPC) = Number of completed iterations/
number of planned iterations
❖
Defect Removal Efficiency (DRE) =E/(E+D)
E = no errors before S/W delivery D= defects found after delivery