Agile, Scrum, Kanban, Extreme Programming (XP), etc.

Extreme Programming (XP) is a radical new approach to software development that has been accepted quickly because its core practices--the need for constant testing, programming in pairs, inviting customer input, and the communal ownership of code--resonate with developers everywhere. Although many developers feel that XP is rooted in commonsense, its vastly different approach can bring challenges, frustrations, and constant demands on your patience.

We all recognise that world is inherently complex but what does this mean? From a theory perspective it means that it is an open system where the agents and the environment coevolve and influence each other. This means that traditional approaches that assume that we can analysis a system and understand what is happening and what we should do no longer hold. We continue to cling to old practices but if we accept that the world is complex how can we make sense of the world?

Scrum and Kanban are two flavours of Agile software development - two deceptively simple but surprisingly powerful approaches to software development. So how do they relate to each other?

This free book contains practical guidance for anyone considering or applying agile development for building valuable software. Plenty of books describe what agile development is or why it helps software projects succeed, but very few combine information for developers, managers, testers, and customers into a single package that they can apply directly.

Learning new development processes can be difficult, but switching to Agile doesn't need to be complicated. Explore the theories behind Agile and learn how to make it work for you. In Agile Software Development Succinctly, author Stephen Haunts will guide you to a fuller understanding of Agile, its advantages and disadvantages, and how to get the most out of it.

This book is a comprehensive, pragmatic tutorial on Agile Development and eXtreme programming, written by a software developer for software developers.

Different teams may be working on different products in a product portfolio or together on one product. The more distributed the teams, the stronger the need for strong governance. Underlying the products is architecture. Roles like product owner, portfolio manager, and ScrumMaster are assigned based on a delicate balance of skill, knowledge, and location. Organizations need to decide where to form what roles in order to achieve company goals.

You need more than great dev tools to release great software; you need an efficient pipeline that takes advantage of modern Agile development practices. Serverless platforms like AWS offer the basic building blocks you need to run code, store data, or process streaming information so you can focus on the features you want to provide, not get bogged down with the infrastructure.

Why do some companies excel with agile and others see virtually no improvement? The difference is culture and an understanding that agile is a framework for deep cultural change instead of a process or set of practices to increase efficiency. Why Agile Works: The Values Behind the Results focuses on why and how agile works and where agile should take organizations in terms of values.