Wiki » History » Version 4
Dimitris Pipelias, 11/11/2025 04:03 PM
| 1 | 2 | Constantinos Lempidakis | h1. Lemco Project Manual |
|---|---|---|---|
| 2 | 1 | Constantinos Lempidakis | |
| 3 | 2 | Constantinos Lempidakis | Lemco project manual provides basic guidelines and instructions that all users must follow when they are using Lemco project management software (Redmine). |
| 4 | Guidelines or Instructions may change or update periodically, for that reason is strongly recommended all users to follow this project by adding it in their "Watch" list. |
||
| 5 | 1 | Constantinos Lempidakis | |
| 6 | 2 | Constantinos Lempidakis | h3. Projects |
| 7 | 1 | Constantinos Lempidakis | |
| 8 | 2 | Constantinos Lempidakis | Several guidelines or instructions for projects can be found below: |
| 9 | 1 | Constantinos Lempidakis | |
| 10 | |||
| 11 | 2 | Constantinos Lempidakis | * [[Opening a new project]] |
| 12 | 1 | Constantinos Lempidakis | |
| 13 | 2 | Constantinos Lempidakis | |
| 14 | h3. Trackers |
||
| 15 | 1 | Constantinos Lempidakis | |
| 16 | 2 | Constantinos Lempidakis | h3. Files Guidelines |
| 17 | 1 | Constantinos Lempidakis | |
| 18 | 2 | Constantinos Lempidakis | * [[Types]] |
| 19 | * [[Naming]] |
||
| 20 | 4 | Dimitris Pipelias | |
| 21 | In Redmine, the project management process starts with the user logging into the platform using their personal credentials. |
||
| 22 | Once logged in, the administrator creates and structures the project, defining its framework, setting up subprojects, assigning user roles and permissions, and specifying deadlines and key configurations. |
||
| 23 | |||
| 24 | |||
| 25 | Throughout the project lifecycle, users can upload and manage documentation—such as manuals, guides, or technical files—through the Documents section. |
||
| 26 | This feature helps keep all project materials centralized, well-organized, and easily accessible to team members. |
||
| 27 | |||
| 28 | The next step involves creating and managing issues, which represent the main work items in Redmine, including tasks, bugs, and feature requests. |
||
| 29 | Each issue should include a clear description, assigned user, status, and due date, allowing the team to track progress and maintain accountability until completion. |
||
| 30 | |||
| 31 | To support communication and teamwork, Redmine provides tools such as the Wiki, comments, and news announcements. |
||
| 32 | These features allow team members to share information, document procedures, and maintain transparency throughout the project. |
||
| 33 | |||
| 34 | Project progress can be monitored visually through Redmine’s Calendar and Gantt charts, which display timelines, milestones, and dependencies between tasks. |
||
| 35 | These tools help users identify delays, adjust schedules, and keep the project on track. |
||
| 36 | |||
| 37 | |||
| 38 | By combining task tracking, documentation management, and collaboration tools in one place, Redmine offers a complete environment for organizing, executing, and evaluating projects efficiently and transparently. |