Project management in Agile Way
55
June 6, 2022 Project Management in Agile Way Andrey Elkin, PMP, C.T.Co
description
This presentation gives an insight on the Agile project management approach, comparing it to the other project manageent approaches in IT. It also shows how this is applied in practice in C.T.Co company.
Transcript of Project management in Agile Way
April 8, 2023
Project Management in Agile Way
Andrey Elkin, PMP, C.T.Co
Who is who
C.T.CoIT Service provider from 1999(Re)insurance businessAgile Practices from 2000
Andrey ElkinProgram/Project Manager (8 in 2012, 12 in 2013)~14 years in IT, ~7 years as PMPMP and ITIL certified
page 2
Project Management in Agile way
What is Agile
page 3
Agile? What it is?
When we mean AgileWe think …
page 4
Agile? What it is?
page 5
Agile Way
page 6
Waterfall Agile
Agile Way vs Waterfall Way
page 7
Agile Software Development
Agile methods break tasks into small increments with minimal planningIterations last from one to four weeksIteration involves a team working through a full software development cycleThis helps minimize overall riskStakeholders produce documentation as requiredIteration goal = Shippable software at the end of each iterationIteration = release
page 8
How agile are you?
Do you use business value to prioritize requirements?Do you have cross functional development teams?Do they deliver working software regularly?Do you review the process at the end of each iteration?Are features small enough to be completed in a short iteration?
page 9
Agile Methods
SCRUMKANBAN
page 10
Scrum
Scrum is an iterative, incremental framework for managing complex work (such as new product development) commonly used with agile software development.
Scrum is a principle-based framework for continuous learning that focuses on maximizing value delivery instead of effort.
page 11
Scrum. Who is who?
page 12
ROI – Product Owner
Process – Scrum MasterQuality – Dev Team
Scrum. How it works?
page 13
Scrum. Real Life
page 14
Agile Methods
SCRUMKANBAN
page 15
KANBAN
Framework made for just-in-time (JIT) productionThe process in KANBAN is going as a flowNo specific time for work package is set, Only WIP amount has been defined
page 16
Six principles of KANBAN
Do not send defective products to the subsequent processThe subsequent process comes to withdraw only what is neededProduce only the exact quantity withdrawn by the subsequent processEqualize productionKANBAN is a means to fine tuningStabilize and rationalize the process
page 17
KANBAN. How it works?
page 18
KANBAN. Real Life
page 19
Project Management in Agile way
Project/Release Planning
page 20
Software Development Lifecycle Model
Software development lifecycle model is based on the effective blend of agile iterative and incremental delivery methods with industry standard frameworks like Rational Unified Process (RUP) and Capability Maturity Model Integration (CMMI)
page 21
Construction1..n iterations
Transition1-2 iterations
Elaboration1-2 iterations
Initiation1-2 iterations
Operations1..n iterations
Phase 12 weeks – 2 months
Phase 22 weeks – 2 months
Phase 3According to project timeline
Release Planning
page 22
Construction1..n iterations
Transition1-2 iterations
Elaboration1-2 iterations
Initiation1-2 iterations
Operations1..n iterations
Phase 12 weeks – 2 months
Phase 22 weeks – 2 months
Phase 3According to project timeline
Construction1..n iterations
Transition1-2 iterations
Elaboration1-2 iterations
Initiation1-2 iterations
Operations1..n iterations
Phase 12 weeks – 2 months
Phase 22 weeks – 2 months
Phase 3According to project timeline
Release 1.0
Release 2.0
Jan Mar May Jul Sep Nov Dec
Release Breakdown
page 23
Construction1..n iterations
Transition1-2 iterations
Elaboration1-2 iterations
Initiation1-2 iterations
Operations1..n iterations
Phase 12 weeks – 2 months
Phase 22 weeks – 2 months
Phase 3According to project timeline
Ready for
UAT
Production rollout
Iterations delivered
Architecture baselined
Production patch
(if needed)
High-level planning
completed Detailed planning
completed
Enough specs to initiate
development
Real Life for Project
page 24
Real Life for Product
page 25
One more example of Real Life
page 26
page 27
Iterations Flow
ITERATION IMPLEMENTATION
Testing processes
Developmentprocesses
DELIVERABLE
Software package
1ITERATION
2 IMPLEMEITERATION
3
WEEK 7 WEEK 8 WEEK 9 WEEK 10 WEEK 11WEEK 6
PRE-ITERATION
Specifications review and clarification,functionality
design
POST-ITERATION
Acceptancereview and adjustment
RECEIVABLE
Finalized specifications
Testing processes
Developmentprocesses
WEEK 5
RECEIVABLE
Finalized specifications
PRE-ITERATION
Specifications review and clarification,functionality
design
PRE-ITERATION
Specifications review and clarification,functionality
design
RECEIVABLE
Finalized specifications
Stabilization processes
IMPLEMENTATION
Testing processes
Developmentprocesses
Stabilization processes
Agile Model vs Waterfall Model
The emphasis is on producing regular visible working application enhancements to demonstrate business value early, and continuously improve the application through incremental and iterative development
page 28
Waterfallmodel
Iterativemodel
Timelineexample
Iter. 1 Iter. 2 Iter. 3 Iter. 4 Iter. 5 Iter. 6 Iter. 7 Iter. 8 Iter. 9 Iter. 10 Iter. 11
Comparison of iterative and waterfall modelsExample of a small to medium-size project
Delivery for testing Delivery for live operations
Project Management in Agile way
Processes and Activities
page 29
Process Map
page 30
CUSTOMERDEVELOPMENT
PARTNER
Construction1..n iterations
Transition1-2 iterations
Elaboration1-2 iterations
I nitiation1-2 iterations
Operations1..n iterations
OPERATIONS SUPPORT
QUALITY CONTROL
PROJ ECT MANAGEMENT
REQUIREMENTS ENGINEERING
ARCHITECTURE DEVELOPMENT
INFRASTRUCTURE MANAGEMENT
MAINTENANCE
Project Management Activities
page 31
MANAGEMENT
TEAM
Project Lead
Hig
h L
evel P
lan
nin
g
Eff
ort
Esti
mati
on
an
d
Ou
tsta
nd
ing
Ite
rati
on
Pla
nn
ing
CLI ENT’s TEAM
Pro
ject
Tasks
Defi
nit
ion
Risk List Update
Project Monitoring and Control
Day to Day Communication
Project Plan
Quality Assurance Specialist
Developer
Tasks
Project Status Report
E-mails, Phone calls
I teration Plan
Business ExpertsProject Manager
Daily Stand up
meetingsE-mails,
phone callsEffort Plan
Pro
ject
Clo
su
re
Closure Report
Project Review Board
Change Control Board
page 32
High Level Planning – Project Plan
Project Plan is compiled with the following content:
PlanningObjectivesScopeReceivablesDeliverablesEstimationsStaffingLifecycleSchedule
PoliciesCommunicationsChange ManagementConfiguration ManagementSecurity PolicyQuality Assurance Quality Control
High Level Planning – Project Plan
Checkpoint reviewsDefined throughout the project, usually at milestone dates.Review are done by both project managers and (preferably) some of the project stakeholders.Face-to-face checkpoint review meetings in addition to written status reports: this will ensure that everyone does get the necessary information.
Routing paths and contact personsList of contact persons from both sides, including deputies, is defined for all major areas.Escalation paths are clearly defined.
page 33
Project Plan – Think on format???
page 34
Project Plan – Be flexible with format!!!
page 35
Estimation and Iteration Planning
In collaboration with project team functionality is estimated and allocated into IterationsTeam tasks are defined and plan is compiled with the following content:
Feature / task nameID of the feature / taskStatus of the feature / taskPriority of the feature / taskIteration the feature / task is assigned toEstimatesAssumptionsDependencies
page 36
Estimation and Monitoring Plan
page 37
Release Development Plan
page 38
Estimation and Iteration Planning
Fullness and Transparency are the corn stones for a good project steering and Trust
page 39
Too much, Too less
It costs you 100 USD
OR
All numbers are calculated by the formulas:
page 40
page 41
Estimation Cone of Uncertainty
Construction1..n iterations
Transition1-2 iterations
Elaboration1-2 iterations
Initiation1-2 iterations
Operations1..n iterations
Phase 12 weeks – 2 months
Phase 22 weeks – 2 months
Phase 3According to project timeline
Project Monitoring and Control
page 42
Project Monitoring and Control
Daily stand-up meetings should take place (15-30 minutes) in order to discuss the current project status and possible events that could influence the outcome of the project
Project risks should be considered and analysed in order to react timely and reduce the impact of the risks occurred to the project outcome
page 43
Project Monitoring and Control Status Report
Allow both project managers and the project review board to track project progressSubmitted on a per-iteration basis (i.e. bi-weekly) in a written form
The following information is always included:Progress compared to baseline (schedule, efforts).Forecasts for remaining part of the project, in numeric terms, for efforts, deliveries, and milestones.
page 44
Project Status Report
page 45
Day to Day Communication
CustomerProject Status Calls – Daily/WeeklyStatus Reports and Meeting NotesChats and E-mailsFace-to-face meetings / workshops
TeamStand-up meetings (work organization)Review meetings (specs, problems, etc.)Project newsAd-hoc meetings (critical issues review)
page 46
Calendar for Very good week
page 47
Day to Day Communication
Status calls:Are held more often than written status reports, and as follow-up after status report reviewShort checklist of open issues is a good practice as it enhances effectiveness of the status calls
Face-to-face meetings:Are held when the project team feels necessary rather than on pre-scheduled basisHelp to avoid “e-mail ping-pong”Purely remote communication creates more issues than mixed face-to-face/remote approach
page 48
Project Management in Agile way
Do we really need PM in projects?
page 49
Nobody want to do this except us
page 50
Our reality
We ...Sale our heads
Don’t forget about yourself in cost calculation. You also would like to be paid
Plan our workMinimize redundant paperwork to minimal. Nobody read them after creation
Are Responsible about our resultsShout about risks as much as you have voice. You are person who deliver project/product
page 51
We speak to Everyone
You will not know each and every detail, but you must be good comapnion in every talk
You will speak withClient Executives – about Money?Client Representatives– again about Money?Company Executives – one more time about Money?Your Boss – still about Money?You Team – finally about Money?
Be open and you will know about all risks and issues and ...... of course about money
page 52
Do you see yourself? On left or right?
This is definitely not our project!!!Sure???
Q&A?
Thank you!
![Welcome! []– Use of Agile methodology (Scrum, Kanban, etc.) to best meet project needs ! Engaged Agile coaches to help along the way "Moved from Waterfall to Agile! Waterfall vs.](https://static.fdocuments.us/doc/165x107/5f0d07a47e708231d438543b/welcome-a-use-of-agile-methodology-scrum-kanban-etc-to-best-meet-project.jpg)
