Agile Software Development: An Introduction

The Agile method allows modern development teams to rapidly build software that is both efficient and effective. This course provides a comprehensive introduction to this approach to software development. The course begins with the major teaching points. Next, the methodology is presented, along with the rationale for its adoption. Included here is the Agile Manifesto. This section is followed by one that discusses how Agile teams are structured and types of development projects that are a good fit for Agile. The course delves into the leading challenges faced by Agile software developers today and the best practices that teams should incorporate into their development projects. The advantages that Agile brings to software development are then covered. The course concludes with key principles for Agile.

Scrum Master (Part 2 of 2): Artifacts and Sprints

Explore the three roles, three artifacts, and four ceremonies to manage software development that make up Scrum. Discover how these principles interact with the Scrum implementation of the Agile framework with examples of how the ceremonies work. Understand the importance of changing the culture and behavior of the organization to reap the maximum benefits from Agile and why it is a key factor in Scrum. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * Lesson 1: (a) Scrum Artifact: Project Backlog; (b) Product Backlog Example: Airline Reservation; (c) Scrum Artifact: Sprint Backlog; (d) Sprint Backlog Example; (e) Scrum Artifact - Product Implement; (f) Product Increment Example; (g) Scrum Artifact Summary; (h) User Stories and Requirements; (i) What Is a User Story?; (j) Do User Stories Replace Existing Requirements?; (k) User Stories Summary. Lesson 2: (a) Scrum Ceremonies; (b) Sprint Planning; (c) Daily Scrum; (d) Three Questions; (e) Sprint Review; (f) Spring Review Content; (g) Sprint Retrospective; (h) Four Questions; (i) Scrum Ceremonies Summary. Lesson 3: (a) Agile Estimation; (b) The Truth about Estimating; (c) Estimation Metrics; (d) Estimating Using Story Points; (e) Estimation Poker; (f) The Rules of Estimation Poker; (g) Benefits of Planning Poker; (h) Estimating a Team's Capacity; (i) Velocity - Estimating Duration; (j) Agile Estimation Summary. Lesson 4: (a) Planning a Release with Scrum; (b) Release Planning Activities. Lesson 5: (a) Planning a Sprint; (b) Sprint Planning Meeting; (c) Sprint Planning - Tasks and Time; (d) Granularity of Release vs. Sprint Planning; (e) Populating a Sprint; (f) Sprint Planning Summary. Lesson 6: (a) Starting the Sprint; (b) Continuing the Sprint; (c) Track Progress - Burndown Chart; (d) Updating the Burndown Chart; (e) Scrum Task Board; (f) The Daily Scrum; (g) Protecting the Team During the Sprint; (h) During the Sprint; (i) Testing within a Sprint; (j) Sprint Execution Summary. Lesson 7: (a) Sprint Closure; (b) Sprint Review; (c) Sprint Retrospective; (d) Sprint Closure Summary.

Agile/Scrum Essentials for Practitioners

There is a lot of buzz today around Agile as a different approach to managing projects, specifically software development and implementation projects. Unfortunately, when Agile was first being introduced, it was set in opposition to traditional, or waterfall, project management approaches. This caused an unnecessary and counterproductive rift that was mostly due to a lack of understanding and a few overzealous evangelists. Today Agile is more mainstream, particularly in IT, and much of this division has begun to erode. However a comprehensive understanding of the Agile mindset and a well-known practices like the daily scrum, is foundational to truly leveraging the benefits of Agile and creating an environment that if both fun to work in and produces high-quality business results. This session will give you the foundational background that will help you understand how Agile is different and why certain practices make more sense and result in more productive teams. You will see how Agile is as much of a mindset as it is a project management framework and how adopting Agile can turn your next project into a success. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * Lesson 1: (a) Guide Introduction; (b) QandA Product Backlog. Lesson 2: (a) Success Hasn't Come Easy; (b) Today's Business Environment; (c) Features/Functions Used; (d) The Swing of the Pendulum; (e) The Unintentional Mousetrap; (f) Landscape Affects the Approach; (g) The Discipline/Process Curve; (h) Emphasis and Constraints. Lesson 3: (a) A Definition of Agile; (b) Agile is Iterative; (c) Agile is Iterative (cont.); (d) A Family of Agile Methods; (e) Building Blocks of Agile. Lesson 4: (a) The Agile Manifesto; (b) Agile - The 12 Principles; (c) Agile - 12 Principles (cont.); (d) Agile - Proven Practices; (e) Agile - Practices (cont.); (f) Agile - Key Results and Benefits. Lesson 5: (a) Proven Sciences and Disciplines; (b) Serial Large - Iterative Small; (c) Agile is NOT for Lightweights. Lesson 6: (a) Origins of Scrum; (b) Origins of Scrum (cont.); (c) A Simple Starting Methodology; (d) Starting Methodology (cont.); (e) Scrum Elements; (f) Scrum Iterative and Agile Flow; (g) Cascading Plans. Lesson 7: (a) Scrum Elements - Team Roles; (b) Scrum Team Basics; (c) A High Performance Team Model; (d) Team Stages and Leadership Style. Lesson 8: (a) Team Roles and Constituency; (b) The Scrum Terms; (c) Team Role 1: The Product Owner; (d) Team Role 1: The PO (cont.); (e) Team Role 2: The Scrum Master; (f) Team Role 3: The Delivery Team; (g) Team Role 3: Delivery (cont.); (h) The Team Operating Agreement; (i) RACI Chart for a Scrum Team; (j) Scaling Scrum Teams. Lesson 9: (a) Demo: The Scrum - Backlog; (b) Demo: The Scrum - WIP; (c) Demo: The Scrum - Finish.

Scrum Master (Part 1 of 2): Waterfall to Agile

Explore the history of the Waterfall method, a linear software management framework, and discover what projects work well with it. Compare Waterfall to the incremental delivery framework Agile and discover which projects are conducive to each framework. Become familiar with the Agile philosophy, core values, and principles as well as circumstances where Agile shines. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * Lesson 1: (a) The Waterfall Method; (b) Try This Planning Analogy; (c) Iterative Development Defined; (d) The Anatomy of an Iteration; (e) Iterative Planning; (f) Waterfall and Iterative Comparison; (g) So...What's the Difference?; (h) Executing a Waterfall Project; (i) Executing an Iterative Project; (j) Iterative Deep Dive; (k) Iterative Deep Dive (Cont.); (l) Summary. Lesson 2: (a) The Genesis of the Agile Framework; (b) Agile Values; (c) Individuals and Interactions; (d) Working Software; (e) Customer Collaboration; (f) Responding to a Change; (g) Agile Philosophy. Lesson 3: (a) What Is Scrum?; (b) Scrum Values; (c) Scrum Principles; (d) Scrum Framework. Lesson 4: (a) ScrumMaster; (b) Serving the Product Owner; (c) Serving the Development Team; (d) Serving the Organization; (e) Characteristics of a ScrumMaster. Lesson 5: (a) Product Owner; (b) Product Backlog. Lesson 6: (a) The Development Team; (b) T-Skillset Model; (c) The Team; (d) Building High Performing Teams.

SCRUM Product Owner (Part 2 of 2): Change and Sprints

The product owner serves as voice of the customer to drive solutions in the context of business value. This course will discus change and quality, risk, sprint planning, review, and deliverables. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * Lesson 1: (a) Supporting Change; (b) Unapproved and Approved Change Requests; (c) Flexibility vs. Stability; (d) Integrate Change; (e) Quality Definition; (f) Acceptance Criteria; (g) Definition of Done; (h) Quality Management in Scrum. Lesson 2: (a) Risks vs. Issues; (b) Risk Attitude; (c) Risk Identification; (d) Risk Assessment; (e) Risk Prioritization; (f) Risk Mitigation; (g) Risk Burndown Chart; (h) Minimizing Risk in Scrum. Lesson 3: (a) Sprint Planning Meeting; (b) Two Parts of a Sprint Planning Meeting; (c) Planning Poker; (d) Fist of Five; (e) Points for Cost Estimation; (f) Other Estimation Techniques; (g) Use Index Cards; (h) Decomposition; (i) Determine Dependencies; (j) Establishing Estimation Criteria; (k) Creating the Sprint Backlog; (l) Scrum board; (m) Sprint Burndown Chart; (n) Velocity; (o) Sprint Tracking Metrics; (p) Outputs from Sprint Planning Meeting. Lesson 4: (a) The Daily Standup Meeting; (b) Three Daily Questions; (c) The War Room; (d) Outputs from Conduct Daily Standup; (e) Collaboration During a Sprint; (f) Product Backlog Review Meetings; (g) Facilitate Communications. Lesson 5: (a) Shipping Deliverables; (b) Outputs from Ship Deliverables; (c) Sprints Summary; (d) Sprint Review Meeting; (e) Outputs of Sprint Review Meeting.

SCRUM Product Owner (Part 1 of 2): Overview and Principles

In this course, you'll learn to drive optimal business value, provide clarity to the team about priorities, objectives and business alignment. This course discusses the role of product owner, requirements, prioritized product backlog. overview, roles, estimates, product backlog, release plan and user groups * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * Lesson 1: (a) Scrum Overview; (b) Project Management as a Discipline; (c) Software Development Lifecycle Model; (d) Traditional PM; (e) Agile History; (f) Agile Manifesto Principles 1-5; (g) Agile Manifesto Principles 6-12; (h) Agile Methods; (i) Scrum History; (j) Scrum Benefits; (k) Scrum Scalability. Lesson 2: (a) Scrum Principles; (b) Empirical Process Control; (c) Self-Organization; (d) Collaboration; (e) Value-Based Prioritization; (f) Time-Boxing; (g) Iterative Development; (h) Organization; (i) Initiate; (j) Plan and Estimate; (k) Implement; (l) Review and Retrospect; (m) Release. Lesson 3: (a) Scrum Roles; (b) Identify the Scrum Master; (c) Scrum Master Responsibilities; (d) Scrum Master Authority; (e) Identify the Product Owner; (f) Product Owner Responsibilities; (g) Product Owner Authorities; (h) Forming the Scrum Team; (i) Scrum Team Responsibilities; (j) Scrum Team Authorities; (k) Identify the Stakeholders; (l) Fundamental Differences with Traditional PM. Lesson 4: (a) Importance of a Project Vision; (b) Create the Project Vision; (c) Project Vision Meeting; (d) JAD Sessions; (e) SWOT Analysis; (f) Gap Analysis; (g) Just Enough; (h) Outputs for Project Vision Meeting; (i) Estimating the Product Backlog; (j) Accuracy vs. Precision; (k) Size vs. Duration; (l) Estimates vs. Commitments. Lesson 5: (a) Value-Driven Delivery; (b) Factors; (c) Product Backlog Essentials; (d) Prioritized Product Backlog; (e) Product Backlog Items; (f) Prioritize the Product Backlog; (g) Business Justification Techniques; (h) MoSCoW analysis; (i) 100 Point Method; (j) Kano Analysis; (k) Continuous Value Justification; (l) Definition of Done; (m) Responsibilities. Lesson 6: (a) Conduct Release Planning Meeting; (b) Outputs of Release Planning; (c) Piloting Plan; (d) Organizational Deployment Method; (e) Communications Plan; (f) Release Burndown Chart; (g) Release Burndown Chart: Example; (h) Create the Prioritized Product Backlog; (i) Develop Epic(s); (j) Epics and Personae; (k) User Story Meetings and Workshops; (l) Writing User Stories.

SCRUM Developer (Part 2 of 2): Implementation and Review

This course introduces the core activities of SCRUM, including the fundamental concept of iterative development, collaborating with stakeholders, and managing risks. The SCRUM concepts covered will be user stories, tasks, daily standup. manage sprint backlog, retrospect, and review * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * Lesson 1: (a) User Story Meetings and Workshops; (b) Task Planning Meeting; (c) Write User Stories; (d) User Story Acceptance Criteria; (e) Outputs for Writing User Stories; (f) User Group Meetings; (g) Planning Poker; (h) Fist of Five; (i) Points for Cost Estimation; (j) Other Estimation Techniques; (k) Outputs from Approve, Estimate and Commit Stories. Lesson 2: (a) Two Parts of a Task Planning Meeting; (b) Use Index Cards; (c) Decomposition; (d) Determine Dependencies; (e) Outputs for Create Tasks; (f) Task Estimation Meetings; (g) Establish Estimation Criteria; (h) Output for Estimating Tasks. Lesson 3: (a) Learning Objectives; (b) Terms to Know; (c) The Scrum Cycle: Plan and Estimate; (d) Create the Sprint Backlog; (e) Scrum board; (f) Sprint Burndown Chart; (g) Velocity; (h) Sprint Tracking Metrics. Lesson 4: (a) Conducting the Daily Standup Meeting; (b) Three Daily Questions; (c) The War Room; (d) Managing Distributed Teams; (e) Outputs from Conduct Daily Standup. Lesson 5: (a) Create the Deliverables; (b) Build Deliverables; (c) Refactoring; (d) Outputs for Creating Deliverables; (e) Product Backlog Review Meetings; (f) Facilitate Communications; (g) Outputs of Grooming the Backlog. Lesson 6: (a) Projects, Programs, and Portfolios; (b) Scrum of Scrums; (c) Four Questions per Team; (d) Outputs from Scrum of Scrums; (e) Sprint Review Meeting; (f) Track Overall Progress; (g) Outputs of Demonstrate and Validate Sprint. Lesson 7: (a) Conduct the Retrospect Sprint Meeting; (b) Explorer-Shopper-Vacationer-Prisoner; (c) Speed Boat; (d) Metrics and Measurement Review; (e) Outputs from Retrospect Sprint; (f) Terms to Know; (g) The Scrum Cycle: Review and Retrospect.

SCRUM Developer (Part 1 of 2): Concepts and Roles

This course introduces the core activities of SCRUM. This course will introduce you to the core principles, values, and solutions for collaboration and teams. It will highlight value-based priority of features and go over concepts and principles, phases, vision, release planning, and backlog. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * Lesson 1: (a) Scrum Principles; (b) Empirical Process Control; (c) Self-Organization; (d) Collaboration; (e) Value-based Prioritization; (f) Time-Boxing; (g) Iterative Development; (h) Core Aspects. Lesson 2: (a) Scrum Overview; (b) Project Management as a Discipline; (c) Software Development Lifecycle Management; (d) Traditional PM; (e) History of Agile; (f) Agile Manifesto Principles 1-5; (g) Agile Manifesto Principles 6-12; (h) Agile Methods and Scrum History; (i) Scrum Benefits; (j) Scrum Scalability; (k) Scrum Phases; (l) Initiate; (m) Plan and Estimate; (n) Implement; (o) Review and Retrospect; (p) Release. Lesson 3: (a) Create the Prioritized Product Backlog; (b) MoSCoW Analysis and Paired Comparison; (c) 100-Point Method; (d) Kano Analysis; (e) Other Considerations for Prioritization; (f) Outputs of Planning the Backlog. Lesson 4: (a) Create the Project Vision; (b) Project Vision Meeting; (c) JAD Sessions; (d) SWOT Analysis; (e) Gap Analysis; (f) Outputs of Creating a Project Vision. Lesson 5: (a) Develop Epic(s); (b) Epics and Personae; (c) Outputs from Developing Epics; (d) Form the Scrum Team; (e) Outputs from Forming the Scrum Team. Lesson 6: (a) Identify the Scrum Master; (b) Identify the Stakeholders; (c) Conduct Release Planning; (d) Outputs of Release Planning; (e) Other Considerations for Prioritization.