]project-open[ V3.5 and V4.0 already contain everything that is necessary in order to run projects via SCRUM or other agile methodologies. This article describes how to use and configure the ]project-open[system in order to support SCRUM, Kanban and other agile project management methodologies without interfering with reporting and other functionality of ]po[.
The SCRUM Main Project
A SCRUM project is represented in ]po[ as a normal project of type âConsultingâ or any of its sub-types. Consulting projects are containers for Tasks.
The SCRUM Sprint
Tasks and User Stories
By default, SCRUM Users stories are represented in ]po[ as sub-projects, while SCRUM tasks are represented as ]po[ timesheet tasks. Tasks already contain the âestimated hoursâ field for specifying the duration of a task. Please see further below about how to add a âStory Pointsâ field to user stories.
As an alternative, you could also use Tickets to represent tasks. In order to do so, please add a âService Level Agreementâ (SLA) sub-project to your SCRUM main project. A SLA project serves as a container for tickets. Using tickets allows customers and other stakeholders to create tasks user stories themselves. Advanced configurations can use the ]po[ workflow handle user story approval, priorization and quoting.
|A sample structure of a SCRUM project with two sprints
and two users stories. The SCRUM project and the user
stories are projects of type "Consulting", while the sprints
are of type "Release Project".
A SCRUM sprint is represented in ]po[ as a project of type "Software Release". The software release process is very similar to SCRUM, so we can use the same package for both processes. Further below we explain how to rename "Software Release" into "SCRUM Sprint" for example. The âSoftware Releaseâ sub-project contains a portlet with a list of âRelease Itemsâ, which we will use to contain "tasks".
Adding User Stories to a Sprint
There is a âAdd Release Itemsâ link that leads you to a page showing you potential âRelease Itemsâ. Please note that you can theoretically include a single Release Item in more then one Sprint. In order to remove the timesheet task from the list of potential Release Items, please set the status to âclosedâ.
|A task board diagram visualizes the current status of the SCRUM tasks
and allows to move them graphically.
]po[ V4.0 already contains a simple task board portlet. We will also add a burndown chart in the close future. The task is designed to be displayed full-screen, so that you could setup for example a big monitor in the developerâs room instead of a white board with post-its.
Hours can be logged on the timesheet tasks of the main project just like in any other ]po[ project. The Product Owner and the Scrum Master may also log hours on the Sprint sub-projects for preparing the sprints etc. So you can work with SCRUM in ]po[ without affecting the rest of the system. So there shouldnât be a reason for your superiors to criticize SCRUM on that ground.
Members of this role should usually be the project manager of the SCRUM main project. This way they will be able to control all aspects of the project.
Team Leader and Development Team
You can add the team leader or even the entire development team as âproject administratorsâ to the Sprint sub-project (go to the main SCRUM project -> Project Hierarchy portlet -> click on the Sprint sub-project -> Add member -> select multiple(!) team members and select âProject Managerâ). Even though the project administrators have full control of the Sprint sub-project, they have only read permissions on the main project. Also, any status change of user stories and tasks is audited, so that you can track who made changes at what time.
|This screenshot shows the category page after Task has
been made "is-a" a Software Release Item.
|The default configuration of the Release Management
states. Please replace with your favourites states or mark
the states as En=f to disable.
and tree_root_key(p.tree_sortkey) = (select tree_root_key(tree_sortkey) from im_projects where project_id = :release_project_id)
Please visit the "Open Discussions" forum at www.sourceforge.net/projects/project-open/ for discussion topics including "SCRUM".