PRINCE2 SCRUM Masterclass
PRINCE2 SCRUM Play nicely together!
Learn how to apply SCRUM and PRINCE2 – This course will show you the whole picture. Take the first step in guaranteeing your projects will not stumble and fall. Blending SCRUM and PRINCE2 will give you what you want and need, and you’ll know all you need just days from now…
Creative Studying with every Masterclass at your fingertips
All Access Monthly
Short study period required? Try All Access for a Month
PRINCE2 SCRUM Masterclass
Announcing the World’s First Video-based PRINCE2 Scrum training course: You earn 15 PDU's for PMBOK, and gain the knowledge needed to pass the Certified Scrum Master Qualification. This tasty step-by-step comprehensive video training, first walks you through the full Scrum framework from to-to-toe in clear articulate detail.
The use of Scrum by a product development team will help where the scope of the product to be developed may not be fully specified, yet rapid progress is required. Scrum accepts that improved accuracy can only be achieved through experience, and NOT by better estimating techniques.
The Daily Scrum is an internal team to inspect and adapt meeting to update state and resolve problems. Each day during the Sprint, the team has a short meeting called the Daily Scrum where they inspect their progress and make any necessary adaptations to maintain progress.
Teams maximize opportunities for feedback. Scrum Teams deliver products iteratively and incrementally
and Development Team optimize productivity and value by enforcing the rules and providing servant-leadership, removal of roadblocks and provides resources and assistance.
Scrum Artifacts represent work or value to provide transparency and opportunities for inspection and adaptation. Scrum Artifacts are designed to maximize key information transparency to provide the same understanding to all.
The Product Roadmap is not a formal aspect of Scrum but is common practice within the agile industry. You need to know where you’re going, otherwise, you’ll just wander aimlessly. Product Roadmap is a holistic view of product features that create the product vision.
An Epic is a high-level/”superuser” story that needs to be broken down into multiple stories at the delivery team level. Embryonic customer requirements can initially be large or vague.
A Release Plan is a high-level timetable for releasing a set of product requirements and it is used to mobilize the project team. A minimum viable product (MVP) is the minimum set of features that delivers value to the customer.
The plan is created by the collaborative work of the entire Scrum Team. Sprint planning is timeboxed to a maximum of eight hours for a one-month Sprint.
At the heart of Scrum is a Sprint – a Timebox of one month or less during which a “Done”, usable, and potentially releasable product Increment is created. All events in Scrum have timeboxed events with a maximum duration.
The sprint review is for the product owner to get organizational feedback on whether they are moving the product in the right direction.
The Project Board is accountable for the project’s outcome, and that is why the Project Plan is approved by the Project Board and why they make the important decisions and authorizations.
and simplified using PRINCE2 documents and controls where needed, and Scrum roles, artifacts, and events. Initiation Stage Plan – NOT needed since Sprint Zero is used to deliver products.
Starting Up a Project and Scrum activities. PRINCE2 and Scrum will be blended and simplified using PRINCE2 processes, documents and controls where needed, and Scrum roles, artifacts, and events.
PRINCE2 and Scrum will be blended and simplified using PRINCE2 documents and controls where needed, and Scrum roles, artifacts, and events.
PRINCE2 Scrum sprint zero is used to gain an understanding of the project, and create the vision, product roadmap and release planning. Scrum is a predictive framework and so the Project Initiation Documentation will contain a lot less information.
The Scrum Master or Coach (sometimes called a Project Facilitator), helps the Product Owner and Development Team – but is responsible for the Scrum process – not for results.
The Project Plan in PRINCE2 is a high-level plan covering the entire life of the project. The detail is developed in Stage Plans in a just-in-time manner. If Scrum is to be used for product development, then the Project Plan should include a preliminary Release Plan
Staged funding for the project budget, early sprints and releases used to justify the initial Business Case, and the Project Plan time and costs need only be ‘ear-marked’. The Business Case is tested during early sprints - money is still spent, but overall it may mean less cost, time and resource usage.
Scrum has no explicit method for managing risks, however, project-level risks are effectively managed implicitly by delivering in short Sprint intervals where both solution and process are discussed and improved. But there is a problem with risks that lie outside of the team, and although the Product Owner is responsible for managing these risks, they have limited authority
Changes ARE needed for this Theme. Be careful when flexing scope, to ensure it does not compromise product quality. The frequency of quality checking (reviews or tests), will influence project planning and affect the iterative and incremental delivery of the products and their release.
The Controlling a Stage process is where much of the PRINCE2 tailoring occurs - the Project Manager continuously monitors the effectiveness of the procedures and controls used.
If the Project Manager does not have the specialist experience/skills to define specialist products, then this can be delegated. The Project Manager needs just check that the Work Packages are defined and reviewed satisfactorily.
This process is an opportunity to assess the ongoing viability of the project and decide what the priorities are for the next management stage. This process ensures that high value (most beneficial) work from the product backlog is undertaken in preference to low-value work.
Managing Product Delivery handles the important interface between the Project Manager and the delivery team who will be using Scrum. The interface would need to be collaborative and transparent, where there is a collective agreement on what is to be produced and how this will be achieved.
Even when using Scrum, project closure is still likely to be a formal event. However, most of the information is already known and most of the work is already done due to the iterative and incremental nature of the scrum way of working.
Here are direct download links to all the side-by-side study information for this course. Download this at your leisure or review them in your browser.
these MS Project PRINCE2 Templates are already fully-loaded with the PRINCE2 Processes and Activities - Just tailor and blend them to suit your project needs - simple!
So you know all about PMBOK the framework that sits behind the world-beating Project Management Institute Project Management Certification (PMI PMP), well, it just got better...
About the teacher
David spent 25 years as a senior project manager for USA multinationals, and has deep experience in project management. He now develops a wide range of Project Management Masterclasses, under the Projex Academy brand name. In addition, David runs project management training seminars across the world, and is a prolific writer on the many topics of project management.