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 10 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.
This Course will suit anyone interested in learning what AGILE is and how AGILE techniques are used in development projects.
- 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
- 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
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.
Andrew is fanatical about helping business teams gain the maximum ROI possible from adopting, using, and optimizing Public Cloud Services. Having built 70+ Cloud Academy courses, Andrew has helped over 50,000 students master cloud computing by sharing the skills and experiences he gained during 20+ years leading digital teams in code and consulting. Before joining Cloud Academy, Andrew worked for AWS and for AWS technology partners Ooyala and Adobe.