My slides from Kyiv Project Management Club event related to Risks. How to manage common software projects risks in Agile

1. FAIL = First Attempt In
Learning. Fail Fast - Learn
Fast in Agile
ARTEM BYKOVETS
(AGILE COACH & CONSULTANT)

2. Few words about myself
• Managing Partner / Agile Coach at SimpleSense
• CEO and coach/mentor at "StartIT”
• CSM, CSPO, CSP, CAL-1 by Scrum Alliance
• Certified Kanban System Design (KMP I) by LKU.
• Best QA specialist of Ukraine by IT Awards 2015
• “Software quality and testing” lecturer at KPI
• Guest lecturer at KMBS
• Happy father of Sophiia J

3. Кто работает в Agile?

4. КАК ОБЫЧНО ПРЕДСТАВЛЯЮТ СЕБЕ RISK MANAGEMENT
В AGILE
Я стикером пометил…
на Ретроспективе
обсудим

5. WHAT WILL YOU DO WHEN YOU LEARN SOMEONE WAS WRONG?
Agile makes changing your mind legal.

6. FIVE TYPES OF SOFTWARE DEVELOPMENT RISK
1. Budget Risk
2. Personnel Risk
3. Knowledge Risk
4. Productivity Risk
5. Time Risk

7. BUDGET RISK
the risk of projects going over budget. Perhaps the most common risk in software
development and often tied to other risks.
Solution: Rolling Wave Planning 1. FOCUS ON URGENT
2. ESTIMATED BY TEAM
3. ABLE TO CHANGE
PLAN
4. RELEASE MVP
5. MAYBE PIVOT

8. PERSONNEL AND KNOWLEDGE RISKS
Personnel Risk: the risk of losing or absence of project team members. Even if for a short
period, this can result in delays and errors.
Knowledge Risk: when there are knowledge silos or the transfer of information is imperfect.
The process of relearning results in additional labor, time, and resources
Solution:
Squad-based
development

9. SOLUTION: WORK FROM SINGLE PRIORITISED BACKLOG

10. RISK – PRODUCTIVITY
this risk is common in long projects, mainly when deadlines and goals are long-term. This
environment creates a lack of immediacy which results in a lack of urgency of work.
Solution: Sprint Development 1. Definition of Done
2. Transparency
3. Deadline every few
weeks J
4. Regular feedback
5. Regular daily sync
6. Retrospective for
improvement

11. RISK – TIME
product delays are all-too-common in software development, typically the results of poor
planning, unrealistic timelines, and the inability to adapt to changing product requirements
Solution: TIMEBOX + INSPECT&ADAPT
1. Whole team planning
2. Regular increment review
3. Flexibility on
Acceptance criteria's
4. Decomposition of big things
5. Strong timeboxing
6. Engineering culture

12. UNDERSTANDING GROWS CONTINUOUSLY
Scope
Time Budget
expectation reality

13. REVERSING IRON TRIANGLE
Scope
Time Budget
Plan
Driven
[Time] [Budget]
Scope
Value
Driven

14. KAIZEN
CONTINUOUS PROCESS IMPROVEMENTS

15. KAIZEN IS COMING
PMCLUB10 – 10%
discount ;)

16. Contacts:
My site: www.abykovets.com
Linkedin: https://linkedin.com/in/abykovets/
Facebook: https://facebook.com/artem.bykovets
Mail: artem@simplesense.com.ua
+38 063 495 36 22