AGILE Techniques

The course is part of these learning paths

DevOps Playbook - Moving to a DevOps Culture
course-steps 6 certification 2 lab-steps 1 description 3
play-arrow
Start course
Overview
DifficultyBeginner
Duration37m
Students76
Ratings
4.9/5
star star star star star-half

Description

Course Description

AGILE has become the de facto framework for innovation at scale,  and knowing AGILE processes are a baseline skill for any organization looking to leverage the speed and flexibility of cloud services. The introduction to AGILE course covers a broad spectrum of topics from how to hold an AGILE meeting to deconstructing its key concepts, techniques and best practices.

In this short course, made up of ten lectures, we introduce you to the key concepts, roles, and techniques of the AGILE methodology so you will be able to recognize and explain the agile process in work situations.

Intended Audience

This course will suit anyone interested in learning what AGILE is and how AGILE techniques are used in development projects.

Learning Objectives

  • Recognize and explain the AGILE methodology
  • Recognize and apply agile principles and how they relate to software projects
  • Recognize and apply the AGILE roles and responsibilities

Prerequisites 

  • Anyone interested in understanding what AGILE is and how the AGILE methodology can be used in software projects.
  • AGILE is technology independent - You don’t need a technical background to learn how to practice AGILE in business projects.
  • This is a beginner level course, so no previous experience of AGILE is required.

 

Transcript

So let's quickly walk through some of the AGILE project techniques. So first: frequent inspection of the product and adaptation to the changes and input during the project. Second: aligning development with customer needs and company goals. Third: co-location of resources to be in the same workspace so it's easy to talk. Four: self-organized and accountable teams. Five: getting rid of waste and ceremony and things that don't really add any value in meetings, for example. Six: having that empirical demonstration of results. Seven: make sure the customer is always present if possible. And eight: product managers and owners. So, frequent inspection of the product and adaptation to the changes and inputs during the project. Now this is a core difference between AGILE projects and non-AGILE projects. With AGILE, we are encouraged to test and adjust. To fail fast, and adjust quickly. Aligning development with customer needs and company goals. So the role of the product owner provides the missing bridge that I've found between the user and the developer. Having a product owner who is in constant contact with the customer or users, and who is aware of the overall goal of the business, is more effective than the requirements documents that we used in the past. So the product owner is the voice of the customer. Being self-organized and accountable. Now, it's a key technique in empowering team members to self-organize resources to match the roles required. A regular demonstration of results. And that's a core part of code over documentation. Remember that key difference between code... ...over documentation, one of the pillars of AGILE. And we're focusing on key planning events. So product planning, release feature planning, iteration planning, SPRINT review, and stand-ups.

About the Author

Students63266
Courses91
Learning paths40

Andrew is an AWS certified professional who is passionate about helping others learn how to use and gain benefit from AWS technologies. Andrew has worked for AWS and for AWS technology partners Ooyala and Adobe.  His favorite Amazon leadership principle is "Customer Obsession" as everything AWS starts with the customer. Passions around work are cycling and surfing, and having a laugh about the lessons learnt trying to launch two daughters and a few start ups.