How to Build Awesome Agile Teams with Scrum/Kanban/Extreme

Many teams start out by thinking of Agile like any new tool set, almost like they're training on how to play a new sport. First, you learn the equipment, then you learn how to swing, then you learn how to catch, and then, finally, the team is playing well together. But, if you see Agile as simply a new set of tools, then you're unlikely to have any real productivity gains.

In this section we go over how to get your organization on board by not starting to promise immediate results. That type of expectation is almost sure to fizzle. Instead, start by listing the challenges you have with your current projects.

There are many different ways to start promoting Agile within your organization. Often, you'll want to convince several groups of stakeholders. The two groups of Stakeholders you'll usually have are the Executive sponsors and Development managers. When you're starting Agile in your organization, these groups are interested in very different things.

In the section we are to review what the agile roles are.

In this section we will review the role of the scrum masters role

The product manager is the voice of the user in the scrum team. In this section we will review how they do this.

project management has several structural challenges that will make it difficult for many project managers to see their path to Agile. In this section we will see how to mitigate these challenges.

Self organization is the key to every teams success. In this section we will review how you can accomplish this. 

While we recognize that there are allot of creative, non-repetitive, variable work in agile development projects, many work items, ceremonies, and activities can benefit from systematic, reproducible and standardized tasks test and options that can be captured in customizable checklists prepared and used by empowered agile teams.