The principles of AGILE

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 Agile is a different way of working. Agile is more about talking than writing. Agile is about small steps done often over a long project plan. Agile encourages change. And Agile empowers people to act autonomously. Let's just clarify what Agile isn't to help us understand what it is. Agile is not anti-process or anti-management. But it could be easy to see how people might view it in this way. From the outside it can perhaps appear unstructured or maybe even chaotic. Where is the critical path? How do you quantify and stay within a budget if you worked only to fortnightly sprints? Now these are all reasonable assumptions and issues to make. If we come directly from a Waterfall Project Management perspective. So let's deconstruct these assumptions a little bit to help us. Agile is not a threat to project management or project leadership. The roles in an Agile project are different than a Waterfall project. And so is how we approach prioritization and how we define the path of a project. However the notion of ownership, risk and accountability are still inherent to Agile projects. Just as they are key aspects of a non-Agile project. So to begin thinking in an Agile way we first need to start thinking differently. First we need to be user centric. We need to encourage a business approach that aligns development with customer needs and company goals. We need to encourage frequent inspection and adaptation. So we need to encourage and welcome reviews. Welcome feedback and ultimately encourage change. Quite a different way of thinking. We need to adopt a leadership philosophy that encourages teamwork, self-organization and accountability. So we need to trust people to do a good job without them needing to be managed, micromanaged via a project manager or a project management timeline. Last of all we need to remember to communicate best practices so that we can allow and create an environment for rapid-develop delivery of high quality projects. And that's an important aspect to a successful Agile project. So Agile is a way of working based on a series of principles. The concept of principles can sound a bit scary, right? But don't worry. They are more about guiding principles than rules that you have to follow. It's very unlikely that someone on a project is going to ask you to name the 12 principles of Agile but they might however expect you to understand the roles and responsibilities of the product owner, the scrum master and expect you to know what is required from the product backlog or from a stand up meeting. So keep engaged as we learn more about these constructs.

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.