Book Image

Redmine Cookbook

By : Shamasis Bhattacharya
Book Image

Redmine Cookbook

By: Shamasis Bhattacharya

Overview of this book

In a variety of online project management tools, Redmine markets itself as offering flexibility. Choosing the right management tool can mean the difference between the success and failure of a project. Flexible project management tools bend themselves to fit your needs, whether that’s communication regarding a simple project, or collaboration, or more complex project methodology such as SCRUM, or an issue-code relationship, or the need of different methodology for your project. Whether you are project manager or system administrator, this book provides valuable recipes to get the best possible performance out of your team, organization, infrastructure, and Redmine itself. Through a series of carefully crafted recipes covering the nitty-gritty of Redmine, you’ll be guided through the installation of Redmine, as well as how to fine-tune and customize your Redmine installation. Finally, we walk you through integrating Redmine with other softwares and databases like Tortoise SVN and Visual Studio and troubleshooting Redmine.
Table of Contents (17 chapters)
Redmine Cookbook
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
Index

Making sure everyone is optimally loaded with work


To achieve a goal of having everyone optimally loaded with work, you can use different approaches. This recipe will try to give you one possible insight into how much time is planned to be spent in a given period so that you can balance the load of tasks among team members.

Getting ready

For this recipe, you need to have a project in Redmine and tasks planned to be done in the future. They can be already assigned, but this is not necessary.

How to do it…

As time goes by, developers and workers in general are completing tasks, sometimes before ETA completion dates and sometimes after. To maintain an accurate state of your projects and to make sure everyone is optimally balanced with work, the best practice would be to have tasks updated by team members so that they can edit the ETA and completion date, or you could do this for them after a daily meeting, for example. To see how many estimated hours each team member has for the next 14 days, perform...