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.
Software
Hibernate ORM layer
Why
(not how)
More flexible
Less time
Better transparency
Concept Requirements Development   Product
takes to
                                  o long


Concept Requirements Development       Product
takes to
                                  o   long


Concept Requirements Development         Product




               ...
An iterative proposal
Plan                 Development




               Concept
 REVIEW




What we need              Get ready
Prototype becomes the
        product
Rapid feedback
Reduced risk
An integrated proposal
Project leader plays
   important role
Worth the investment
Demo




What we need              Development




               Planning
Demo




                Development
GO




     Planning
Backlog
(stuff that we need)
Remove
           Add                patients
             tients
          pa
                                           ...
Ranked by importance
Add notes
                                    Apply
                      Remove
Access                                   ...
Start planning
Set time frame
Team estimates work
Add notes
                                    Apply
                      Remove
Access                                   ...
Build a “sprint” backlog
Add notes
                                    Apply       to patients
                      Remove
Access
                ...
Adjust scope
Add notes
                                    Apply
                      Remove                  to patients
Access
     ...
Change priority. Split.
Project leader’s input is key
Demo




What we need              Development




               Planning
In progress   Done :)
  Access
  control




   Add
  patients




 Remove
 patients




  Apply
syndrome
to patients
Daily meeting
In progress   Done :)
  Access
  control




   Add
  patients




 Remove
 patients




  Apply
syndrome
to patients
In progress   Done :)
  Access
  control




   Add
  patients




 Remove
 patients




  Apply
syndrome
to patients
In progress   Done :)
  Access
  control




   Add
  patients




 Remove
 patients




  Apply
syndrome
to patients
In progress   Done :)
  Access
  control




   Add
  patients




 Remove
 patients




  Apply
syndrome
to patients
In progress   Done :)
  Access
  control




   Add
  patients




 Remove
 patients




  Apply
syndrome
to patients
Demo
Working code
Rapid feedback
Release!
Retrospective
Good. Bad. Ugly.
Forum for change
Demo




What we need              Development




               Planning
20 Minutes with
 Ruby on Rails

                    st July
              ay 31
        Tuesd
               11am
GREENISGOOD.CO.UK
Introduction to Scrum
Introduction to Scrum
Upcoming SlideShare
Loading in …5
×

Introduction to Scrum

7,687 views

Published on

An introduction to the Scrum approach to software development for project leaders.

Published in: Technology, Business

Introduction to Scrum

  1. 1. Software
  2. 2. Hibernate ORM layer
  3. 3. Why (not how)
  4. 4. More flexible
  5. 5. Less time
  6. 6. Better transparency
  7. 7. Concept Requirements Development Product
  8. 8. takes to o long Concept Requirements Development Product
  9. 9. takes to o long Concept Requirements Development Product change these
  10. 10. An iterative proposal
  11. 11. Plan Development Concept REVIEW What we need Get ready
  12. 12. Prototype becomes the product
  13. 13. Rapid feedback
  14. 14. Reduced risk
  15. 15. An integrated proposal
  16. 16. Project leader plays important role
  17. 17. Worth the investment
  18. 18. Demo What we need Development Planning
  19. 19. Demo Development GO Planning
  20. 20. Backlog (stuff that we need)
  21. 21. Remove Add patients tients pa Apply mptoms sy o patients t Access control Attach Add notes images to to patients patients
  22. 22. Ranked by importance
  23. 23. Add notes Apply Remove Access s to patients symptom Add patients control tients o patients pa t High Low
  24. 24. Start planning
  25. 25. Set time frame
  26. 26. Team estimates work
  27. 27. Add notes Apply Remove Access s to patients symptom Add patients control tients o patients pa t 10 days 3 days 3 days 7 days 10 days 13 days 16 days 23 days 35 days
  28. 28. Build a “sprint” backlog
  29. 29. Add notes Apply to patients Remove Access mptoms Add patients sy control tients o patients pa t 10 days 3 days 3 days 7 days 10 days 13 days 16 days 23 days 35 days
  30. 30. Adjust scope
  31. 31. Add notes Apply Remove to patients Access ndrome Add patients sy control tients o patients pa t 10 days 3 days 3 days 3 days 10 days 13 days 16 days 19 days 29 days
  32. 32. Change priority. Split.
  33. 33. Project leader’s input is key
  34. 34. Demo What we need Development Planning
  35. 35. In progress Done :) Access control Add patients Remove patients Apply syndrome to patients
  36. 36. Daily meeting
  37. 37. In progress Done :) Access control Add patients Remove patients Apply syndrome to patients
  38. 38. In progress Done :) Access control Add patients Remove patients Apply syndrome to patients
  39. 39. In progress Done :) Access control Add patients Remove patients Apply syndrome to patients
  40. 40. In progress Done :) Access control Add patients Remove patients Apply syndrome to patients
  41. 41. In progress Done :) Access control Add patients Remove patients Apply syndrome to patients
  42. 42. Demo
  43. 43. Working code
  44. 44. Rapid feedback
  45. 45. Release!
  46. 46. Retrospective
  47. 47. Good. Bad. Ugly.
  48. 48. Forum for change
  49. 49. Demo What we need Development Planning
  50. 50. 20 Minutes with Ruby on Rails st July ay 31 Tuesd 11am
  51. 51. GREENISGOOD.CO.UK

×