agile - Atlassian GreenHopper and Release Management -
we playing around atlassian products , have prepared agile sprint using greenhopper, , little confused flow.
here how doing current development @ office:
1. developers completes issues assigned them. mark them resolved.
2. once issues sprint complete have release ticket provides release details , assign inf team build , deploy in qa. if things approved in qa moved staging, produciton.
3. if issues found or of issues not resolved reject release , assign devs. , devs correct them , prepare release.
does have suggestions on achieving similar jira+greenhopper or better ideas.
thanks in advance.
we pretty similar here, , works within jira / greenhopper:
product owner creates epics / themes / user stories in jira/grasshopper
backlog grooming occurs, story thrashed out bit, , story points entered user story
sprint planning: stories selected upcoming sprint, , using greenhopper, create add stories sprint. see below
sprint begins.. tasks created in jira developers track progress, , linked user story. once tasks story complete, user story done.
we've put scripts in jira have button "done" automatically assigns story our build team, merge our main baseline (not sure if applies you). once have put production build, user story gets assigned qa team.
qa team tests production build... if passed, story closed.
i might add qa team might take longer test story sprint allows - purposes of team's sprint , velocity, story taken done @ point gets assigned build team.
does make sense?
jira capable of of this, it's great - although might need configuring setup entries epics/themes etc.
we use greenhopper functionality create , track stories , sprints, task progress etc, use whiteboard - more visible, , better daily standup.
hope helps.. questions i'll happy answer :)
Comments
Post a Comment