• Post category:StudyBullet-3
  • Reading time:10 mins read


Learn to manage requirements as professional scrum product owner using user stories ( Business Analysis ,Scrum Master)

What you will learn

Learn how to manage product backlog as part of an agile scrum team.

Explain what user stories are and how they will make your team or business more efficient

Learn what scrum is and why it is so powerful for producing high quality, user oriented and user friendly digital products.

Learn how to manage a product backlog and generate user stories.

Feel confident in implementing a product backlog for any service, maintenance or support team

Learn how to create a requirements backlog composed of user stories.

Understand the concepts behind the 3 Cs, DEEP and INVEST with respect to agile scrum.

A complete overview of the process of creating product vision and how you can use it to form your product backlog.

How to manage product backlog in four simple steps

Description

*All Glory to GOD for giving me the knowledge and experience to create this course*

COURSE SUMMARY

“Scrum Open, Professional Scrum™, Professional Scrum Product Owner™, (PSPO), Professional Scrum Master™, PSM, PSM I, PSM 1, etc. is the protected brand of Scrum . org. Our course and practice exams are neither endorsed by nor affiliated with Scrum . org.”

Three reasons to TAKE THIS COURSE right now!

The unique reasons for taking this course are:

1. Complete, Concise, Confident Overview of Product Backlog Theory – I cover the theory and give you examples of how the theory is used in industry as an Agile Product Manager

2. Confidence in using Agile Scrum – In a very simple way, I teach you the fundamentals of Agile Scrum and Product Backlogs with Agile Product Management and how to use it effectively in industry without going into a class room or spending a lot.

3. You get to ask me questions and see me respond to every single one of them thoughtfully!

Includes Narration from Randal Schaffer and Ted R. Brown.

What is Agile Scrum?

Agile is an iterative time boxed software development approach that focuses on building software incrementally from the beginning of a project rather than delivering it all at once at the end. Scrum is a framework that traces back to early 90s, which provides a framework for managing complex product and software development with iterative and incremental processes. Scrum is a very popular framework for implementing agile project management.

Who should take is course?


Get Instant Notification of New Courses on our Telegram channel.


Whether you are a developer, Professional Scrum Product Owner (PSPO) or simply someone who wants the answer to the question “what is scrum and how can I use it in my projects”, this is definitely the class for you.

What will I learn?

In this class, you will learn:

• Product backlog and user stories- I give you a complete overview of what product backlog in scrum entails as used in the business work place without having to do a face to face course saving you hundreds if not thousands of dollars.

• Concise overview of agile scrum – Including the scrum theory, the scrum team, the scrum process, product backlog and a lot more.

• The facts based on real industry experience and research – The correct terminology and use of scrum is essential to mastering it. My experience in industry and research into the topic has been used to give you a solid grounding in the most concise way possible.

The course is video based with no supporting document necessary.

How is the course structured?

Each section features an overview of a particular aspect of agile product management of requirements using the product backlog such as its origin, when you can use it and how you can use it in product development. Examples are included throughout the course with excellent quality video and audio. All is based real world experience.

*All Glory to GOD for giving me the knowledge and experience to create this course*

English
language

Content

Introduction
Introduction
Pashun Consulting Intro
Agile Scrum Recap
What is a Product Backlog?
Introducing User Stories and the Product Backlog
Section 2: Creating a Product Vision
what is a Product Vision ?
how to create the Product Vision ?
what is a vision board ?
EXAMPLE: Vision Board: The Sports Website
EXERCISE 1
Section 3: Creating a Product Backlog Step by Step
about Product Backlog Management
Introduction to User Stories and Acceptance Criteria
Step 1: Convert All Ideas into User Stories
about User Stories
what is DEEP ?
what is the INVEST principle ?
EXAMPLE: Initial Product Backlog for The Sports Website
EXERCISE 2
Step 2 – Prioritization
the importance of Prioritising the Backlog
EXAMPLE: A Propritized Product Backlog for the Sports Website
EXERCISE 3
Step 3 -Estimate The Product Backlog
how to carry out Product Backlog Grooming and Estimation
estimating with Story Points
EXAMPLE: An estimated Product Backlog for The Sports Website
Step 4 – Refining and Grooming Your Product Backlog
EXAMPLE: A Refined Backlog for the Sports Website
EXERCISE 4
Tips 1 -7
Introduction: Tips & Strategies
how to Capture Stories in Meetings
Tip #1: PO Should Know That He/She Will Be Expected To Present Enough Work That
Tip #2: Avoid Scheduling Backlog Refinement During The First Or Last 20% Of The
Tip #3: The Backlog Items Must Be Fine Grained And Properly Understood By The PO
Tip #4: Treat Every Backlog Refinement Meeting Just Like The Beginning Of Sprint
Tip#5: Everyone Should Understand That Estimates Are Provisional Until A User St
Tip #6: Strive To Optimize Your Time During The Meeting
Tip #7: Remember That Backlog Items Are Actually A Collaboration Between The PO
Tips 8-14
how to Manage Changing Requirements
Tip #8: Keep Your Eye On The Goals Of The Meeting
Tip #9: Get Volunteers For Action Items For Any Unknowns Or Big Risks
Tip #10: You’re Definitely Free To Split User Stories During This Meeting
Tip #11: Everyone Should Understand That Product Backlog Order Is Provisional Un
Tip #12: Be Brave To Discuss A Couple Of Items Farther Down The Backlog
Tip #13: Let The Dev Team Review The User Stories To Be Discussed About 24 Hours
Tip #14: Have A Mini Backlog Refinement Prior To Holding The Backlog Refinement
Tips 15-21
how to Prioritise for the Release
Tip #15: Track Progress Using Release Burndown Charts
Tip #16: Feel Free To Introduce Late Breaking User Stories. As You Do That, Stri
Tip #17: Use One Issue Tracker and One Backlog!
Tip #18: Watch Out For Too Many Changes And Limit Your Scope
Tip #19: Ensure To Experiment With The Amount Of Refinement, Which Your Team Doe
Tip #20: Ensure To Retrospect, Inspect And Then Adapt
Tip #21: Transparentize, Prioritize And Stick To The Product Vision
EXAMPLE: Complete example of Product Backlog: The Sports Website
Conclusion
FEEDBACK: Reviews and Discussion
Thank you again for taking this class!
BONUS MATERIALS
BONUS LECTURE