objectiF RPM allows you to execute your project planning agilely, classically, or even as a hybrid. Hybrid planning means that within one project, a few activities should be carried out classically and a few agilely. In objectiF RPM you can decide via the properties of the activity.
The planning method confirms which parameters are fixed for the planning and which ones are variable. Agile activities (sprints) are identified with a sprint length, fixed appointment and a set expense. An expansion of the extent of development will be realized in additional sprints. Accordingly, you can select the planning method “Fix cost, duration, appointments,” for an agile activity.
For all other activities, you can decide on one of the two planning methods with automatic appointment calculation, according to the properties that are most recommended for your planning.
In agile activities, the activity’s progress will be determined through portion of the contained and implemented requirements. For the agile activities in your project you can set under calcuation that the Earned Value Analysis should be executed agilely.
Classic activities are evaluated based on the closed portions of the activity. In objectiF RPM, you can specify rules for activities that have been started but not quite finished. If you decide on the 0/100 rule, then the performance will only be evaluated when the task is 100% completed. Which one you choose will depend on your planning strategy.
In agile activities, the team controls itself, so it makes sense to not allocate the activities to individual employees, but to certain teams. That’s why you can allocate the activities to processing groups (or teams) in objectiF RPM, and directly adapt their capacity at allocation. Teams with five full-time employees, then, have a daily capacity of five days.
Activities can be connected with requirements directly in objectiF RPM. Classically planned activities are normally allocated concrete requirements. Agile sprints, on the other hand, are scheduled at the beginning of planning but the requirements to be implemented in each sprint are determined only at the beginning of the sprint. After all, agile teams want to be able to react flexibly to changes at short notice. In objectiF RPM, agile activities are connected with a backlog. The employee capacity of the activities then results in the total capacity of the backlog.
Predecessor and successor sprints
Predecessor and successor relationships confirm, for example, how activities react to delays of other activities. Strictly taken, this cannot happen with agile activities because the sprints are exactly set. With hybrid projects, however, it is possible to start agile sprints when the results of classical predecessor activities have been reached. That’s why objectiF RPM enables the creation of predecessor and successor activities and adapting the relationship to the actual (hybrid) circumstance.
If you have questions or suggestions about planning or hybrid projects in objectiF RPM, we can be contacted at email@example.com or 030/467086-20, and we are always very glad to hear from you.