Skip to content

Instantly share code, notes, and snippets.

@coffeencoke
Created February 23, 2012 22:21
Show Gist options
  • Save coffeencoke/1895364 to your computer and use it in GitHub Desktop.
Save coffeencoke/1895364 to your computer and use it in GitHub Desktop.
Agile Cycle List

Agile Cycle

Example "to get started" way to read this:

To begin our process, we start at the planning cycle, do we need stories? if not, go to the Development Cycle. If we do need stories, write stories. If the story is a web story and it needs markup, add to the need markup queue, if it does not need markup, add to the ready to be coded queue. If the story is not a web story but is a mobile support story, and the story needs requirements from the mobile team, add to the need requirements queue. If it does not need requirements, add to the ready to be coded for mobile support queue…

Planning

  • Need Stories
    • Write Stories
      • Web Story
        • Need Markup
          • add to "Need Markup" queue
        • Does Not Need Markup
          • add to "Ready to be Coded" queue
      • Mobile Story
        • Need Services
          • add to "Need Requirements" queue
        • Does not need services
          • add to "Ready to be Coded" queue
  • Does not Need Stories
    • go to Development Cycle

Development Cycle

  • Work on Story
    • Web or Mobile Support Story?
      • y- go to Web or Mobile Support Dev Cycle
      • n- go to Mobile Dev Cycle

Web or Mobile Support Dev Cycle

  • Web Story
    • Needs Markup
      • Develop Markup
    • Code
  • Mobile Support Story
    • Needs Requirements
      • Gather and record requirements
    • Code
  • Code Review
  • Mobile Support Story
    • Deliver story to mobile for Acceptance Testing
      • Does not Pass Mobile team's acceptance criteria
        • can be fixed with a hotfix
          • make a hotfix and redeliver with hotfix
        • can not be fixed with a hotfix
          • go to Planning Cycle
      • go to Mobile Dev Cycle
  • Not Mobile Support Story
    • Deliver story to QA for Acceptance Testing
      • Does not pass acceptance testing
        • can be fixed with a hotfix
          • make a hotfix and redeliver with hotfix
        • can not be fixed with a hotfix
          • go to Planning Cycle
      • Passes acceptance testing add to feature queue
  • Feature
    • Needs more stories before feature can be delivered
      • Wait for more stories
    • Promote stories to a stacked Feature (or features) and deploy for demo
    • Demo to customer
      • Cannot be released
        • can be fixed with a hotfix
          • make a hotfix and redeliver with hotfix
        • can not be fixed with a hotfix
          • go to Planning Cycle
      • Can be released
        • go to Release Cycle

Mobile Dev Cycle

  • Code
  • Feature
    • Feature Complete?
      • n- Wait for more stories
      • y- Promote stories to a stacked Feature (or features) and Move to Mobile Dev Build Release

Mobile Dev Build Release

  • Deploy services for build to demo
  • Deliver build of mobile app to customer
    • Cannot be released
      • go to Planning Cycle
    • Can be released
      • go to Release Cycle

Release Cycle

  • Merge and Deploy API and Web features to staging
  • Build the mobile apps to test against staging
  • Test Web and Mobile against staging
    • Cannot be deployed
      • can be fixed with a hotfix
        • Make a hotfix and redeploy
      • cannot be fixed with a hotfix
        • go to Planning Cycle
  • Deploy to Production
  • Release mobile build
  • Go to Planning Cycle

Concept (napkin style, without napkins)

Kanban Concept

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment