combining waterfall and adaptive practice in it projects

Post on 13-Apr-2017

174 Views

Category:

Software

0 Downloads

Preview:

Click to see full reader

TRANSCRIPT

Combining PMBOK waterfall andAdaptive (Agile, Scrum) models forstart-up software projects

Страница 2

DANIL DINTSISPH. D. IN SYSTEM ANALYSIS, PGMP, PMP, ITIL OSA, MOF CERTIFIED SPECIALIST

CONSULT@DINTSIS.ORGWWW.DDINTSIS.COM

Страница 3 www.specialist.ru

Sources

PMBOK® Guide 5 Edition PMBOK Extension for Software Projects ISO/IEC/IEEE/ГОСТ Р ИСО 12207, 15288 IEEE Standards (SWEBOK® 3) ITIL ®, MOF®

Страница 4 www.specialist.ru

What is Software Product? It is:

Business Solution Common Decision

Serviceable and Changeable

Страница 5 www.specialist.ru

Software and Apps as a specific type of a Product

Wide audience

Virtual teams

External dependencies

High educated developers

Advanced users

Страница 6 www.specialist.ru

Project planning and management models

Страница 7 www.specialist.ru

Waterfall – planning from start to finish

The most lovely one by corporate customers and top managers

Страница 8 www.specialist.ru

Rolling wave

Rolling wave is the best approach for long projects, or for projects with phase-to-phase dependencies

Страница 9 www.specialist.ru

Waterfall model advantages

Strong and clear development roadmap Opportunity for complex architectural planning Clearly defined project scope: time, resources, finance

Страница 10 www.specialist.ru

Early bird key decisions.

Waterfall models are hard to quick changes.

Final product market opportunities are in a risk zone in case of long-term development

Disadvantages of the waterfall model

Страница 11 www.specialist.ru

Adaptive models

Страница 12 www.specialist.ru

Agile modelUser story

Analyze

Projectize

Develop (Code)

Document

Test and Validate

Operate

Страница 13 www.specialist.ru

• Incremental planning with steps from 1-day to 1 month• Integration of users and developers in a regular collaboration• Small self-organized teams• Large projects can include many adaptive teams• Each team member works on a single project during one iteration• Each team includes specialists with specific and general

competencies

Adaptive model. Main features

Страница 14 www.specialist.ru

• predict results• strongly fixed project scope• team considers result as realistic one

• clear monitoring and control

• assistance in other projects planning• baseline for resource, financial and schedule

planning

Why WBS is so important?

Project

Package Package Package

Phase

Страница 15 www.specialist.ru

Time

Func

tiona

lity

Minimizing risks in requirements

Release 1

Release 2

Release 3

ADAPTIVE MODELS

Страница 16 www.specialist.ru

Disadvantages of the Adaptive model

Summarizing of bugs from consequent iterations Volume, time and resource uncertainty

Strategic planning challenges

Strongly based on both customer’s and team’s involvement and motivation

Страница 17 www.specialist.ru

Combined waterfall – agile model as in the PMBOK extension for software projects

Страница 18 www.specialist.ru

Risk management cycle combining waterfall and agileas in the PMBOK extension for software projects

Страница 19 www.specialist.ru

MSF model

Project plan approved

Out ofDevelopm

ent

Release Readiness Review

Deployment Milestone

Vision approved

Vision

Deploy

men

t

Build

Det

aile

d pl

anni

ngStabilize

Страница 20 www.specialist.ru

A Single Iteration Lifecycle

Plan

Analyze

DesignDevelop

Test

© Scott Schultz “Rapid Iterative Production Prototyping”, 1988

Страница 21 www.specialist.ru

WBS extension for mixed Waterfall – Agile models

Страница 22 www.specialist.ru

Boards for different planning levels (based on Trello)

Global Board

Package board

(SCRUM)

Team member individual

board

Страница 23 www.specialist.ru

Product. Version 1.0

Страница 24 www.specialist.ru

Развитие продукта. Регулярные улучшения

Страница 25 www.specialist.ru

Change levels vs Planning models

Change category

What changes Difficulties Duration Model

First level Modification of existing work procedures

Low Fast change Adaptive/Agile

Second level

Changing of business procedures

Medium Medium Adaptive as a part of a project/Program

Third level Changing business branches

Very difficult Long-term Portfolio

Страница 26 www.specialist.ru

Developers are not only a “resourse”!People need more than tasks!

Team motivation. Implementing best from Agile

Страница 27 www.specialist.ru

Team building approaches

Combining local and virtual teams Experts and specialists of common practices Balance between project and functional team members

Страница 28 www.specialist.ru

Face-to-face information change recommended

Страница 29 www.specialist.ru

Team work models

Pair programming

Test-led programming Co-location

Страница 30 www.specialist.ru

PM role

Leadership

Control

Страница 31 www.specialist.ru

Slack as an example of a team collaboration tool

Страница 32 www.specialist.ru

Contacts

www.i-mokymas.com info@i-mokymas.com www.itstartupadvise.me

top related