Tool for project management in Agile development-mingle

Some time ago, I used ror in combination with scrum to create a simple project. I learned about ror and scrum. The results and feelings of the next decomposition have the opportunity to write down the entire process of agile development and comparison of waterfall development, combined with the process of RUP, XP, and scrum.

At that time, I had been seeking for scrum project management tools in my project. At that time, I found many tools, including open-source tools, commercial tools, and Microsoft projects. Mingle was found at that time, but the mingle installation package was not released at that time. Later, I went to the agile alliance to use an Excel template for management, which made it quite troublesome.

Yesterday, Bill mentioned mingle, which aroused the interest I wanted to study. So he downloaded the message and played it.

First introduce mingle (excerpt javaeye ):

Thoughtworks's agile project management product, mingle, has started Public Beta.
Mingle is an agile project management tool. It provides "one-stop" services for the entire team in the software delivery process, and shares all the project results through the development framework provided by thoughtworks with 10 years of Agile Project development experience. Your team can use mingle for project management, collaboration, document sharing, bug tracking, demand mining, and Program Code Connect to the requirement.
Ten reasons for using mingle:
I, Mingle It is a project management tool that agile teams really want to use.
With mingle, there are no repeated data input and redundant operations. Because the team actually uses it, mingle records the real status of the project in real time.
II, It can achieve the way you want to work.
Mingle is easy to use, fast, simple, and flexible. In particular, it can easily connect program code with requirements.
III, Mingle It can increase team productivity and reduce project delivery risks.
All team members can learn about the progress of the project anytime and anywhere. It can show the fierce "field" of software development, so that you can quickly respond to various problems in the development.
IV, It helps teams improve their learning speed and find the best development mode suitable for themselves.
Mingle automatically collects story, bugs, and other project products and dynamically organizes them together. With this data, you may even find unexpected project trends.
V, It is simple and powerful.
Mingle is easy to use. We only focus on truly valuable data and present them in the first place. Therefore, mingle provides powerful intelligent support for project management, achieving a perfect combination of simplicity and strength.
VI, It is a team's knowledge sharing platform.
Throughout the development team, project managers, developers, business analysts, and testers can get the information they need from mingle, rather than searching through workbooks and documents.
VII, Mingle It intelligently completes the job you want.
When you submit your own program code, enter the comment message "Fix bug #541 ". Mingle associates the submitted code with the bug and automatically updates the bug data. When browsing this bug, you can directly view all the code modified to fix the bug. In this process, you do not need to log on to mingle or do any additional work.
8, It is composed Thoughtworks Manufacturing.
Thoughtworks has been providing users with innovative software solutions for 14 years. We focus on the IT solution technology and delivery process consulting work, known as the technology trend leader in the industry. We have introduced agile development methods, and mingle will support and promote all this work.
IX, Mingle Use your own development process.
You can use the terms you are used to in mingle to customize various development processes that suit you.
10, Mingle Easy to get started.
Mingle is easy to install and provides step-by-step Configuration Wizard. After the installation is successful, a Project template provided by thoughtworks is attached by default. You can quickly start a new project. You can also easily import the data of the current project from Excel to mingle.
You can download and watch the mingle video demonstration: http://studios.thoughtworks.com/mingle-project-intelligence/videos. You can use the following link to register online to apply for the download of mingle: Role. For more details, visit the official mingle Website: http://studios.thoughtworks.com/mingle-project-intelligence.

Start to follow, visit the official website, download for Windows. You can also download a virtual machine. After the installation, run and find that minglewebserver service accounts for 100% of the CPU (mingle is written in jruby and does not know whether MerB or rails MVC is used. Yesterday, Karron said the two are merged, in the future, rails3 will adopt the MerB architecture and may discard the original rails ). Restart the service and enter the configuration page. This configuration interface is similar to WordPress configuration. It is nothing more than configuring the database (MySQL and PostgreSQL supported), SMTP, and license.

Note: obtain the license in the email you entered during download. You can enter http: // localhost: 8080/license to configure your 5-person license. To increase the number of users, follow the instructions.

Before introducing mingle, we will introduce several terms:

LRelease

N project plan specifies several release. Each release may have several iterations. One iteration has several sprints, depending on the specific situation.

LProduct backlog

L Product Requirement library, in the unit of story, involving functional, testing, and deployment... Product backlogs can be added to quickly respond to customer needs.

LSprint backlog

N is the requirement library for a sprint cycle, in the unit of sprint. Generally, a sprint cycle is one month.

LStory

The minimum unit in N backlog is equivalent to the list of each WBS task.

LTask

N a story can contain multiple tasks. For example, the user logon module can contain story-Logon module development and story-unit testing.

LDefect

N each sprint can record and be tracked from the requirement analysis stage, design, development to deployment.

After installation, create a new project. Select an existing template and scrum template,

After creation, a template and data of a scrum project are imported by default. Open the home page with rich data. The whole portal has the current release burndown diagram, including analysis, design, development, and test, and a matrix diagram of sprint, story, task, and defect, the dependency graph of defect, story, and task is also an important statistical chart. Identifying and building dependencies between them is often the key to project success. personnel can be effectively arranged based on the priority and order of tasks to improve generation efficiency. Mywork is the task item currently assigned to the login user,

Compare the project release plan and Pb plan charts in excel at that time.

First, open project Admin. Here is the management portal of the project. Including project configuration, template import and export, and variable settings.

To export a project template

It is a custom card properties. You can set show/hide, lock, and Transtion. Set the type and application place (sprint, defect, story, task...) of a new card properties ....)

This is the management of the card type. The system has predefined release, sprint, story, task, and defect. You can drag and drop to set the order, such as release before sprint.

Is to add a cardType interface, you can select the card properties you want, drag and drop its order, set the color of cardType.

This is the planning tree of the entire project. It shows the relationship from release to sprint to story to task. It is very library. Drag and Drop Map

Let's take a look at the feature tree of the entire project.

This is also cool. You can customize your own favorite and the tab menu in the preceding row to define your workbench portal.

This is cool. Define some transition. When some conditions are met, it will be automatically triggered to convert to some results. For example, to define an accepted transition, when the status of a story is ready for signoff, the owner is automatically set to peterwang, acceptedon = (today), status = accepted

Attach a product backlog Diagram

Compare the product backlog in Excel format used by the current project

Open the details of each story and set the sprint to which the story belongs.

The current sprint backlog Lane chart shows the story information for each status (preparation, development, testing, accepted, etc.) in the current sprint.

Compare the sprint backlog chart of the Excel method used by the current project

Set the story to which the task belongs.

Compare the relationship between tasks and story in Excel mode used by the current project.

This is the system audit, which records the change history of each card (such as release, sprint, story, task, and defect ).

• Add a homepage chart created using agile hybrid template (2.1 ).

This template represents a hybrid agile approach to project tracking that wocould support release and iteration-based planning. the template has des some sample cards to assign strate the working of the charts and transitions. these stories can be deleted if necessary by a Project Administrator.