jiraagilegreenhopper

Atlassian GreenHopper and Release Management

We are playing around with Atlassian products and I have prepared an agile sprint using GreenHopper, and little confused with the flow.

Here is how we are doing the current development at my office:

  1. Developers completes the issues assigned to them. Mark them as resolved.

  2. Once all the issues for the sprint is complete we have a release ticket that provides the release details and we assign it to the INF team to build and deploy in QA. If things are approved in QA its moved to staging, produciton.

  3. If any issues found or any of the issues are not resolved we reject the release and assign back to the devs. and devs correct them and prepare another release.

Does anyone have any suggestions on achieving something similar with JIRA+GreenHopper or any better ideas.

Solution

  • We do something pretty similar here, and it all works well within JIRA / Greenhopper:

    1. Product owner creates Epics / Themes / User stories in JIRA/Grasshopper

    2. Backlog grooming occurs, story thrashed out a bit, and story points entered into user story

    3. Sprint planning: Stories are selected for upcoming sprint, and using greenhopper, we create add the stories to the sprint. see below

    4. Sprint begins.. Tasks are created in JIRA by developers to track progress, and linked to the user story. Once all tasks for a story are complete, user story is done.

    5. We've put scripts in JIRA to have a button for "done" which automatically assigns the story our build team, who merge it into our main baseline (not sure if this applies to you). Once they have put it into a production build, the user story gets assigned to the QA team.

    6. QA team tests production build... if it passed, story is closed.

    enter image description here

    I might add that the QA team might take longer to test the story than the sprint allows - so for purposes of a team's sprint and velocity, the story is taken as done at the point it gets assigned to the build team.

    Does that make sense?

    JIRA is capable of all of this, it's great - although you might need to do some configuring to setup entries for epics/themes etc.

    We use Greenhopper functionality to create and track stories and sprints, but for task progress etc, we use a whiteboard - much more visible, and better for the daily standup.

    Hope this helps.. any questions I'll be happy to answer :)