-
Agile planning from a developer's perspective
From releases to features, to story cards and estimating story units, hear our developers and technical leads share their reflections on how agile planning works inside Atlassian.
All our teams utilise story cards because it allows you to visualise the work remaining in an iteration. Some of our teams use GreenHopper to manage story cards within JIRA and some teams prefer paper cards and corkboards. Either way works as long as teams are disiplined about updating.
Watch our developers talk about planning (3:44)
-
Ted on index cards for agile & scrum
Ted's team uses the GreenHopper plugin for JIRA as a virtual corkboard. Virtual index cards make it easy to record the story, the story points and an estimate.
Once a developer pulls a card down from the corkboard, they can't move on to another card until the card is complete. This way there are only 3 status types for any card: untouched, incomplete with completed.
Ted talks about index cards in GreenHopper (1:07)
-
Per on scrum based iterations
Do you believe that Confluence has a shippable milestone every two weeks? It's true.
Dogfooding our own software is critical to shipping quality products. We get 200 users on each each new iteration to discover bugs before any customer would. The early exposure to the new code also sets a high standard of quality for each developer's commits.
Watch Per talk about scrum based iterations (1:11)
Planning
Effective planning is critical to Atlassian's purpose to "Create useful producs that people lust after". Using index cards, managing iterations and even doing program management are tangible ways we go about planning to fulfill our purpose.