Gaia SprintGaia-Sprint is a highly interactive Scrum Process Management administration tool for tracking Scrum projects. It is free to use and free to modify, though it follows the GPL license model, so any changes released to "customers" must be made available in "source code form" for those customers too. Register a userBy default Gaia-Sprint will setup a user with the username admin and password 1234. You can change both of these in the "profile" window just after you login. Other users when coming to Gaia-Sprint can by default create new users and start creating project. A todo item in such a regards would be to make this a setting or add up some "secret password" you need to type in to be able to create users and projects. Also another TODO would be to have CAPTCHA for user registration. When other users have registered you can start adding those users into you projects. It is easy to remove users from your project after they have been added, but be careful since this might delete all data which is attached to the user you're deleting. You cannot delete yourself from a project. This is an easy hack to make sure the last user will never be deleted from project which will delete the project. ProjectsYou can create as many projects as you wish and you can add other users into the projects you have access to. You cannot however add yourself into other peoples projects. This is to ensure privacy in projects. If you want to have access to other peoples projects, you should send them a mail stating that they must add you up into the project with your username so that they know which user to add. One project typically consists of a bunch of Product Backlogs and any number of "sprints". Every project has a "dialog" which basically is an ongoing chat where everything written will be stored forever and serve as a "communication backlog" per project. Product BacklogThe Product Backlog might be thought of as the "customer requirements" and is mostly the responsibility of your "customer" in a Scrum project. The customer is responsible for prioritizing items on the Product Backlog. But the team of developers are responsible for assigning "Estimates" for how much work the specific items needs. The team and customer can discuss items on the Product Backlog in a forum like user interface. In addition all communication done through the "Dialog Window" will forever be available to read as a backlog of communication. The Product Backlog can be manipulated either through the "Edit Product Backlog" button or the "Prioritize Product Backlog" button on the project page. You must however create Backlog items in the "Edit Product Backlog" window. SprintAn iteration in the Scrum Process methodology is called "sprint". A sprint typically lasts from 2 to 4 weeks and is the phase where the customer cannot interfere with the priorities of the team (developer team) at all. He can talk and discuss things with them, but he cannot change his mind but have to wait until the sprint is over for the next sprint planning meeting to state his mind. If the customer must change priorities during a sprint, the whole sprint must be aborted and a new sprint started with the changed priorities. However the sprint is initiated with the sprint planning meeting where the customer gets to play around with priorities and give the team a prioritized list of features. A sprint begins with deciding how long it should be, typically 2-4 weeks are optimal. Then every member of the team gets to say how many hours they have for "sprint work". Sprint work is the time you have left after attending meetings, reading email and other "non-coding" work. Typically this will be between 40 and 70 percent of your full work time. The team then creates tasks for every Product Backlog items they think they are capable of full filling starting from the top of the priority list and working down and divides those tasks between them. Then they estimate roughly how much work should be done per task and the sprint begins. Note that the Product Backlog is prioritized mostly by the customer and the team should have very strong arguments for not starting at the top of the list given by the customer. Burn-down chartEvery day the team reports to each other in a standup meeting and gives estimates of how much work is left in the tasks they have. This should typically decrease on a daily basis, but uncertainties and problems arising during research may increase the complexity of tasks once thought to be easy. The burn-down chart is then generated as a result of the daily standup meetings reports and will reflect how the team is working and how they are following their schedule.
|
Sign in to add a comment
