1. www.ciklum.net
Scrum and Kanban in Action
Vladimir Gorshunov
Ciklum Services & Consulting (CSC)

2. Consultant profile
Vladimir Gorshunov
• Ciklum Technical Consultant
• Agile Coach, Scrum Master
• Experienced Agile Project Manager with
technical background
Vladimir has more then 8 years in software development and for 4 years he
is building efficient distributed agile teams, which are able to deliver
business value on-time and on-target using best industry practices.
Vladimir expert with Java technical background and has been involved in
different projects from the variety of business domains (Banking
Solutions, Mobile Development, High Loading Computation, Payment
Systems, Customer Experience Management, Government Systems, etc.)
www.ciklum.net

3. Two stories…
www.ciklum.net 3

4. First story…
www.ciklum.net 4

5. What is mobile development for
YOU?
www.ciklum.net 5

6. What is mobile development?
 Less that 3-4 people in the team
 Too much overhead with all the meetings - actually
wastes time
 Very short projects
 Not enough time to adapt if the initial plans aren’t very
accurate
www.ciklum.net 6

7. What is mobile development?
 Can’t keep fully dedicated QA for one project
 QA is a shared resource, sometime event remote
resource
 Even developers are shared between projects!
 Just do it! ASAP!
 Client don’t care about your internal process, he need
a product
www.ciklum.net 7

8. Scrum practices (9)
 Scrum Master
 Product Owner
 Team
 Sprint planning meeting
 Daily Scrum
 Sprint review
 Product backlog
 Sprint backlog
 Burndown chart
www.ciklum.net 8

9. Scrum doesn't fit all
www.ciklum.net 9

10. Kanban practices (3)
 Visualize the work flow (Board)
 Limit WIP (work in progress)
 Measure and optimize lead time (cycle time)
www.ciklum.net 10

11. Kanban doesn't fit all
www.ciklum.net 11

12. Scrum vs Kanban?
We can use them together!
www.ciklum.net 12

13. Scrum + Kanban in mobile dev
 Less that 3-4 people in the team
 Too much overhead with all the meetings - actually wastes
time
Keep daily meeting, planning and demo, process
improvement can be during all process or you can have
retrospective at the end of 2 sprints instead of one.
 Very short projects
 Not enough time to adapt if the initial plans aren’t very
accurate
www.ciklum.net 13

14. Scrum + Kanban in mobile dev
 Very short projects
 Not enough time to adapt if the initial plans aren’t very
accurate
You can use 1 week sprint instead of long 2-3 week
sprint. You can even make demo or provide demo build
two times per week.
You develop many projects, so you can adopt you
process across all of your projects.
www.ciklum.net 14

15. Scrum + Kanban in mobile dev
 Can’t keep fully dedicated QA for one project
 QA is a shared resource, sometime event remote resource
Include QA in common process, and in visualization process
especially
www.ciklum.net 15

16. Scrum + Kanban in mobile dev
 Even developers are shared between projects
Limit WIP
Adopt your process in all your projects
Visualize the workflow
www.ciklum.net 16

17. Scrum + Kanban in mobile dev
 Just do it! ASAP!
 Client don’t care about your internal process, he need a
product
 That is TRUE!!!
 Be proactive, explain AGILE way of doing think
www.ciklum.net 17

18. Second story…
www.ciklum.net 18

19. What is NEW product development
for YOU?
www.ciklum.net 19

20. What is new product development?
 There are a lot of ideas from business.
 Hard to determinate how much developers
we ready need.
 Let’s use what we used before!
www.ciklum.net 20

21. What is new product development?
 Let’s start for a “green field”!
 We need QA only at the end of the project!
 Development team use agile, designers
don’t.
www.ciklum.net 21

22. What is new product development?
 There are a lot of ideas from business.
That is great, isn’t it? Put all ideas in your
backlog, coach or hire Product Owner. Does
your customer have a CTO?
 Hard to determinate how much developers
we ready need.
Scale your team as soon as you will have
enough job them.
www.ciklum.net 22

23. Agile and new product development
 Let’s use what we used before!
Review all your decisions on
retrospectives, some times it can be easier
to use new solution instead of adopting an
old one.
 Let’s start for a “green field”!
Please, be pragmatic, use existed
solutions and practices.
www.ciklum.net 23

24. Agile and new product development
 We need QA only at the end of the project!
QA in agile team need to test user stories
before they will come to team, good QA will
be a Product Owner assistance.
 Development team use agile, designers
don’t.
Integrate designers in you agile process, stop
think about design as a solid thing.
www.ciklum.net 24

25. Stay hungry, Stay foolish.
Steve Jobs
1955 – 2011
www.ciklum.net 25

26. One size doesn't fit all
Questions?
www.ciklum.net 26