To enter Redmine go to rm.appogeum.com.
What is Redmine?
Redmine is a system for easy management of small and complex projects. Imagine that you want to communicate 10 remarks/changes/errors pertaining to the project, and you send them by e-mail. It may happen that 4 of them will be considered and dealt with immediately, while the remaining 6 will be discussed at length, by e-mail, with the history of the discussion appended to each message. One after another, the issues will be resolved, but one of them can be forgotten. Additionally, there can be messages added by phone, Skype, etc. To orient oneself in that plethora of information and to be sure that nothing is lost in the process, companies use different systems for recording the messages. That can be done with the help of a notebook, memo pads stuck to the computer screen, or Google spreadsheets. In our company, we use Redmine.
Redmine, a project management system, is a so-called ticket system in which each remark you enter (a task) is displayed on the list until both sides agree that the remark has been analyzed/implemented, assigned to the proper person, and has an appropriate status. The system works equally well regardless of whether the project involves 2 or 20 people.
Moreover, Redmine is the one place in which all files, information, test solutions, and other data related to a given project are stored. No longer is it necessary to search through many places, such as the history of Skype conversations, sent and received e-mails, the downloads folder, etc. People working on the project are immediately informed about each remark or change you enter into the system.
Redmine works in the Polish and English language versions, depending on your preferences.
Tips and rules for working with Redmine
Tasks – creating a task
Each remark you enter into the system is a task (created with the help of the option New task). Do not enter more than one issue/remark into one task unless they are very closely related and are not very important. When you create a new task you have to choose the type of task, e.g. Error, Task, etc., which suits the nature of your issue/remark. You also choose the title and content of the task. If there is need for it, you can also add files – screen captures, zip files, etc.
When you create a task, assign it to the person who should deal with it – a programmer, a graphic designer, a manager. That is very important as people who work in Appogeum manager many projects and the proper assignment will enable them to easily filter the list of tasks to do those they have been assigned to.
The remaining fields are at your disposal.
Tasks – task status
There are three key statuses of tasks. The first one is “Assigned”: when you create a new task you choose that status. At the moment when your remark has been dealt with or answered, the task will be described as “Solved”. If you agree that the answer to the remark is sufficient you can close the task. It is then no longer displayed on the task list when the filters are set at default. If you believe the problem has not been solved, change the status back to “Assigned”.
Tasks – updating tasks
Each task can, and even must be updated at least once. It is like with a conversation, or the answer function, or adding a comment. An update may involve adding a comment or a file, or changing the task status. The history of the task is preserved.
In 99% of cases it is important to make changes in the fields concerning the status of the task and the person assigned to tackle the task.
For example, let us assume that we have a programmer John and a manager/client George.
George creates a task in which he informs John that an icon must be changed but he forgets to attach the file with the icon. [assigned to John, status: Assigned]
John updates the task to inform George that the icon is missing. [assigned to George, status: Assigned].
George updates the task by adding the file with the icon. [assigned to John, status: Assigned]
George has modified the icon and quickly updates the task again, uploading the new version. [assigned to John, status: Assigned]
John updates the icon of the application and prepares a new test version which he places in the Files section. [assigned to George, status: Solved]
George downloads the application, checks the change and sees everything is in order, so he updates the task again and changes its status to “Closed” which means the change is correct. [assigned to George, status: Closed]
However, should George notice that the icon has not been added or that it is an incorrect version, he will enter an appropriate comment into the task and assign it to John again, with the status “Assigned”.
Summary
Apart from the functions described above, Redmine offers many additional options, such as a calendar, communications, a repository of code, and documents. The use of all those options is easy, analogous to that of many systems of discussion forums, etc.
Please, remember that while you can only see the tasks in your own project, we have access to all the tasks from various projects we are currently working on, which makes it so important for you to assign the appropriate status and person to your tasks.
If we abide by the rules described above, our cooperation on the project will be really pleasant and simple, and the tasks will be done in no time at all.
