Versions Compared

Old Version 2

changes.mady.by.user Benjamin Armintor

Saved on

compared with

New Version Current

changes.mady.by.user Andrew Woods

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Process for using

...

JIRA

  1. The

...

  1. REPORTER of a story is responsible for providing criteria

...

  1. for CLOSing a story. For code implementation stories, this includes provision of a test.
  2. Once the story has been evaluatued to be worked, it is moved from the RECEIVED state to the OPEN state.
  3. The

...

  1. ASSIGNEE of a story STARTs WORK on the story.
  2. The

...

  1. ASSIGNEE of a story STARTs

...

  • A story can be in the ICEBOX without delivery criteria, but it must have an requester.
  • A story can be in the BACKLOG without an owner, but it must have delivery criteria. A story cannot be in the Backlog until the Product Owner has accepted it. A story cannot be Started until it has been assigned to a sprint.
  • A story cannot be in a SPRINT without a requester, delivery criteria, and an owner.
ICEBOX

...

  1. REVIEW of the story when the work is completed. 
    1. When putting the ticket into REVIEW, a link to the GitHub pull-request should also be included in the ticket
    2. Note, the ASSIGNEE should STOP WORK on a story if they are temporarily changing focus to a different task.
  2. The REPORTER (and/or the Tech Lead) reviews/tests the finished code. Then either CLOSEs or REOPENs the story depending on the outcome of the review.
  3. Once a story is CLOSED, the Tech Lead (or delegate thereof) merges the code into the codebase.

JIRA Workflow

Image Added

Example
  1. Jonathan requests the Glacier Mock story. It goes into the RECEIVED state.  It has no assignee. It has no acceptance criteria.
  2. At the sprint planning meeting, we assign acceptance criteria and move the story to the OPEN statue. The story has no assignee to do the work.
  3. If the story goes into the current sprint, it may not have an assignee (Don't assign assignee to stories outside sprints!).
  4. At the next daily scrum, Chris decides to work on this story. He STARTs WORK on the story, and makes himself the assignee.
  5. 3 hours later, Chris is done with the work, makes a pull request, and moves the ticket to IN REVIEW.
  6. Jonathan (the reporter) reviews the pull request (runs tests, etc.). When Jonathan thinks the ticket is complete, he accepts the pull request and moves the ticket to CLOSED.
  7. If the work is subsequently revealed to be incomplete, the Tech Lead REOPENs the story.
Terms
  • BACKLOG
    • Stories that have been accepted are moved to the Backlog.
  • SPRINTS
    • Stories that have been started must be moved to a sprint.  Stories are finished and delivered in sprints.
Pivotal Tracker States

...

Process for implementing a fix or feature

  1. Start work on the ticket in JIRA
  2. Create an issue branch in your local git
  3. When you believe the ticket is complete, push the issue branch to github
  4. Send a pull request to master linking the JIRA ticket in the description
  5. Link the JIRA ticket to the pull request or commit
  6. Link the pull request to the JIRA ticket
  7. Move the JIRA ticket to IN REVIEW
  8. The reporter should review the change and, if it appears to be complete (including at minimum Integration and Unit Test coverage) move the ticket into CLOSED.
  9. The reporter should delete the issue branch in github
  10. The PM or Tech Lead should evaluate the demo and Accept/Reject the ticket

...