The basics of Agile and Waterfall Project management methodologies. Description when each approach can be applied. Advices How to create a Product backlog and how to colect requirements. Sprint planning, Burndown chart, Demonstration, Retrospective, Tasks board examples.

2. ABOUT ME
KOSTIANTYN TREFIAK
CERTIFIED PROJECT MANAGER, PMP
PRODUCT OWNER
BUSINESS ANALYST
CMS/WEB 2.0/E-COMMERCE
E-MAIL: KOSTIANTYN.TREFIAK@GMAIL.COM

3. WATERFALL MODEL
THE WATERFALL MODEL IS A SEQUENTIAL DESIGN PROCESS
Testing and Build
Maintenance
System design
Development
Requirements

4. WATERFALL ARTIFACTS
WATERFALL PROCESS REQUIRES TONS OF DOCS!
Software
requirement
specification
Software
architecture
document
Software QA
Plan
Test results
report

5. PLANNING AND SYSTEM DESIGN TAKES A LOT OF EFFORT AND TIME
Requirements Architecture and design Development Testing Build
2013 2013 2014 2015 2016

6. CHANGE REQUESTS MAY OCCUR DURING LATE PHASES
Requirements Architecture design Development Testing Build
2013 2013 2013 2014 2015

7. CHANGES HAVE SIGNIFICANT IMPACT ON PROJECT SUCCESS
EACH DOCUMENT MIGHT BE CHANGED

8. IT’S HARD TO MAKE DECISIONS ON THE LATE PHASES
Meet customer needs Meet project terms

9. WATERFALL CAN BE APPLIED IN EXTREMELY DIFFICULT PROJECTS
NUCLEAR POWER PLANT, SPACE SHIPS, MEDICINE

10. AND IN SMALL PROJECTS AS WELL

11. EXAMPLE
CREATE A SIMPLE WEB-SITE IN MS PROJECT SOFTWARE

13. 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

14. WHAT IS AGILE PM?
AGILE SOFTWARE DEVELOPMENT IS A GROUP OF SOFTWARE DEVELOPMENT METHODS BASED ON ITERATIVE AND INCREMENTAL
DEVELOPMENT

15. INCREMENTAL
DEVELOPMENT
A SHIPPABLE SOFTWARE AFTER EACH
ITERATION

16. SCRUM - AGILE SOFTWARE DEVELOPMENT METHODOLOGY

18. THE MAIN AGILE ARTIFACTS
Product backlog Sprint backlog Sprint demonstration Retrospective

19. SCRUM KEY ROLES

20. PRODUCT BACKLOG -
IS AN ORDERED LIST OF "REQUIREMENTS"
THAT IS MAINTAINED FOR A PRODUCT

21. 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

23. 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

24. HOW TO CREATE A PRODUCT BACKLOG
Workshop Interview Questionnaire Prototyping Observation

25. TIPS AND TRICKS
• FOCUS ON WIDE RANGE RATHER ON DEEP ANALYSIS
• ENSURE THAT PRODUCT BACKLOG COVERS ALL APPLICATION
• DON’T FORGET ABOUT NON-FUNCTIONAL REQUIREMENTS
• PERFORMANCE
• QUALITY
• SCALABILITY

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

28. M.O.S.C.O.W
Must haveM
Should haveS
Could haveC
Won’t have this timeW

29. USER STORY DETALIZATION
SMALL AND DETAILED STORIES ON THE TOP
LARGE SIZE AND ROUGH STORIES ON THE BOTTOM

30. USER STORIES DETALIZATION LEVEL
• ACCEPTANCE TESTS
• USE CASES
• PROTOTYPES
• VISUALIZATION

31. THE PRODUCT BACKLOG EXAMPLE:

32. ACCEPTANCE TEST EXAMPLE:
AS A USER I CAN REQUEST MY PASSWORD RECOVERY
ACCEPTANCE TESTS:
1. ERROR MESSAGE WHEN USER IS NOT FOUND
2. ERROR MESSAGE WHEN USER NAME HAS IMPROPRIATE SYMBOLS
3. IF I ENTER VALID E-MAIL OR USER NAME – THE MAIL WITH PASSWORD RECOVERY LINK IS SENT
4. THE LINK ON THE EMAIL ADDRESS REFERS ON A PASSWORD RECOVERY PAGE (SEPARATE US)

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

34. SPRINT PLANNING

35. DON’T FORGET TO SET SPRINT GOALS!

36. 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

37. VELOCITY BASED APPROACH
• TEAM ESTIMATE IT’S VELOCITY
• FEATURES WITH THE HIGHEST PRIORITY IS DISCUSSED AND ESTIMATED
• THE PROCEDURE GO ON UNTIL SPRINT BACKLOG IS FULFILLED

38. SPRINT PLANNING ATTENDEES
• PRODUCT OWNER
• SCRUM MASTER
• TEAM

39. USER STORY ESTIMATION TECHNIQUES
• PLANNING POKER
• TEAM ESTIMATION GAME

40. PLANNING POKER

41. 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

42. TEAM ESTIMATION GAME

43. DAILY SCRUM MEETINGS
3 QUESTIONS TO ASK:
• WHAT DID I ACCOMPLISH YESTERDAY?
• WHAT WILL I DO TODAY?
• WHAT OBSTACLES ARE IMPEDING MY
PROGRESS?

44. SCRUM BOARD

45. REAL ONE

46. SCRUM BURNDOWN CHART

47. WE ARE LATE!

48. WE ARE UNDER SCHEDULE

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

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

51. RETROSPECTIVE MEETING

52. SELECT 2-5 THE MOST IMPORTANT
IMPROVEMENTS
• SET RESPONSIBLE PERSON PER EACH ONE
• PUT IMPROVEMENTS ON THE NEXT TASK BOARD
• DON’T FORGET TO INCLUDE ESTIMATES IN THE NEXT SPRINT PLANNING

53. QUESTIONS?