Learn Agile Basics from the ExpertS
|
This series of videos is created by Agile Alliance, a membership organizations that aims to support practitioners globally, and are part of their conferences between 2013 and 2018. They provide a great foundation for you to learn about the agile mindset a few years back and see how it evolved to date.
The videos are covering the following topics of Agile:
|
|
|
Introduction to Agile
|
What is this thing everyone calls Agile? If you have been doing software development a different way your whole career you may be wondering why should I change, what’s so different? In this introductory talk we will define why Agile is more than a process or methodology; it’s really a different approach to doing software development.
To provide some additional context we’ll also:
To provide some additional context we’ll also:
- Look back at how the Agile methods and practices emerged
- Discuss the Agile Manifesto and 12 Principles and their resulting impact on the way that we do software development today
- Describe what it’s like to work on Agile Project
- Describe what you can do next Monday to get started
|
Agile Development Practices Explained
Presenter:
Scott Densmore This presentation focuses on practices that correlate with Agile values, how to apply them, and why we use them. It examines those practices from the perspectives of both an individual engineer and an engineering manager.
|
Agile is all about values and not a set of prescriptive 1s and 0s, even for a development team. There are quite a few practices that align to those values and allow the development team to transition to agility in delivery of software.
This session focuses on practices that correlate to the values, how they apply and why we do them. It takes a view from both an individual engineer perspective as well as an engineering manager. It discusses how to apply these practices from an individual team to scaling across multiple teams. This is a journey where the destination is to continually adapt these practices Scott’s talk is based on experience in building software large scale software for the cloud and tooling for developers.
Download: Slides from the Talk
This session focuses on practices that correlate to the values, how they apply and why we do them. It takes a view from both an individual engineer perspective as well as an engineering manager. It discusses how to apply these practices from an individual team to scaling across multiple teams. This is a journey where the destination is to continually adapt these practices Scott’s talk is based on experience in building software large scale software for the cloud and tooling for developers.
Download: Slides from the Talk
|
Agile Teams: Self-Organizing, Collocated and Distributed
Presenter:
Jutta Eckstein Agile development requires teams to self-organize. However, this doesn’t happen by chance. Jutta Eckstein describes the essentials for building productive self-organizing teams for small and colocated teams as well for large, distributed settings.
|
Agile development requires teams to self-organize. However, this doesn’t happen by chance. Teams have to be set up in a way that allows them to self-organize. And moreover, if you work on a large project with more than one team the team structure should still enable self-organization. The same is true for global development.
This session covers the essentials for building productive self-organizing teams for small and collocated and as well for large and distributed settings.
Download: Slides from the Talk
This session covers the essentials for building productive self-organizing teams for small and collocated and as well for large and distributed settings.
Download: Slides from the Talk
|
Continuous Delivery ExplainedPresenter:
Rachel Laycock Introduces the foundational practices of Continuous Delivery. She delves into the details with practical suggestions about how you can get started. She also discusses the challenges and roadblocks you may encounter and tools you can leverage for success.
|
Jez Humble defines Continuous Delivery as, “The ability to get changes of all types—including new features, configuration changes, bug fixes and experiments—into production, or into the hands of users, safely and quickly in a sustainable way.”
As the first post-agile methodology, the goal of continuous delivery is to have all deployments be so routine that you can do them at any time with no impact to your customers. Sounds easy!
In fact, to do this, you need to automate and simplify all practices and process from requirements to deployment including, quality assurance and testing, continuous integration, configuration management, environments and deployment, data management, release management and organizational structure. In this session, we’ll introduce theses foundational practices of Continuous Delivery. We’ll delve into the details with practical suggestions on how you can get started and make progress in all foundational areas. Along the way, we’ll suggest some tools that could be used to assist your adoption. Lastly, we’ll discuss some of the challenges and roadblocks that you might encounter when you begin your Continuous Delivery journey.
Download: Slides from the Talk
As the first post-agile methodology, the goal of continuous delivery is to have all deployments be so routine that you can do them at any time with no impact to your customers. Sounds easy!
In fact, to do this, you need to automate and simplify all practices and process from requirements to deployment including, quality assurance and testing, continuous integration, configuration management, environments and deployment, data management, release management and organizational structure. In this session, we’ll introduce theses foundational practices of Continuous Delivery. We’ll delve into the details with practical suggestions on how you can get started and make progress in all foundational areas. Along the way, we’ll suggest some tools that could be used to assist your adoption. Lastly, we’ll discuss some of the challenges and roadblocks that you might encounter when you begin your Continuous Delivery journey.
Download: Slides from the Talk
|
Product Ownership ExplainedPresenter:
Richard Seroter Product ownership is one of the most important pieces of a software team. Watch as Richard Seroter takes a deep dive into what product ownership entails, including the job description, what makes a successful product owner, how to fail miserably (from personal experience!), and tips for creating the maximum impact in the role.
|
Is product owner just a role at software companies, or does every enterprise need them?
What does this person actually “own”?
How can you completely mess up the role and what does success look like?
Product ownership is one of the most important pieces of a software team. This talk takes a deep look at what product ownership entails including the job description, what makes a successful product owner, how to fail miserably (from personal experience!), and tips for creating the maximum impact in the role.
Download: Slides from the Talk
What does this person actually “own”?
How can you completely mess up the role and what does success look like?
Product ownership is one of the most important pieces of a software team. This talk takes a deep look at what product ownership entails including the job description, what makes a successful product owner, how to fail miserably (from personal experience!), and tips for creating the maximum impact in the role.
Download: Slides from the Talk
|
Agile Planning & Project Management
Presenter:
Mike Cohn In this session Mike Cohn shatters the myth that Agile teams can’t plan. He begins by examining the benefits of the short cycles of iterative and incremental development. Next, Mike looks at the six different levels of planning that occur in Agile organizations.
|
We’ll start by looking at the benefits of the short cycles of iterative and incremental development. We’ll then look at the six different levels of planning that occur in agile organizations. We’ll see what user stories are and why they’ve become the preferred approach to planning and managing the work of an agile team. We’ll look at how user stories are estimated with the popular Planning Poker technique. To do that we’ll discuss the merits of relative estimating and abstract approaches such as story points and what a point really means. With an initial plan created, we’ll look at how agile teams use the concept of velocity to measure and predict progress. We’ll also look at information radiatiors such as task boards and burndown charts. We’ll conclude by looking at how these concepts can be applied to complex situations such as fixed-date and fixed-scope projects.
