Agile

500 views
466 views

Published on

Published in: Technology, Self Improvement
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
500
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
14
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • You’re limiting your audience straight away.\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Agile

    1. 1. Agile(in a dramatically contrived metaphorical context.)
    2. 2. A quick introWhat is Agile, and why do people use it?Different types of AgileAgile in designPerception of Agile
    3. 3. Just like a chef.
    4. 4. An chef would...Come up with some awesome recipes.Write a shopping listDo the shoppingPut it in the fridgePrep your meals.Get cookin’Serve your meals.Do a ‘Masterchef’.
    5. 5. Come up with some tasty recipes.Taste is always the main goal. ... but you don’t know what it tastes like yet.Some people hate cheese.
    6. 6. Write a shopping listYou roughly know what you wantYou don’t make too many choices before you go shopping
    7. 7. Do the shoppingYou go down your listYou decide which ingredients to getHow many calories?You expect a certain quality
    8. 8. Put it in the fridgeIt’s time to organise all that stuff you got.Best before dates. Utilise your cupboards, fridge and freezer.
    9. 9. Prep your mealsYou get all your necessary ingredients together.You might be making more than one course at once.Delegate the tasks to the other chefs.Everyone has their own chopping board.
    10. 10. Get cookin’The fun bit for the chefs.We know how long it should be takingPass it on if you need to.Do some taste-tests as you go along.
    11. 11. Serve your mealsPresentation is keyMake sure it’s cooked all the way throughOne course at a time.There’s (normally) room for dessert.Don’t speak with your mouth full!
    12. 12. Do a ‘Masterchef’So, everyone has had a taste.Let’s decide what was good, and what was bad.
    13. 13. An agile team would...Come up with some amazing ideasWrite some user storiesDevelop your user storiesTransfer to the backlogPrepare the sprintGet codingDemo your productHave a Retrospective meeting
    14. 14. Come up with some amazing ideas.It always starts with the idea... ... but it’s only an idea at this point.Changing over timeSetting your audience boundaries early
    15. 15. Write some user storiesWrite as many user stories down as you canFocus on the story narratives, rather than the criteria.
    16. 16. Story NarrativeAs a [role]...I want [something]...So that [benefit].
    17. 17. Story NarrativeAs a provider search user..I want to search for providers by speciality...so that I can efficiently refer patients to specialists.
    18. 18. Story Narrative
    19. 19. Develop your storiesDiscuss each story with your teamWrite acceptance criteria for each story Make sure you mutually agree the ‘definition of done’Watch out for ‘Epics’.Estimate each storyPrioritise your stories
    20. 20. Acceptance CriteriaGiven [...]When [...]Then [...]
    21. 21. Acceptance CriteriaGiven the user is on either the homepage or results pageWhen the users clicks “Search”Then the they are given a list of providers.
    22. 22. Acceptance Criteria
    23. 23. Transfer to the backlogYou’ve written your detailed user storiesIt’s time to transfer these to the appropriate places.Use the backlog for most things... ... but the “Icebox” is useful for stories that can wait.First indication of the project length
    24. 24. Prepare the sprintSprints begin with a meetingSprints usually last 2 weeksMake sure all user stories have an ownerThe team can view their tasks for the sprintMake sure clients have agreed
    25. 25. Get codingThe fun bit for developersWe know how long to spend on storiesCollaborationTest-Driven Development
    26. 26. Demo your productDemo the latest features to the product owner.Only include fully working featuresRun through 1 each feature at a time.End on a highWait to give your full opinion
    27. 27. Do a retrospectiveRetrospectives happen at the end of every sprintWe discuss: What went well What went wrong How we can improve
    28. 28. The ReleasesIt’s different to Masterchef.It’s more like releasing a recipe book.Only when the product is usable and has sufficient featuresUsers will make it their own. Everyone has different tastes.
    29. 29. Daily ScrumsIn the morning, we should have a meetingWe need to stand-up. (Sometimes called “stand-ups”)Only 1 person talks at once (using a prop?)We need to discuss: What we’ve been up to What we’re about to do And what/who we need to achieve that.
    30. 30. ClientsFixed pricingClient participationContract definition“Money for nothing...... change for free”
    31. 31. Client ParticipationExpected to participate in: Prioritising features, for implementation order Sprint planning meetings Acceptance criteria Retrospectives
    32. 32. Contract DefinitionThings to ensure are defined in the contract: Total value of the contract Rates for times & material billing Scope of the contract
    33. 33. Money for nothingClient may terminate at the end of a sprint Would pay 20% of the remaining contract valueWhat can we commit to?Client must participate! Resort to T&M billing
    34. 34. Change for free If client is participating...they can make changes to the scope... as long as stories of equal scope are removed from thecontract.
    35. 35. Cheers.Any questions?

    ×