E

R
A
W
T
F
O
AGILE S
T
N
E
M
P
O
L
E
DEV

BASICS

L
L
A
F
R
E
T
A
W
Y
G
O
L
O
D
O
H
MET

Requirements

CLICK ICON TO ADD PICTURE

System design
Development
Testing and Build
Maintenance

WATERFALL MODEL
THE WATERFALL MODEL IS A SEQUENTIAL DESIGN PROCESS

CLICK ICON TO ADD PICTURE

Software
requirement
specification

Software
architecture
document

WATERFALL ARTIFACTS
WATERFALL PROCESS REQUIRES TONS OF DOCS!

Software QA
Plan

Test results
report

CLICK ICON TO ADD PICTURE

Requirements
2013

Architecture and design

2013

Development
2014

Testing
2015

Build
2016

PLANNING AND SYSTEM DESIGN TAKES A LOT OF EFFORT AND TIME

CLICK ICON TO ADD PICTURE

Requirements
2013

Architecture design
2013

Development
2013

Testing
2014

CHANGE REQUESTS MAY OCCUR DURING LATE PHASES

Build
2015

CHANGES HAVE SIGNIFICANT IMPACT ON PROJECT SUCCESS

EACH DOCUMENT MIGHT BE CHANGED

Meet project terms

CLICK ICON TO ADD PICTURE

Meet customer needs

ITS HARD TO MAKE DECISIONS ON THE LATE PHASES

CLICK ICON TO ADD PICTURE

WATERFALL CAN BE APPLIED IN EXTREMELY DIFFICULT PROJECTS

NUCLEAR POWER PLANT, SPACE SHIPS, MEDICINE

AND IN SMALL PROJECTS AS WELL

EXAMPLE: CREATE A SIMPLE WEB-SITE IN MS PROJECT SOFTWARE

T
C
E
J
O
R
P
E
AGIL
T
N
E
M
E
G
A
MAN

AGILE MANIFESTO
INDIVIDUALS AND INTERACTIONS OVER PROCESSES AND TOOLS
WORKING SOFTWARE OVER COMPREHENSIVE DOCUMENTATION
CUSTOMER COLLABORATION OVER CONTRACT NEGOTIATION
RESPONDING TO CHANGE OVER FOLLOWING A PLAN

WHAT IS AGILE PM?

AGILE SOFTWARE DEVELOPMENT IS A GROUP OF SOFTWARE DEVELOPMENT METHODS BASED ON ITERATIVE AND INCREMENTAL
DEVELOPMENT

INCREMENTAL
DEVELOPMENT
A SHIPPABLE SOFTWARE AFTER EACH
ITERATION

Rapid

Adaptable Quality-driven

AGILE
Cooperative Iterative

NOT A PROCESS. ITS A

PHILOSOPHY OR SET
OF VALUES

AGILE UMBRELLA

More
more rules to follow
Prescriptive
RUP (120+)

Agile
Scrum
Crystal

Kanban

RUP has over 30 roles, over 20

activities, and over 70 artifacts

XP (13)
XP
FDD

Scrum (9)
DSDM
Kanban (3)
RUP

and few more

* Check wikipedia for list of all Agile methods

Do Whatever!! (0)

More Adaptive

fewer rules to follow

SCRUM - AGILE SOFTWARE DEVELOPMENT METHODOLOGY

Product backlog

Sprint backlog

THE MAIN AGILE ARTIFACTS

Sprint demonstration

Retrospective

SCRUM KEY ROLES

PRODUCT BACKLOG IS AN ORDERED LIST OF "REQUIREMENTS"

THAT IS MAINTAINED FOR A PRODUCT

REQUIREMENTS TYPES
THEME - IS A COLLECTION OF USER STORIES
EPIC - IS JUST A LABEL WE APPLY TO A LARGE STORY
USER STORY - IS SIMPLY SOMETHING A USER WANTS

USER STORY EXAMPLE:

AS A CUSTOMER I WANT TO ADD A PRODUCT IN CART
AS A CUSTOMER I WANT TO PAY VIA PAYPAL
AS A CUSTOMER I WANT TO HAVE DHL SHIPPING OPTION
AS A CUSTOMER I WANT TO ADD ITEMS IN WISH LIST
AS A SALES PERSON I WANT TO SEE THE MOST POPULAR ITEMS IN WISH LISTS

HOW TO CREATE A PRODUCT BACKLOG

Workshop

Interview

Questionnaire

Prototyping

Observation

TIPS AND TRICKS

FOCUS ON WIDE RANGE RATHER ON DEEP ANALYSIS
ENSURE THAT PRODUCT BACKLOG COVERS ALL APPLICATION
DONT FORGET ABOUT NON-FUNCTIONAL REQUIREMENTS
PERFORMANCE
QUALITY
SCALABILITY

PRIORITIZE BACKLOG
M.O.S.C.O.W
FEATURE BUYING
BUSINESS VALUE BASED
TECHNOLOGY RISK BASED
WALKING SKELETON

M.O.S.C.O.W
M

Must have

Should have

Could have

Wont have this time

CLICK ICON TO ADD

PICTURE

USER STORY DETALIZATION

SMALL AND DETAILED STORIES ON THE TOP
LARGE SIZE AND ROUGH STORIES ON THE BOTTOM

USER STORIES DETALIZATION LEVEL

ACCEPTANCE TESTS
USE CASES
PROTOTYPES
VISUALIZATION

THE PRODUCT BACKLOG EXAMPLE:

ACCEPTANCE TEST EXAMPLE:

AS A USER I CAN REQUEST MY PASSWORD RECOVERY
ACCEPTANCE TESTS:

1.
2.
3.
4.

ERROR MESSAGE WHEN USER IS NOT FOUND

ERROR MESSAGE WHEN USER NAME HAS IMPROPRIATE SYMBOLS
IF I ENTER VALID E-MAIL OR USER NAME THE MAIL WITH PASSWORD RECOVERY LINK IS SENT
THE LINK ON THE EMAIL ADDRESS REFERS ON A PASSWORD RECOVERY PAGE (SEPARATE US)

SPRINT
AN ITERATION OF WORK DURING WHICH AN INCREMENT OF PRODUCT FUNCTIONALITY IS IMPLEMENTED.
DURATION 2-4 WEEKS

SPRINT PLANNING

DONT FORGET TO SET SPRINT GOALS!

TEAM VELOCITY
IS HOW MUCH PRODUCT BACKLOG EFFORT A TEAM CAN HANDLE IN ONE SPRINT.
CAN BE MEASURED BY:

STORY POINTS
IDEAL MEN DAYS
US AMOUNT

THE BEST METHOD TO ESTIMATE VELOCITY IS BASED ON PREVIOUS ITERATIONS VELOCITY

VELOCITY BASED APPROACH

TEAM ESTIMATE ITS VELOCITY
FEATURES WITH THE HIGHEST PRIORITY IS DISCUSSED AND ESTIMATED
THE PROCEDURE GO ON UNTIL SPRINT BACKLOG IS FULFILLED

SPRINT PLANNING ATTENDEES

PRODUCT OWNER
SCRUM MASTER
TEAM

USER STORY ESTIMATION TECHNIQUES

PLANNING POKER
TEAM ESTIMATION GAME

PLANNING POKER

PLANNING POKER RULES

PRODUCT OWNER READ USER STORY AND ACCEPTANCE TESTS
TEAM IS ASKING QUESTION AND SPLIT US TO TASKS
IF EVERYTHING IS CLEAR TEAM SHOW ESTIMATION CARDS
IF VARIANCE BETWEEN ESTIMATES IS TOO BIG , SCRUM MASTER ASKS WHY IT HAPPENED
GAME IS REPEATED

TEAM ESTIMATION GAME

DAILY SCRUM MEETINGS

3 QUESTIONS TO ASK:

WHAT DID I ACCOMPLISH YESTERDAY?

WHAT WILL I DO TODAY?
WHAT OBSTACLES ARE IMPEDING MY
PROGRESS?

SCRUM BOARD

REAL ONE

SCRUM BURNDOWN CHART

WE ARE LATE!

WE ARE UNDER SCHEDULE

DEMONSTRATION
EVERYBODY IS WELCOME
TEAM MEMBER DEMONSTRATES US DVELOPED BY HIMSELF
CUSTOMER ACCEPT A PRODUCT

MEASURE FOCUS FACTOR

FOCUS FACTOR = ACTUAL VELOCITY / CAPACITY
CAPACITY = TEAM MEMBERS AMOUNT X 40 HOURS X WEEKS AMOUNT

RETROSPECTIVE MEETING

SELECT 2-5 THE MOST IMPORTANT IMPROVEMENTS

SET RESPONSIBLE PERSON PER EACH ONE

PUT IMPROVEMENTS ON THE NEXT TASK BOARD
DONT FORGET TO INCLUDE ESTIMATES IN THE NEXT SPRINT PLANNING

QUESTIONS?
MICHAEL.SIBUG@GMAIL.COM
WWW.UXI.ROCKS