Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Hvorfor arbejde med agil udvikling når du arbejder med web?

466 views

Published on

Gennemgang af hvad det vil sige at arbejde agilt og hvorfor det kan være en fordel - både for leverandøren og kunden.

Published in: Technology
  • Be the first to comment

Hvorfor arbejde med agil udvikling når du arbejder med web?

  1. 1. Estimation: from waterfall to agile Mikkel Bo Hansen, Strategic Client Manager
  2. 2. Agenda ● Who is Adapt? ● Why agile? ● Estimation ● Results ● Where is the Client? ● Questions
  3. 3. Who is
  4. 4. is a digital agency that unites business understanding, design and technology
  5. 5. ● We create solid results for leading international brands (since 1998) ● Experience with launching 2000+ digital solutions ● 80+ passionate employees ● We unite business understanding, design and technology ● You are not just another project. You are a part of a team.
  6. 6. Offices in Copenhagen, Kaunas, Vilnius, Barcelona & Boston LOCATIONS
  7. 7. Strategy, insights & design Web Business analysis User Experience User surveys Visual identity / design Go-to-market strategy Concept Mobile strategy Developing apps for: Business Promotions Social media Games IOS, Android, Windows Usability testing Think-aloud-tests Focus groups Concept testing Eye tracking Brand perception Card sorting Personas MobileE-commerce SERVICES Complete e-commerce platforms Integration (ERP, CRM, PIM) Omni channel Personalization Customer engagement Corporate sites Campaign sites Intranet Extranet Backend systems
  8. 8. Mikkel Bo Hansen Strategic Client Manager Mail: mbh@adapt.dk ● Copenhagen Business School ● Cand.Merc.dat ● (+DTU 2 years) ● PHP programmer (not drupal) ● Specialised in… ○ Agile Methods ○ UX
  9. 9. Why did we go agile We’ve tripled both in company size and average project size over the last three years From our own developed Perl platform to developing on a global platform that is moving all the time Agile methods has become acknowledged as the optimal method for software development.
  10. 10. Design Specification Implementing Integration Test Installation Maintenance Waterfall approach
  11. 11. Why agile?
  12. 12. SCRUM Kanban XP LEAN
  13. 13. anno 2001 Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan The Manifesto
  14. 14. Design Specification Implementing Integration Test Installation Maintenance 2-4 weeks The Iterative Model
  15. 15. Build what you need Never used Always Often Sometimes Rarely
  16. 16. Create the product that the user needs. And do it fast! Test - Build - Adjust
  17. 17. User Stories Condition I must be able to change my email I need to see a sorted list of products I must be able to create a ticket to the system admins I must be able to register a bug Perspective As an editor As a new user As a teacher As a registered customer Value Statement So that I am always updated with the latest info So that I don’t need to contact an administrator So that I don’t need to spend time filling out all information every time. As a <type of user>, I want <some goal>, so that <some reason>
  18. 18. As a <type of user>, I want <some goal> so that <reason>. User Story Backlog The Backlog Sprint 2-4 weeks Product Owner Scrum Master
  19. 19. Estimation Fortune telling
  20. 20. We tend to break down tasks and estimate the subtasks when we have the least knowledge! Time Uncertainty + - - Task Breakdown - Estimating Time - Risk - Knowledge
  21. 21. Scope Buffer How can I know something that I don’t?! You can’t!!! But you can know that you don’t know it! …. and you can accept it User Story 1 User Story 2 User Story 3 User Story 7User Story 4 User Story 5 User Story 6 Scope Buffer User Story 1 User Story 2 User Story 3 User Story 7User Story 4 User Story 5 User Story 6 Total Budget …. and THEN make it work for you! Scope Buffer User Story 1 User Story 2 User Story 3 User Story 7User Story 4 User Story 5 User Story 6 Time Know what you don’t know
  22. 22. Story points vs time ● “How complicated is the task compared to the other task” ● It is way easier for the human brain to compare two elements than describe an isolated element ● Gives more valid estimates How to handle what you don’t know? So how long will it take to do this? I don’t know…. 150-250 hours from what i know now Ok so 150 hours ! VS ● The value of the Story Points will be variable through the project. (only a problem if you forget it!) Story Points
  23. 23. Which one will take the longest time? ? How long will it take to assemble? (No, we don’t have the manual) ? x4 x16 x32 x8 x2
  24. 24. The great guessing game! So we have the user story [...] 5 8 5 3 13 We need to make a lot of customisation and create our own modules But there are some good modules that can solve 95% of the wishes out of the box. 5 8 8 5 8 8 it is! Planning Poker
  25. 25. 63 hours Backlog The Backlog 8 12 2 4 4 15 8 21 8 15 8 13 21 8 8 5 13 8 13 4 8 2 33 SP Story Points = 1,9 Velocity Budget: 150 hours / 1,9 = 79 SP Business value
  26. 26. Results
  27. 27. Accurate estimation When estimating tasks at sprint startup we bring our learnings from the project so far into consideration When doing planning poker as a team we support knowledge sharing. This also makes the estimates more precise since we commit to the story point as a team.
  28. 28. But there’s always a but Implementing agile methods is hard work. Get the customer on board Some customers are simply not ready for agile On smaller projects it can be difficult to implement - Not enough time to learn
  29. 29. No two organisations are the same! Customize! One slide to rule them all
  30. 30. Where is the customer???
  31. 31. Right in the middle
  32. 32. Knowledge is needed As a <type of user>, I want <some goal> so that <reason>. User Story Backlog Sprint
  33. 33. Role of the customer Adding business value Close relation to Product Owner (maybe even be the product owner) Sorting the Backlog Testing
  34. 34. Do you have any questions?
  35. 35. Upcoming events 18. November 2015: “Kom til tops i Google med Søgemaskineoptimering” 27. Januar 2016: “Optimer din forretning med fokus på konvertering” Hvis du ønsker at høre mere om vores kommende events kan du tilmelde dig vores nyhedsbrev på adapt.dk eller efterlade dit visitkort Hjælp os med at blive bedre. I vil efter præsentationen modtage en anmodning om at give feedback på præsentationen
  36. 36. Mikkel Bo Hansen Strategic Client Manager Mail: mbh@adapt.dk

×