11.2 Demonstration
An example project used to demonstrate Redmine
-
Introducing a project management system for an R&D site – can be a faculty of a University – with 20 associates and 3-4 parallel projects
-
High-level plan in Redmine
-
-
Plan - Define
-
Usage requirements
-
System available 24/7
-
Access from local and remote computers available
-
Web based UI
-
-
Logging all activity
-
Gantt chart for printing
-
Logging time on a project, later on a ticket basis
-
Mandatory time log at the end of the week by all employees
-
Granularity: log a minimum of 4 hours / issue of a project
-
-
Role & permission handling
-
Project auditor / head of department
-
Read-only mode for all projects
-
Monitors all projects on a weekly basis
-
-
Project manager
-
Read and write for own projects
-
Manages projects, creates and assigns tasks, evaluate process
-
Creates time log on a ticket basis
-
-
Project executors
-
Limited read and write access for own projects, full access to own tickets
-
Execute assigned tasks, create more granular task list in a hierarchical format, if needed
-
Creates time log on a ticket basis
-
-
-
-
Success criteria
-
Web based, multi-user system set up
-
All users use the system on a daily basis
-
All projects of the department are available in the system
-
Granular task list with start and finish dates available
-
System is up-to-date, shows real-time process
-
All employees logs a minimum of 7 hours per day for the current week till the following Tuesday evening
-
-
Technical tasks on installing and modifying the system
-
Create a secure server environment
-
Use encryption
-
Set up support and maintenance roles and responsibilities
-
-
-
Provide a task list for integration to to-be-used processes
-
Define type of tickets and workflow
-
Type of tickets : workflow
-
Prototyping: New > Accepted > In Progress > Testing > Done
-
Development: New > Analysis Done > Implementing > A Testing > Integrating > B Testing > Done
-
Testing: Test ready > Define Test cases > Implement auto test cases > Implement regression test > Execute manual & Auto test cases > Evaluate > Back to development (Convert to Development ticket) | Done
-
-
-
Add users & permissions, according to the above
-
User Audit, pw. 123
-
User PM, pw. 456
-
User User1, pw 789
-
-
Add a sample project for the department
-
-
Execute task list
-
(Constantly) measure if success criteria are met,
-
Evaluate
-
Report
-