Agile Foundations - getting to Done

Got projects? Use ideas from Scrum, Kanban, XP, and Lean to communicate requirements, plan, and monitor great projects.
4.0 (11 ratings)
Instead of using a simple lifetime average, Udemy calculates a
course's star rating by considering a number of different factors
such as the number of ratings, the age of ratings, and the
likelihood of fraudulent ratings.
206 students enrolled
57% off
Take This Course
  • Lectures 31
  • Length 4.5 hours
  • Skill Level Beginner Level
  • Languages English
  • Includes Lifetime access
    30 day money back guarantee!
    Available on iOS and Android
    Certificate of Completion
Wishlisted Wishlist

How taking a course works


Find online courses made by experts from around the world.


Take your courses with you and learn anywhere, anytime.


Learn and practice real-world skills and achieve your goals.

About This Course

Published 11/2013 English

Course Description

Got projects? This course gives you the practical techniques you can use to get your work done - for software, or beyond.

  1. Stakeholders: Including Customers and Users
  2. User Stories: Product Adaptation
  3. Prioritization, Estimation: Planning and Adapting
  4. Planning: Incremental Development
  5. Work-in-progress (WIP) + Quality
  6. Teamwork: Creating Shared Understanding
  7. Teamwork: Shift in Roles. +Distributed Teams I
  8. Feedback: Lean, scaling frameworks: Process & Project Adaptation
  9. Leadership: Culture & Mindset & History

After this course you will be able to

  • Understand the values behind several Agile methods such as Scrum and Kanban
  • Relate to your stakeholders (personae, story maps, some Innovation Games®)
  • Document requirements (User Stories)
  • Prioritize, Estimate, Plan, and Track your plans

Continuing Education Credits? (PDUs)

This course also aligns with the PMI-ACP® program so gives you some of the hours you need to qualify for their exam, as well as class C PDUs to maintain your existing PMI certification. This course by itself does not get you certified, but it makes you smarter in your quest to do so, or to simply enhance your skill at work.

To claim them go to PMI's CCRS PDU claim website, log in, report PDUs, select class C (Self directed learning), and enter Agile Dimensions or Udemy in the provider field. There are some limits on how many hours of each type you can use to renew your certification (for example, 15 of the 30, for example).

See ya on the forum!

What are the requirements?

  • Internet connection for browsing course material

What am I going to get from this course?

  • Identify four classes of stakeholders
  • Communicate Requirements
  • Plan projects and iterations using the right mix of kanban, Scrum, and enterprise agile to meet the needs of your team
  • Track progress with charts to trigger the team to take action if things fall behind
  • Use bi-weekly lessons learned to continually improve your process

Who is the target audience?

  • Business Analysts
  • Software Testers
  • Software Developers
  • Project Managers
  • Managers
  • Software Engineers
  • Anyone with projects to coordinate

What you get with this course?

Not for you? No problem.
30 day money back guarantee.

Forever yours.
Lifetime access.

Learn on the go.
Desktop, iOS and Android.

Get rewarded.
Certificate of completion.


Section 1: Overview

Welcome!! In this video we'll define what Agile is, what flavors there are, and how it can help you get your work done.


Let's see what Agile is about by defining some terms and touching upon some different styles of project management.


Follow this step by step overview of the Agile process as we walk though our Agile3d Factory(tm).


This lesson shows you a high level view of how the detailed concepts fit together.

6 questions

Let's see if we can remember some o those buzzwords

Section 2: Know your Customer

    4 types of stakeholders


    Standards covered

    IC13-4.1 - Including Customers & Users

    PM11-D2.1 - Stakeholder Needs


What is the guiding purpose of our project? What statement holds the cloud of requirements together?

5 questions

Remember the word 'PIPE'? What does it stand for?

__Principals__ (hint - think $)



__End__ __Users__

Section 3: Build the Right Thing

How can we best describe requirements so they are clear to the customer and to our team?


User Stories are the basic building blocks of Agile projects.

  • Epic / Feature / Story / (task)
  • 3 C's
  • RGB
  • Product Box

Learning Card Activity:

  1. Write a story.
  2. Read 2 others

Grade yourself:

  • 5 points - has 3Cs and RGB
  • 7 points - has INVEST
  • 9 points - small

What seperates good stories from bad? In this mode we will cover William Wake's INVEST mneumonic, and how it can apply to your requirements.

5 questions

This quiz confirms you know how to write requirements in the form of a good User Story.


What comes first? After this module you will have specific tools to help you prioritize your list of work, which is key to Agile.


This module shows how to rank what gets done first, next, or not at all!

Section 4: Planning

Customer Value and effort to build something may be different. Let's focus our business people on setting the priorities, and show how the engineers and team can quickly estimate so we'll be ready for planning.


Learn how Agile teams get everyone's input to produce quick and effective estimates.


How big are the things we are working on? Here is a good way to estimate our work so we can plan better.

Don't stress too much about getting it perfect the first time. After 3 to 5 iterations your estimates will become more consistent. Before that any more thinking is s waste of time. We really just don't know until we get into this technology with this team. But with experience our estimates become very accurate. It is common for them to be off by 60% for brand new team, and to converge to be within 15% after a few sprints.

This graph shows the actual hours per 'story point' varies at the beginning for this team, but then not only becomes more consistent, but more productive (fewer hours needed to finish each story point)


How much can we do? This module shows how decide how much we commit to, how many things are "stretch goals", and what has to wait for next time.


Okay, everything has been building up to this point. It's time to sketch our plan so we can later effectively take action if things are falling behind.


How much will fit in our plan? What is the concept of 'Speed buffer?'


These final details help you select and adapt the right process for you. 1? 10? 100?


We wrap up our planning module by showing how to view multiple teams, and how to avoid 4 deadly mistakes.


You've sketch out your big picture release plan. Another couple of weeks have passed, and now it's time to another iteration. Here is a checklist to get you started.

5 questions
Section 5: Monitor Execution

Quality is key to keeping our team running efficiently and to delighting our customers. How can we do our work efficiently and build quality into the way we work?


The daily stand-up meeting is a key driver for collaboration in the coming day.


"Big Visible Indicators" - "Information Radiators" are terms you may hear that describe the workspace of an alert Agile team..


At the end of our two week slice we demonstrate our work so we can be sure we got it right. If any changes are needed we can decide if we should include them later. Customer feedback helps us build the right thing.

We also get the team's feedback on how we can tune our process to work smoother in the next two weeks. After a few years of doing that you will have a well oiled machine!


What went wrong? Or really, how can things go better? Retrospectives help the people doing the work find improvements to streamline their work. Imagine the cumulative effect of 2 improvements every two weeks for a year! Here's how.

Test your Progress on Monitoring Execution
5 questions

Let's learn by doing. Create some imagined problems for your team, and illustrate how they would show up in your graphs.

Section 6: Putting it in Action

Practice sustainable pace as you repeat each sprint and release. Energized knowledge workers produce more. Overly stressed ones produce defects.

Wrap up
Section 7: Bonus - Build Quality In

How do testers serve an Agile team to build quality in?

Section 8: Bonus - Teamwork and Leadership

Some of the theory behind our agile techniques comes form a century of industrial engineers looking for ways to work more efficiently. By seeing the past, we get a feel for some of the reasons behind the Agile practices we've learned.


One of the biggest problems I've seen with teams over the years is not the planning or engineering, but hidden conflicts. By knowing folks may see the same issue though different styles we can avoid some common problems that can make work harder than it needs to be.

Students Who Viewed This Course Also Viewed

  • Loading
  • Loading
  • Loading

Instructor Biography

AgileBill Krebs, Distributed Agile Coach, SPC, PMI-ACP, CSP, ICE-AC

“AgileBill” Krebs has over 20 years of programming, performance, project management, and training in the IT industry at 5 IBM labs, Davisbase, and Allscripts. He has used agile since 2001, and taught it to over 2,000 people worldwide. He has presented at agile conferences, IBM Research, and conferences on education.

Bill's certifications and groups include the "grand slam" of four advanced certifications in Agile - SPC, PMI-ACP, CSP, and ICE-AC. I also holds 7 other certifications in related areas and is pursuing a Master's degree in Education Technology. He hosts the Distributed Agile Study Group and is a member of ALN, the Scrum and Agile Alliances, ACM, PMI, and more. Besides speaking at conferences, Bill serves as an enterprise Agile Coach in the healthcare industry.

Ready to start learning?
Take This Course