Agile Project Management with JIRA and Greenhopper

Agile is often sold as a set of tools, but its real value lies in the habits it creates: rapid feedback, clear visibility, and the ability to adapt without losing control. In this session, XBOSoft’s Allan Trefzger and Go2Group’s Mike Mayhew drew on decades of experience to show how JIRA, Greenhopper, and supporting plugins can bring those habits to life — for both development and quality assurance.

The conversation began with a reminder that Agile is not “faster by default.” The benefit is focus: breaking work into short, well-defined sprints so teams can deliver something tangible, review it with stakeholders, and adjust course before investing months of effort. That feedback loop works best when the process is supported by tools that make progress — and problems — visible to everyone.

From requirements to results

Traditional requirements gathering often produces long, static documents that quickly go out of date. In the Agile approach discussed here, requirements are broken into user stories and organized in a backlog that can be prioritized and refined over time. Greenhopper’s planning and work boards make that backlog visible, while swimlanes, filters, and story points let teams plan realistically and track progress without constant status meetings.

Keeping quality in sync

One recurring challenge is making sure testing keeps pace with development. The panelists described ways to integrate QA directly into the sprint workflow, using JIRA issue types for test cases and plugins like SynapseRT for traceability. This allows testers to see exactly which requirements each test covers, and for managers to confirm coverage before a release.

Bringing development, QA, and stakeholders together

In many organizations, development and QA operate as separate silos. Agile practices — supported by the right tooling — encourage “cross-contamination” in the best sense: testers understand unit tests, developers see the QA process, and both groups share visibility into code commits, test coverage, and sprint status. That shared context reduces handoff errors and shortens the time from discovery to fix.

Reporting that drives decisions

Agile reporting is less about Gantt charts and more about showing trends and capacity in real time. Burndown charts, workload reports, and test run summaries give managers a clear, simple picture of where a project stands. Because these reports draw directly from the boards and workflows teams are already using, they reflect reality — not a separate layer of documentation.

For organizations already using JIRA, the takeaway is clear: the platform can be far more than a ticket tracker. With thoughtful configuration — and the right mix of plugins — it becomes the central hub for planning, building, testing, and delivering software in a way that keeps everyone aligned.