Agile project management made easy
The agile project management method Scrum can be deployed quickly thanks to its simple structure and predefined roles. Scrum ensures flexibility and transparency. In Projektron BCS you digitally manage your Scrum projects and benefit from the complete toolbox of our project management software.
Sprint progress at a glance
Projektron BCS supports you in the effective design of your Daily Scrum with a Task Overview which can be customized flexibly to your needs.
Projektron BCS clearly shows you the current processing status of your requirements and activities from your Sprint Backlog. Every team member can select an activity for processing or mark it as implemented with just one click. This serves as a reliable basis for the daily planning by your Scrum team.
A burndown chart with cumulative flow diagram, which displays the Sprint's progress in a graphic, can also be integrated in the Task Overview. Projektron BCS visualizes the processing status for the requirements in color and displays the ideal chronological course of the Sprint as a reference.
Visualized for agile teams
In the integrated Scrum board, you can move individual activities from the user stories by drag & drop. Depending on which column you move your activities to, for example to Scheduled, Processing or Done, the status of the respective activity changes automatically. Colored markers distinguish which activities belong to which user story. You can adapt the board to your individual way of working with additional filter options and groupings.
Your team members are displayed above the board. Assign processors to activities quickly and simply using drag & drop. If you move a task back to “Scheduled,” assigned processors are removed directly. In the Scrum board, you can also use the Work in Progress limit (WiP limit) included in Kanban. If you select an employee, all activities that are scheduled or in progress which the employee is working on or is able to work are highlighted. You can use the Focus button to quickly move between the employee’s activities. When you click an activity, it receives the focus. This allows a targeted discussion of an activity during a Scrum meeting.
From an Epic to User Stories and Partial Requirements to Activities and Acceptance Tests: You can structure and refine the requirements for your product in the Product Backlog of Projektron BCS.
You can also create, move by drag & drop and prioritize the required Scrum structural elements directly in the Product Backlog. Additional information on the structural elements of your Scrum, such as status, priorities and estimated values, can be maintained centrally in the Product Backlog.
Team members and product owners can communicate with one another directly on the user stories and epics. If there is a new message for you or your team, you will see this directly in your personal overview. You can call up the corresponding scrum element with just a few clicks and write your reply. The communication history and the most important changes are also directly displayed on the scrum element. This enables you to reconstruct what was discussed at a later time.
Prioritize User Stories and transfer them to the Sprint backlog
You are well prepared to start the Sprint Planning using Projektron BCS. Projektron BCS displays any outstanding Sprints of your Scrum-project in the Planning view of the Product Backlog. Using drag & drop, you can run through possible Sprint assignments and processing sequences of the User Stories. In this, Projektron BCS considers your team's development speed (Velocity) as well as the estimated Story Points of your User Stories and informs you about any capacity bottlenecks.
Once you have established the targets for a Sprint, you can transfer the User Stories from the Product Backlog – using drag & drop – into the corresponding Sprint Backlog.
If you are working on a major Scrum project with more than one development team, the Planning view in the Product Backlog allows you to also clearly organize your User Stories in multiple, parallel-running Sprints.
Working through Scrum projects easily
Projektron BCS supports you with suitable wizards which guide you through the most important steps in your Scrum projects and sub-projects, if desired, when working with single Scrum structure elements.
For realistic planning
Projektron BCS makes it possible for you to reserve employee capacities for individual Sprints or for the entire Scrum project. How much free capacity is currently available can be checked quickly in the Resource Preview in Projektron BCS.
Whether Sprint Planning, Daily Scrum, Sprint Demo (Review) or Sprint Retrospective: You can create regularly scheduled meetings for your Scrum team automatically in the Sprint Calender. The dates created as a suggestion can be customized manually, for example when you want to invite additional participants or when the time changes.
Documented Scrum activities
Your Scrum team uses Time Recording in Projektron BCS to book their accrued efforts directly to the processed User Stories, Partial Requirements, Activities and Acceptance Tests.
Projektron BCS totals the booked times along the Product Backlog structure. As the Product Owner, you therefore know exactly how much effort was required, for example, for the implementation of a User Story or a product increment and if there were any relevant deviations between the estimated efforts and the efforts actually accrued.
If you also work with the Invoice module in Projektron BCS, you can easily invoice booked and project-specific efforts to your customers.
Tickets for Scrum
If you work with the Ticket System of Projektron BCS, you can easily transfer product-related inquiries and customer inquiries to your Scrum projects.
For example, if a customer authorizes a new function via a ticket, you can create the corresponding User Story in just a few clicks and add it to a Product Backlog. Here, the ticket description can be easily adopted for user stories and activities. Projektron BCS links the new User Story with the original ticket, thus allowing an easy tracing of the creation history, for example when prioritizing the Product Backlog.
In addition, tickets can be linked to User Stories, Epics or Partial Requirements that already exist.