InfoQ Homepage Adopting Agile Content on InfoQ
-
/articles/manifesto-originators/en/smallimage/Leadership.jpg)
How Did the Originators of the Agile Manifesto Turn from Technology Leaders to Leaders of a Cultural Change?
Based on in-depth interviews with twelve of the seventeen originators of the Agile Manifesto, we describe how technology-driven forces led to the cultural change introduced by the agile approach. This message implies what human aspects and methods, practices and tools should be emphasized in adoption processes of agile software development.
-
/articles/cohn-chapter8/en/smallimage/cover.jpg)
Book Excerpt: Succeeding with Agile: Software Development Using Scrum
This is a book excerpt from Mike Cohn's new book "Succeeding with Agile: Software Development Using Scrum". This article describes the primary adjustments individuals must make as they transition from traditional roles to Scrum. The focus is on how these roles change, rather than on a thorough description of each role.
-
/articles/technical-challenges/en/smallimage/image.jpg)
Overcoming Technical Challenges for Adopting Agile Methods in the Enterprise
This article touches upon challenges to adopting agile methods within the enterprise and provided strategies for addressing them. Set up development environments in a consistent fashion using automated scripts and checklists, facilitate automated testing and continuous integration by using standard tooling and test data transparency, and ensure a stricter criteria for the done definition.
-
/articles/failed-agile-adoption-reasons/en/smallimage/AgileLenses.gif)
Why Agile Adoption Fails in Some Organizations
How often do you hear that a company attempting to adopt agile practices fails? This article examines and explains the often overlooked organizational reasons that agile fails, why it isn’t obvious, and some potential strategies for coping with organizational impediments. The article’s target audience is managers with budgetary responsibility although technical groups might also find interest.
-
/articles/building-an-agile-team/en/smallimage/team_building_ring.jpg)
Building an Agile Team
Building an agile software development team is not easy. Many managers and team leads hire technically capable people, throw some form of an agile process at the team, and hope that everything works as well as the literature says it does. This approach is not only unrealistic, but is prone to failure. This article will describe the components of a successful team and how we built this team.
-
/articles/making-scrum-stick/en/smallimage/image_scared-man.jpg)
Making Scrum Stick: Overcoming Anxiety And Fear
While a team can grab on to something as simple and effective as Scrum quickly, the associated changes can cause worries. There are common issues that occur when adopting Scrum as well as nuances that will almost inevitably crop up. By being aware of these issues you can be prepared for them or, perhaps, not feel too bad that you are experiencing them yourself – they are common.
-
/articles/coping-with-change/en/smallimage/lizzard.jpg)
Coping with Change on Scrum Projects
This article surveys the expected variation of different roles in the Agile organization and proposes techniques with which to better handle the transition to Agile methodologies from traditional Waterfall. The following roles are discussed in this article: Customers/Stakeholders, Product Management, General Management, Project Management, Developers and Quality Assurance.
-
/articles/agile-testing-book-excerpt/en/smallimage/AgileTesting.jpg)
Book Excerpt: Agile Testing
This book is for testers on an agile team, test and quality assurance managers transitioning to agile development, and agile teams learning how to approach testing. The book introduces agile testing, how it's different from testing on a traditional team, and what makes agile testers different. The book contains dozens of stories about the various testing-related issues faced and resolved.
-
/articles/adopting-pair-programming/en/smallimage/pair-on.png)
Successfully Adopting Pair Programming
Jay Fields takes a look at pair programming from an adoption perspective. This article is for you if you already know what pair programming is and guidance on how to get to the point of successfully practicing pair programming. Jay goes over everything from an optimal seating arrangement, to effective coaching techniques, to calling out common mistakes to avoid.
-
/articles/dutch-railway-scrum/en/smallimage/DutchTrain2.jpg)
Case study: Distributed Scrum Project for Dutch Railways
How we customise Scrum to our local context plays a large role in the success or failure of a project. This article describes a successful, large, distributed Scrum project, which had already been scrapped once under a traditional approach. The authors share lessons learned on: project startup, product ownership, testing and the importance of estimates and effective communication.
-
/articles/Agile-adoption-study-china/en/smallimage/scrum.gif)
Improvement, Success and Failure: Scrum Adoption in China
This recent inquiry, by InfoQ China editor Jacky Li, picked 5 very different cases of Scrum adoption in China, which got different results, and asked: Why did you use Scrum? How did you adopt it? What problems did you encounter, and why did it succeed or fail? Despite the small sample size, it's an interesting comparison, pointing out that improvement doesn't ensure success.
-
/articles/hiranabe-lean-agile-kanban/en/smallimage/Fig5_task-board_tiny.jpg)
Kanban Applied to Software Development: from Agile to Lean
In this InfoQ article Kenji Hiranabe applies lessons learned while working with Japanese manufacturers. While many Agile teams are optimizing only a portion of the value stream, Hiranabe proposes a simple way to adapt lessons from Lean Manufacturing's "Kanban" visual tracking system to make process visible to more of the organization, for better communication and process improvement.