Though Agile is one of the most successful methodologies for software development, it doesn't scale well for enterprise businesses. This course will teach you the methods, frameworks, and pipeline for Daikibo, a tool that will help you implement Agile at scale.
Agile brings many advantages to developers, among them a visible development process with a faster time-to-market and quick feedback loops that help raise quality. However, for enterprise businesses, Agile can be very complicated to scale properly. The answer? Daikibo: Agile at scale that works! In this course, Scaling Agile for Enterprise: Daikibo, you'll learn how to implement Agile at scale using this technology. First, you'll learn how to understand the methodologies and frameworks that make up Daikibo. Next, you'll learn how to create teams and groups that scale. Finally, you'll learn about the Daikibo pipeline and the user story life-cycle, going from concept to commitment to feedback to production. By the end of this course, you'll have a better understanding on how to scale an agile project for enterprise using Daikibo.
Xavier is very passionate about teaching, helping others understand search and Big Data. He is also an entrepreneur, project manager, technical author, trainer, and holds a few certifications with Cloudera, Microsoft, and the Scrum Alliance, along with being a Microsoft MVP.
Course Overview Hi. My name is Xavier Morera, and I am very passionate about teaching. I welcome you to this course, Daikibo Agile at Scale for Enterprise. Did you know that Agile is most commonly used by smallish development projects mostly executed in a single location? But because of Agile's success, it has worked its way into being adopted by enterprise, for example, Fortune 500 companies. The problem is that Agile does have its limits, and when many try to scale Agile, they fail. A big problem is that exploring how to properly scale Agile is a tricky scenario. You cannot try out new things at enterprise level without risking big projects, and big projects mean big money. No one likes to experiment while losing tons of money, but there is a company that explored the complexities of Agile at Scale, Cognizant, and they created Daikibo, a tried and true approach to implement Agile at Scale. Some of the major topics that we will cover are understanding the methodologies and frameworks that make up Daikibo, learning how to create teams and groups that scale, the Daikibo pipeline, the user story lifecycle at scale going from concept to commitment to feedback to production. By the end of this course, you will understand how to scale an Agile project using Daikibo. As a prerequisite, it's highly recommended to know about Agile, but I will also include a list of recommended courses within the Pluralsight library as a reference. I hope you'll join me on this journey to learn Daikibo, Agile at Scale, at Pluralsight.
Agile at Scale...Why? Hello. I am Xavier Morera. I am passionate about teaching, and I welcome you to this course on Daikibo, Agile at Scale for Enterprise. Agile has proven to be a great methodology used by an ever-growing number of projects helping increase the chances of success, so it's being adopted anywhere from startups and small projects to large projects at enterprise level. However, because of the dynamic nature and complexity of projects at a larger scale, many companies have hit a wall and learned the limits of traditional Agile. But there's still a need in enterprise for large scale projects to be delivered, so how can this need be catered for? Daikibo, which means large scale in Japanese, is the answer, and in this course I will teach you how to implement Agile at Scale. Let's start by mentioning how Agile is usually implemented. Since the beginning, Agile projects have focused on smallish development projects that are usually executed in the same location, and things were pretty good. Agile proved it works. I remember a few years ago how hard I had to push in some organizations to get buy-in from management on Agile, but times have changed, and people have learned to recognize its value, and as it's common in enterprise where the tendency is to be slower to adopt new methodologies and technologies, Agile worked its way to bigger projects in Fortune 500 companies. But then we run into a "little problem" as we have our Agile teams. But how do we scale? Should copy pasting teams work? Just create many of the same? Well, the answer is not quite. When it comes to adoption of Agile at Scale in enterprise, there are new complexities. It's not the same.
Getting People Involved: Teams and Groups Welcome to the next module of Daikibo training, Getting People Involved: Teams & Groups. At this point, we have covered the why, the when, and the how to organize Agile at Scale; however, we must now go one level deeper and understand how each one of the teams and groups that are involved in the process should work towards the goal of successful project delivery. I will start by explaining the difference between a team and a group. This is a key distinction, but it is common that some practitioners use the terms interchangeably, thus it is necessary to cover in detail and clarify. Once the distinction is clear, we will explain how each team and group is structured, as well as explaining in detail the interactions with other teams and groups. It is equally important to cover the distinction between scaled versus traditional teams and where within the project it looks like traditional Agile, namely Scrum. Why is it important that it feels like traditional Scrum? Well, you might be Agile at Scale on a huge, multi-hundred million dollar project, but you want your developers to feel as familiar as possible in his or her day-to-day work without the need for extensive retraining and learning. Let's use a simple analogy. Imagine you have a steering wheel. You could put this steering wheel in a sedan, SUV, sports car, or a luxury car. It would still be doing what it was created for, steer the wheels. It does not care about the type of car as long as it accomplishes its mission. It is the same for developers. From a developers point of view, the fact that a project is being scaled should not be an impediment for them to be productive as they would in a traditional Agile project. A developer must focus the majority of their energies in delivering working code, a potentially shippable product at a pretty fine cadence. And there is a very important detail that Daikibo places on teams, so let me tell you.
Raising the Bar: Governance and Best Practices Hello, and welcome to this module, Raising the Bar: Governance and Best Practices. In this module, we will be covering metrics, best practices, key learnings, and other important details when applying Daikibo. I will make this brief and get straight to the point focusing on what you need to take into consideration for a successful Agile at Scale implementation.