Quick start, is so simple

Agile project management can be applied to any JIRA project. Whether you are a scrum master or just try new to agile development, your greenhopper can help you during the whole release process management to-do (backlog), sprint (Sprint) and to monitor the progress of the project.





Installation and integration


Project planning you.

Scrum and Kanban? Your greenhopper by JIRA can be customized and flexible workflow provides a adapt to the team development of agile project management tools. For example, you can first from a Scrum panel, and then by adding columns and constraints to Kanban practice.

To quickly create Backlog

To build a product by Backlog to quickly create user stories. Fill in the assembly, the criteria for success, business value or team to other fields required for the planning and execution of work. If your Backlog in other tools, can migrate from the GreenHopper to the import tool.

Sort of Backlog

By sorting the Backlog users in the story and the defects of drag, those business value of the biggest story on the top of the Backlog. If you have a lot of Backlog, can set up filters to filter the user stories or specific defects.

Easy to estimate

Agile planning meeting can plan to implement agile poker stories and repair defects workload estimation. Of course, the use of the point of the story and ideal hours, the size of T-Shirt is GreenHopper other estimation methods can support.

The progress of visualization

Team members can update the story by dragging or edit details in the story in the view pop-up. You can see at a glance at all the tasks, no longer need solid wall cards (cardwalls).

Coupled with the powerful function of JIRA itself

Custom types, associated with agile development problem field and workflow in JIRA, quickly adapt to the changes in the organization process. In a GreenHopper board can display multiple JIRA project development status.

continuous improvement

The GreenHopper team development process has become visible, to help you identify the bottleneck and definition of the problem, in order to make a quick reaction.



Scrum criterion

Scrum is an agile method, in this method, the team Sprint (Sprint) according to said time to arrange the work piece. The team made a commitment, delivery may work in the sprint at the end of the software to the customer.

Task review (Backlog)

In the task in the process of combing, the team will complete the story (Story) to estimate the amount of work needed to prepare for the sprint planning. The story can be decomposed into tasks or supplementary acceptance conditions, so the team can clear the standard finish.

Sprint planning

The product owner (Product Owner) from the product (Product Backlog) task selects a subset of the top, and then use this subset into tag will sprint sprint task (Sprint Backlog). All the stories are marked corresponding sprint will be discussed in the sprint planning meeting, when the sprint at the start tag question becomes the team needs delivery commitments.

Sprint process visualization

The story Lane allows team members to understand the progress of each independent story. When all tasks of a story are in complete list, products will be responsible for the change of the story reminds state has been completed.

Burn figure (Burndown Chart)

The team used to burn down charts according to their sprint goals to track progress. If the sprint goal has changed, such as the sprint added another story, this will be reflected in the map.

Sprint review

Sprint sprint review meeting with the report. The report details the initial commitment, scope change and team deliverables.

Scrum + Kanban = Scrumban

The Kanban basic standards applied to the existing Scrum framework, and improve the development process. According to the number of story points or problems add column constraints to avoid bottlenecks and find possible free time.



Kanban (Kanban) criterion

Kanban is a catalyst, through subtle and gradual manner gradually improve your existing processes (both scrum or something else). Rooted in the lean production, Kanban can be regarded as a signal system and has been effectively applied in software development, development and operation (Devops), it operation and maintenance and other process in.

Visualize your workflow

The panel on the column with your current workflow steps according to the corresponding process changes at any time, add or delete columns. Kanban team usually in a panel setting longer process or wait state, such as adding a columns to display the state of "waiting for customer response".

The level of the lane

On your panel uses swimlanes to classification problems, and help you according to the grade of service (such as "emergency") to develop valuable workflow. You can use the JIRA query language (JQL) to configure the lane, fully configurable classification standard

set constraints

Kanban team through the panel from left to right to change the state of the drag operation. The ability to set the minimum column constraint to identify idle (yellow) and the maximum column constraint to identify bottlenecks (red).

Measurement of the turnaround time

The problem is a problem of turnaround time itself time (not including waiting time). Delivery time is a problem the total time from the forward to complete the cost. The same size of the story usually requires the consistency problem of turnaround time, which accordingly provides customers with predictability.

Trend analysis

The cumulative flow diagram (Cumulative Flow Diagram) to monitor future trends and analysis of the historical process, the identification work is where to start and where bottlenecks.


Installation and integration

Add content to your agile wallboard

The configuration of a JIRA panel, so the team will have a release of information, it can be used in the daily station will be on the team. Add a chart, sprint burndown charts, sprint remaining days and cumulative flow diagram etc..

Reduce the pressure of the team

According to the development and production of automatic deployment stage environment. GreenHopper and Bamboo are integrated through HTTP Request Workflow Function plugin. But no matter when, as long as the developers will be a user story until completion status, the code will automatically build and deploy.

The use of Bonfire to improve the quality of

Don't make the quality assurance (QA) has become a bottleneck, will test the power delivered to the hands of each team member. Use Bonfire to create a test task, then check the open test tasks associated with the user and the unfinished story on the GreenHopper panel.

Create a team calendar

To improve the transparency of team activities by date and date of delivery of the visualization of sprint. The use of Team Calendars (team calendar plugin), can display and leave the team sprint.

With the plug-in integration

GreenHopper and other JIRA plug-ins (such as Tempo and JIRA Wallboards) integration, so as to provide a seamless experience for planning and reporting team. There is a further demand, now you will use REST API application and GreenHopper integration!

Simple installation

The use of JIRA Universal Plugin Manager (plugin manager) can quickly install and update the GreenHopper plug-in.