Scrum common wisdom says a Scrum delivery team needs a dedicated Scrum Master (SM). For new teams, this make sense. But as teams mature, do they still need a dedicated SM? Can an SM have multiple teams? Can the team assume the role within themselves? This article proposes that for mature teams, a dedicated SM is no longer needed.
Agile and the Project Management Office (PMO) are no longer considered diametrically opposed phenomena. With an ever-changing business landscape, organizations are required to adopt more nimble approaches. In many cases, Agile is more suitable within the PMO than people think.
In this article, let’s discuss the kind of qualities, preferences, and non-technical skills you might need in a servant leader, your potential Scrum Master, agile project manager, potential account manager, or whatever role you need filled.
Technical Debt is not always a bad thing but it needs to be carefully managed especially as it increases with time at a geometric rate. This is an approach to managing technical debt on Agile projects 1
This is the 3rd article in a series about Open Agile Adoption, looking at an opt-in approach to achieve sustainable organisational transformation.
Today organizations that are on a Devops journey often end up implementing in pockets that are not scaleable. This article addresses some of the challenges and suggests ideas to overcome them. 2
A concrete example of how to get started with acceptance-test driven development on an existing code base. It is part of the solution to technical debt. 5
Learning Gerrit Code Review presents an overview of the Gerrit review tool, from how to install and configure projects through to how to integrate with other services like GitHub and Jenkins.
Ellen Gottesdiener and Mary Gorman have written a book titled Discover to Deliver: Agile Product Planning and Analysis. They recently spoke to InfoQ about the ideas behind the book.
Interview with Tiago Garcez about why agile is better suited to the challenges that companies are facing, the value that agile can deliver, and how you can start an agile transition.
This is the second in a series of articles which examine a new approach to organizational change: Open Agile adoption based on invitation and engagement rather than mandate and instruction from above
Tyler Jewell, CEO of Codenvy, unveils in this 2-parts article the architecture of Codenvy, providing details on its platform, plug-in architecture, workspace and cluster management, and many others.