Managing an Agile Team

This week we’ll introduce the four fundamental jobs of software development to help you define what’s important to your team and, hence, which of the many agile practices might make the most sense for you to try out. Then we’ll talk about achieving alignment with your company while maintaining autonomy through an agile team charter. We’ll close by stepping through the leading agile methodologies--Scrum, XP, and kanban. You’ll finish the week with an understanding of how to pair what’s important to your team with the best of what agile has to offer.

One of the most critical focal points for any team is facilitating a focus on outcomes over output. Without this, you’ll never graduate from responding to requests about your to-do list of output to driving better user outcomes that move the needle for your company. This week, you’ll learn how to define and prioritize what’s important to your team in the areas of learning and deciding, and to pair those with relevant agile practices from Scrum, XP, and kanban.

This week we’ll dive into the jobs of building software and the core management jobs in running an agile team. Agile--and XP in particular--offers a rich body of work on specific coding practices. We’ll step through a few of the most prominent and discuss key linkages with the other concepts and practices you’ve learned. On the job of managing, we’ll dive deeper into what that means and what works in an agile context.