Agile Drupal Development with Scrum. 27. November 2009 Philipp Schroeder, Liip AG

Transcription

1 Agile Drupal Development with Scrum 27. November 2009 Philipp Schroeder, Liip AG

2 A brief introduction to Scrum Benefits of Scrum from - a company s point of view and - a freelancer s point of view

3 Philipp Schroeder Project manager at Liip AG, Switzerland My Co-presenter at DrupalCon Paris 2009: Mori Sugimoto Freelance Drupal consultant / developer, UK

4 We are not expert ScrumMasters, but we find Scrum very useful and want to share our experience. Please feel free to fill in.

5 What is Scrum? A process skeleton designed to deliver a product incrementally in smaller components, (rather than in one big chunk)

6 Why Scrum? Web 2.0 Social Networking Micro blogging X$$$ Let me try out Panels 3, please Client Sales Developer

7 Why Scrum? Let's build the best website for $ XXXXX Client Developer

8 A developer s story My clients often come to me with a set budget with lots of features, as soon as possible I don't want to make false assumptions about what I can deliver for that budget Yet, I want to do work and get paid Scrum helps achieving this

9 Scrum helps... clients focus on crucial features clients to become realistic about what can be achieved developers work in a self-organised way to collaboratively explore and find the right solution to keep building the solution at a fast pace

10 How does Scrum work?

11 In the beginning: The product backlog

12 Product backlog ID Story Importance 1 As an editor, I want to have an easy-to-use text editor As a potential investor, I want to read the organisation s achievements As a visitor, I want to see an animation of a cheerful mouse waving in the home page

13 Process of Scrum Sprint retrospective Delivery / Sprint review Product Backlog (requirements) Sprint planning Development End of project (goal achieved / budget run down) 24hrs 1 iteration = 1 Sprint = 2 weeks to 1 month

14 Scrum Master as facilitator

15 Everything is a timebox Sprint Daily Scrum meeting Planning / review / retrospective meetings

16 Every sprint, we have an increment of working software

17 Roles in Scrum

18 A chicken and a pig open a restaurant...

19

20 User stories As [role], I want [functionality] to achieve [goal]

21 Story points / Sprint planning

22 Planning poker

23 Strengths of Scrum from a company s point of view

24 Integrated team work, direct communication

25 Integrated team work - see: Scrum roles

26 high bandwidth communication

27 Client and provider grow with the project

28 Personally Rewarding

29 Strengths of Scrum from a freelancer s point of view

30 From a freelancer s perspective: Makes your life easier :) It s pay as you go Project duration and scope entirely depends on the budget Client become aware of the cost implication of their requests

31 From a freelancer s perspective: Quotes based on detailed specification is no longer necessary

32 From a freelancer s perspective: Scrum techniques work well even for the smallest project Product (=sprint) backlog Scrum meeting

33 Weaknesses of Scrum from a company s point of view

34 Managing dependencies

35 Granularity of user stories

36 Managing client's expectations

37 Expectations vs. Drupal community development power :-)

38 Integration with UX / Design process

39 Weaknesses of Scrum from a freelancer s point of view

40 There are hidden costs Communication overhead Project facilitation Setting up dev environment Site launch

41 If the project is relatively small, you can't afford to refine iteratively

42 Smaller organisations suffer from high communication overhead

43 Tips

44 Project initialisation

45 Exploration stories

46 Writing User Stories with Drupal in mind

47 Merci!

48 Questions?