
This is a quick video for you to get to know me as an Instructor, Agile Coach, and person. I share what motivates me to teach and coach. I share some personal info and some professional info about my Agile experience.
My promise about what you will be learning regarding Agile User Story Writing, Product Backlog, Sprint Backlog, and Relative Estimation.
Increase your understanding of why there is a Product backlog in Agile, Scrum Project Management and how understanding this will help you write better user stories.
You will learn the difference between a Product Backlog and A Sprint Backlog.
Learn the answer to one of the most common questions once people know what a Product Backlog is, "What is a Healthy Product Backlog?".
Three C's is a clever way to remember the three major components of a good User Story.
A great acronym to take User Stories to a whole new level. This lecture will go over INVEST and how it will make any user story great!
This lecture goes over the three questions that every User Story should answer.
Here is a template anyone can use for any User Story to help make sure you answer the three questions "Who? What? Why?". It is structured language to make getting started writing user stories happen now.
Acceptance Criteria is crucial for any User Story. Here we go over what makes good Acceptance Criteria for User Stories.
Those dependencies can really slow things down. Here are some basic ways to manage dependencies when writing User Stories.
The smallest form of work in Scrum. We discuss what Tasks are, when to use them, and even when not to use them.
Let's stop for a moment and think about what the real goal of Estimation is.
A lot of people think of estimation as hours of effort only. Let's use this acronym to have three dimensions to any body of work as we try to estimate it.
You think we do not know how to count?! What is relative sizing? Why do we use Fibonacci numbers in our estimating?
There are good ways and not so good ways to do anything. Here is one of the best ways to do relative sizing to get the most out of it.
What are the final steps in getting a User Story ready? Lets discuss how to put a final stamp of approval on any user story.
One of three social agreements in Scrum. Definition of Ready will help any team be more "crisp" and "clear" on what ready work looks like to them.
Another social agreement in Scrum. This one really helps make sure we are not forgetting to add any part of the work that gets work to Done in our story writing and estimating process.
Now you know what Definition of Ready and Definition of Done are lets discuss how to use them on a team.
Let's discuss a commonly misunderstood Scrum event and how it affects good User Story writing.
One of the most asked questions out there. Let's discuss what Scrum says and what actually happens.
Answers to one of the most common questions around Backlog Refinement. I give you the ideal and practical approaches to this question.
Practical tips on how to increase the quality of Backlog Refinement. Three Amigos is a great way to get more out of this ceremony.
For those whom have teams that have at least one person not collocated with the rest of the team I share one of my favorite tools to use with the whole team.
Remember the Why of User Stories! Remember to never stop learning! Never stop improving! Be Agile Now!
Join Be Agile Now community resources for user story writing mastery; connect via YouTube, Facebook, and LinkedIn, ask questions, share answers, and receive student coupons for future agile learning.
User Story writing is a key Agile skill to develop and master to increase flow and value through any Agile team. A lot of issues are solved with well defined and written user stories. Teams will have less false starts, less starting and stopping during Sprints, and increased flow and predictability.
Here are the components and context needed to write GREAT User Stories that are not taught anywhere else.
This course includes:
This course is about what the ideal Product Backlog is and how it benefits the whole team. The questions "What are the good parts of a user story?" and "What it should not be?" will be answered. A structured language template for user stories will be provided.
What is Relative Estimation? How it can be used to increase team predictability? And how not to use user story points in Agile Project Management? are all questions that will be answered too.
You will become familiar with Definition of Ready and Definition of Done as social agreements your teams will use to increase communication levels and collaborate more efficiently.
Last but not least this course will introduce you to me and the community I am building of Agile Practitioners whom want to constantly improve in all areas Agile.