In this article, we will explore more. As the Certified Hybrid-Agile Master Professional (CHAMP) course from Management Yogi is hands-on (see here), there will be quite a few points on it. Some of them are noted below.
Sprint Vs Flow
Hybrid-Scrum considers Sprints for the Adaptive parts to deliver the work. On the other hand, in Hybrid-Kanban, it’s about flow.
When you add Waterfall into the project, this dynamic between Sprint and Flow will remain the same. However, the board management will differ.
Cadence
The cadence in Hybrid-Scrum will be based on Sprints. As you repeat Sprint after Sprint for your Hybrid-Scrum project, a cadence is set.
However, the cadence for a Hybrid-Kanban project can be set for a release. This release is time-bound, but not with any hard and fast rule.
Board Management
This is related to the first point. Boards used in Hybrid-Scrum can be the Sprint Planning Board and Sprint Planning Sheet views. There can also be current Sprint-related views, which can be used.
When you go for Hybrid-Kanban projects, the boards will be the Backlog Board and Backlog Sheet view. One can also use the Task Board and related view.
The CHAMP certification uses the MS Project Agile software, and hence, I’ve outlined these views.
Work Breakdown Structure (WBS)
Though there is no concept of WBS in Agile projects, when you go for Hybrid projects, WBS will come into play.
In the Hybrid-Scrum project, the work breakdown will be an integration of Sprint Backlogs and the traditional Work Breakdown Structure.
On the other hand, for a Hybrid-Kanban project, the work breakdown will be an integration of the Kanban Backlog (can be part of a Release) and the traditional Work Breakdown Structure. And remember, there are absolutely no Sprints here!
Baseline Management
In fact, baselines are not needed at all if you’re following pure Agile projects. However, baseline is a tricky area to manage for Hybrid projects.
Baseline management will slightly differ between Hybrid-Scrum and Hybrid-Kanban projects. If you’re reporting Earned Value metrics, then you’ve to baseline for both.
Work Limits
In Hybrid-Kanban, the Work in Progress (WIP) limit is explicitly set. This is to manage the flow of work. Kanban is always about flow. You can also say the scope gets limited with the WIP limit.
On the other hand, for Hybrid-Scrum, considering the Agile elements, the scope is implicit, not explicit, via the Sprint scope. The scope of the Sprint is set at the beginning of the Sprint.
Just-in-Time (JIT) and Pull
Both Scrum and Kanban are JIT approaches. But Kanban is more JIT, considering you can pull the work items immediately if your team has capacity.
In Hybrid projects, similar concepts will apply.
Custom Fields
To manage task differentiation and segregation, you need to have separate custom fields in Hybrid-Scrum and Hybrid-Kanban projects. The naming convention, field type, and flag setting have to be clear. You can see them as you proceed with the CHAMP course.
Conclusion
There are many other differences; however, I’ve highlighted some of them above. For example, one of the main charts for the Agile element in Hybrid-Scrum is the Burndown Chart, whereas in a Hybrid-Kanban project, it’ll be the Cumulative Flow Diagram (CFD).
At this stage, you might be wondering—how about the Hybrid-Scrumban projects?
This is where your skills learned and earned by managing Hybrid-Scrum and Hybrid-Kanban will come into play! A CHAMP certification is of definitive help. See here – how a successfully certified CHAMP learned and used Hybrid-Scrum and Hybrid-Kanban.
CHAMP Reviews and Success Stories:
- CHAMP Course: Excellent One for Mastering MS Project in both Traditional and Agile Environments
- CHAMP Success Story: A Niche Certification –Never Seen Anything Like this Before!
- CHAMP Success Story: One of the Best Hybrid-Agile Certification Courses I Ever Attended
ManagementYogi's CHAMP Certification Course:
No comments:
Post a Comment
Sign- or Log-in and put your name while asking queries in comments. Any comment is welcome - comments, review or criticism. But off-topic, abusive, defamatory comments will be moderated or may be removed.