Evaluating JIRA Agile – Team members

This article is part of a blog series! Part Title 1 Evaluating JIRA Agile – Product owners 2 Evaluating JIRA Agile – Scrum masters 3 Evaluating JIRA Agile – Team Members 4 Evaluating JIRA Agile – Everyone   Agile paints software development in a modern light. The single best thing about agile is that it engages the team in the entire planning development process: Decisions are no longer made in a vacuum away from the team, and software development

Continue reading »

Evaluating JIRA Agile – Scrum masters

This article is part of a blog series! Part Title 1 Evaluating JIRA Agile – Product owners 2 Evaluating JIRA Agile – Scrum masters 3 Evaluating JIRA Agile – Team Members 4 Evaluating JIRA Agile – Everyone   This is the second part of our blog series on how JIRA Agile optimizes the key players in an agile team (see also: product owners and the team). Agile methodology brings about a whole new way for managing projects – It focuses on iterative

Continue reading »

Evaluating JIRA Agile – Product owners

This article is part of a blog series! Part Title 1 Evaluating JIRA Agile – Product owners 2 Evaluating JIRA Agile – Scrum masters 3 Evaluating JIRA Agile – Team Members 4 Evaluating JIRA Agile – Everyone   Making the transition from traditional project management to agile involves changing the way the team views and prioritizes work. This change can be made easier with tools that provide gentle guidance when learning the fundamental tenets

Continue reading »

Yesterday, two of our very own Atlassian Confluence product managers, Sherif Mansour and John Masson, hosted a live webinar where they shared agile best practices that they've learned over the years, including: When to write product requirements documents and when to seek alternatives How to write effective product requirements documents How to build prototypes when designing new features Using JIRA and Confluence for product management You were clearly eager to learn We reached GoToWebinar's

Continue reading »

Who’s who in agile teams?

Agile teams are structurally different than their waterfall counterparts. Agile teams focus on the team itself, where waterfall teams often follow the structure of the organization. In traditional waterfall development scheduling often is “top down,” meaning management sets the pace and schedule. In agile, the team is self organizing, and sets its own schedule and destiny within the larger organization. As I was learning scrum one of the questions that kept coming to mind was, “How do development

Continue reading »