This course covers a multitude of topics from what scrum is from a definition standpoint to how it stacks up to Waterfall as well as other Agile methodologies. Throughout the lectures, you will see definitions, key terms and gain access to downloadable resources and external links.
The first section of this course talks about what Scrum is, who the core roles are, how the core roles differ from non-core roles and how to resolve conflict amongst all team members.
In the next area of the course, you will learn about the six Scrum Principles and how they are helpful in managing time throughout the lifecycle of the project. These six Principles include Empirical Process Control, Self-Organization, Collaboration, Value-Based Prioritization, Time-Boxing and Iterative Development.
Then, we will cover the five Aspects of Scrum projects. These tell how the team members should respond and be structure. The five Aspects include Organization, Business Justification, Quality, Change and Risk.
In the second half of the course, you will be introduced to the five Phases that each project undergoes from Initiate to Release. In these five Phases, there are a total of nineteen Processes. There are at least two Processes in each Phase. The Processes all progress from Project Vision Statement to the Retrospect Project events and activities.
At the end of the course, we will take a look at how Scrum measures up against other methodologies, including Waterfall, TDD, Crystal and more.
It is our hope that you truly enjoy this course and have huge success in your profession.
In this brief lecture, you can meet me, your instructor. My name is Beverly Reynolds and I come to you with 20 years of instructional design and project management background. I am excited to share this course with you and hope you enjoy the lecture content!
You will hear that the main focuses of this course centered around the Scrum main principles, aspects, phases and processes implemented on a daily basis. During these lectures, you will see why each of these are essential to EVERY PROJECT.
It is my hope that you will be able to not just memorize the materials to pass your exam(s), but that you will be able to apply the concepts to YOUR professional work. As always, thank you for your support! I look forward to visiting with you several times throughout the lectures of this course.
In this lecture we will overview scrum and provide you with a list of exams as of this recording. The exam acronyms and titles are subject to change.
No matter what, this course will provide a good basis for what scrum is, what the events are and who are the key roles - regardless of whether they are core roles or non-core roles.
In total, you will be able to picture yourself in one of these roles and see how you can best move the project along to release in the field or to the user base.
Do you know what constitutes a project? If not, this lecture is for YOU! This lecture talks about the difference between a project, program and portfolio (in order from smallest entity to largest entity). It will also detail the history of Scrum, where it began and why it was started.
This lecture will give you an idea of the background of Scrum as well as how it can be used in any enterprise, company or organization - regardless of industry or size.
This lecture will tell you about the key roles of scrum as well as basic conflict resolution. By the end, you will know about the core roles and non-core roles. Every project will have conflict, this lecture will take a look at how scrum views conflicts and how to resolve.
Conflict is a part of every team - even your team - but how you handle each challenge can and will make or break the success of the team and the project.
In this lecture, we will discuss the Principle of Empirical Process Control and why it is key. There are three key terms in this principle, including: Transparency, Inspection and Adaptation. You will see and hear why these are important.
All levels of the organization, managers and stakeholders should be able to see the progress made by the team at any point. There at several ways in which this can be achieved, and we will detail them in this lecture.
Here we discuss the Principles of Self-Organization (e.g., innovation and shared ownership), Collaboration (examples to include awareness, appropriation and articulation) and Value-Based Prioritization, as well as why they are essential to YOUR project.
These are principles that are absolutely key to know and to understand, as they tell about how a team should be structured for maximum business value.
Time-Boxing and Iterative Development are MUST HAVES for any project - we will provide you with the reasons behind this statement. Keep in mind that scrum is about ITERATIVE or rapid development lifecycle.
Regarding Time-Boxing, you will see the events that are time boxed, as well as those that are not time-boxed.
As for Iterative Development, you will see that this is a change management practice that focuses on the customer needs by creating short sprints with effective production goals.
In this lecture, we will detail the Aspects of Organization and Business Justification and how they help you align your project. What are the roles that are involved in EVERY scrum project? Which roles have a stake in the game and which ones do not have any direct involvement? Are the roles core roles or non-core roles?
What does business justification mean? What are the considerations when a project is justified (in terms of existence)? We will answer these and more in this lecture.
In Part 2, we continue the Aspects discussion - this time regarding Quality, Change and Risk.
Quality is key to any endeavor, whether a software implementation or construction project.
Change is inevitable and planned for in each and every scrum project. Scrum is the best means for dealing with changes in team, requirements and possibly rules.
Risk should be assessed and mitigated along each step of the way during the project lifecycle. We will take a very detailed approach to risk, since these are things that negatively affect the success of outcome.
Here you will see a quick overview of the 5 Phases and 19 Processes of scrum. You will also get a 'flavor' for the order of these items for maximum business value to the end of the project. There are inputs, tools and outputs of every process of each of the phases of scrum. All mandatory events or activities are marked with an asterisks.
We will be detailing all phases in the coming sections and lectures. See you soon!
In this lecture, you will learn about Business Justification, Trial Project, Proof of Concept and JAD Sessions. Once the project has a basic justification, it may be important to have a wireframe or proof of concept created. This lecture will help you see how the project is initiated, hence the first phase of any scrum project.
It is important that every project is kicked off right from the very start. You will learn about initial success here!
In this lecture, we will discuss SWOT Analysis, GAP Analysis, Backlog Types and the Project Vision Statement. Now the project is beginning to take shape - do NOT worry that these terms are new to you. This lecture will detail each one for you by the end.
Here you will hear about the SGB or Scrum Guidance Body and forming a new scrum team. Anytime a new team is formed under a new methodology, the team goes through challenges. These challenges are to be expected. Knowledge is POWER!
It is in this lecture that you will learn about Change Requests, Risk Overview, Risk Identification, Risk Assessment and Risk Prioritization. What is a Change Request? Does every project have risks? These questions and more will be answered within this lecture.
In this portion of the course, you will learn about Issues, User Stories and Prioritization Methods. The idea of user stories and creation may be new to you. They are simply personas that will use the piece of functionality being developed (or feature). You will see what a user story is and the importance of including the benefits too.
In this lecture we will discuss User Story Workshops and Planning Poker. Sometimes it is hard to come up with the personas for a user story, so the team holds User Story Workshops and determines what it will take to develop that feature or feature set.
In this lecture, we will detail Fist of Fives, Index Cards and Tasks / Task Lists. Once user stories are in place, the team then discusses the tasks needed on behalf of the team members to not only achieve completion, but also to meet the acceptance criteria.
In this lecture, we will talk about Team Velocity, Sprint Planning Meeting and Burndown Charts. These are the tools for planning and measuring the progress of the team.
Scrum is all about the idea of transparency to stakeholders and management. This is essential from a memorization and application standpoint.
Implement is the 3rd Phase in the scrum lifecycle. This is where the work actually happens in every project! The team meets daily via the Daily Standup Meetings and they discuss what they did since the last meeting, what they will do today and any impediments. Here you will see how these details are tracked on the Scrumboard and what this physical board looks like.
Another important aspect of this lecture is the columns of this board. They are used for total transparency - even outside the team.
In this section of the course, we will detail the Scrum of Scrums (know who facilitates this meeting and who attends) and Sprint Review Meeting (be sure to understand the intent of such a meeting and the duration).
How does the SOS or Scrum of Scrums differ from the Daily Standup Meeting? What are the roles involved in each type of meeting? When should each meeting take place in the lifecycle of the project?
Throughout this lecture, you will learn about ESVP, Speedboat and Retrospect Sprint Meeting. You will see and hear how to make improvements from sprint to sprint based on team input.
Retrospect Sprint differs from Retrospect Project. Both are meetings, but the Retrospect Sprint meetings are time-boxed. Both include meetings that help to improve future time frames.
In this lecture we will wrap up the scrum Phases and tell you about how deliverables are shipped. There are two processes in this phase: Ship Deliverables and Retrospect Project. In the Ship Deliverables process, you determine the method of deployment. In the Retrospect Project process, you hold a non-time-boxed meeting to discuss the project and areas for improvement.
How do you complete a project? How do you make improvements of the work done for the NEXT project?
This is a very brief lecture or movie to encourage you through the end of this course!
You are doing a FABULOUS job and I believe that every student needs encouragement to push through the vast amount of content.
In this area of the course, you will learn about additional Agile Methodologies, such as Kanban, Lean, DSDM, Crystal and FDD. You will be able to know which of the methodologies uses the color spectrum and which limits the number of items in a Work in Progress state?
Are these new terms to you? If so, not for long. I have even been asked about I I knew what these were in a Scrum Master job interview. You might also want to do some additional reading outside these lectures on these terms too.
I come to you with 20 years of experiences in instructional design and project management within top Fortune companies. Most recently I started my own design business, authored and illustrated (and published) my own children's book and decided to once again take up teaching...this time to benefit my own business.