Project management in Agile Way

transcript

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

Project Management in Agile way

What is Agile

Agile? What it is?

When we mean AgileWe think …

Agile? What it is?

Agile Way

Waterfall Agile

Agile Way vs Waterfall Way

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

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?

Agile Methods

SCRUMKANBAN

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.

Scrum. Who is who?

ROI – Product Owner

Process – Scrum MasterQuality – Dev Team

Scrum. How it works?

Scrum. Real Life

Agile Methods

SCRUMKANBAN

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

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

KANBAN. How it works?

KANBAN. Real Life

Project/Release Planning

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)

Construction1..n iterations

Transition1-2 iterations

Elaboration1-2 iterations

Initiation1-2 iterations

Operations1..n iterations

Phase 12 weeks – 2 months

Phase 3According to project timeline

Release Planning

Release 1.0

Release 2.0

Jan Mar May Jul Sep Nov Dec

Release Breakdown

Ready for

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

Real Life for Product

One more example of Real Life

Iterations Flow

ITERATION IMPLEMENTATION

Testing processes

Developmentprocesses

DELIVERABLE

Software package

1ITERATION

2 IMPLEMEITERATION

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

WEEK 5

RECEIVABLE

PRE-ITERATION

design

PRE-ITERATION

design

RECEIVABLE

Stabilization processes

IMPLEMENTATION

Testing processes

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

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

Processes and Activities

Process Map

CUSTOMERDEVELOPMENT

PARTNER

I nitiation1-2 iterations

OPERATIONS SUPPORT

QUALITY CONTROL

PROJ ECT MANAGEMENT

REQUIREMENTS ENGINEERING

ARCHITECTURE DEVELOPMENT

INFRASTRUCTURE MANAGEMENT

MAINTENANCE

Project Management Activities

MANAGEMENT

Project Lead

evel P

CLI ENT’s TEAM

Risk List Update

Project Monitoring and Control

Day to Day Communication

Project Plan

Quality Assurance Specialist

Developer

Project Status Report

E-mails, Phone calls

I teration Plan

Business ExpertsProject Manager

Daily Stand up

meetingsE-mails,

phone callsEffort Plan

Closure Report

Project Review Board

Change Control Board

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.

Project Plan – Think on format???

Project Plan – Be flexible with format!!!

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

Estimation and Monitoring Plan

Release Development Plan

Estimation and Iteration Planning

Fullness and Transparency are the corn stones for a good project steering and Trust

Too much, Too less

It costs you 100 USD

All numbers are calculated by the formulas:

Estimation Cone of Uncertainty

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

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.

Project Status Report

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)

Calendar for Very good week

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

Do we really need PM in projects?

Nobody want to do this except us

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

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

Do you see yourself? On left or right?

This is definitely not our project!!!Sure???

Thank you!

Project management in Agile Way

Documents