Our Team uses Agile
Software development advances towards product release through the combined efforts of a product owner, the Scrum master, and the development team. Some of these individuals wear multiple hats, also performing project or board administration.
As the product owner, my primary responsibility is to manage the product roadmap, prioritizing and organizing issues, assigning versions, and fleshing out details so that the Agile team can plan their sprints quickly and efficiently. I rely on input from the Agile team.
I need to stay current on the progress of sprints, epics, and releases, so reporting is critical. To plan for product releases, the development team's velocity must be predictable, bottlenecks and obstacles to progress must be quickly recognized and managed. Info from dev tools also feeds into accurate release planning.
The dev team needs to be able to track their progress during a sprint to react to roadblocks. Breaking issues down and delegating to other developers helps streamline work. The team also benefits from logging and tracking time worked on issues. This improves accuracy of estimation.
The Agile team consists of developers and a Scrum master. Our team typically assists the product owner in organizing and prioritizing issues in the backlog. Someone on the team creates and configures Scrum boards, configuring them to use quick filters and swim lanes. We also configure the board to set the type of metric used for estimating work, and to enable developers to log and track the time spent on an issue. Someone on the team assigns members to the various project roles and also creates project links that leverage the integration of development and collaboration tools with Jira.
When it's time to plan a sprint, we estimate work effort for each issue, create the sprint and then chunk issues into sub-tasks for easier time tracking. During the sprint, we rely on the development tool data that’s surfaced in the detail view of an issue. We need to know how to link data in Bitbucket and Bamboo to the relevant Jira issue. The team uses Jira reports to stay on top of sprint progress and for long term planning. We create and interpret team-specific reports and dashboard gadgets.
- Getting Started with Jira Software Server
- Getting More from Jira Software Server
- Realizing the Power of Jira Reporting & Dashboards
- Planning with Portfolio for Jira
Get started with free training
Get on the path to certification
- Prep course: Agile Development with Jira Software
- ACP-300 Agile Development with Jira Software
- ACB-312 Jira Reporting and Dashboards (Certified Badge)
- ACB-110 Advanced Jira Workflows (Certified Badge)