InfoQ Homepage Agile Content on InfoQ
-
What Do You Look For In a Servant Leader?
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.
-
El-Habya'a” or The Technical Debt
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. Technical debt also deserves a special attention in Agile projects. This article suggests that technical debt is a risk and it can be managed using standard risk management process and presents an outline of this process in the context of Agile projects.
-
Open Agile Adoption in Theory
In this 3rd article in the series about Open Agile Adoption Dan Mezick presents the theoretical background to the approach and explains why the techniques described in the other articles work to help achieve sustainable agile transitions.
-
DevOps - Pivoting Beyond Pockets
Traditional Infrastructure Operations roles are no longer scaleable. The traditional system admin or the network engineer or the engineering roles such as storage engineers are rapidly changing. The difference between a developer and operations engineer are becoming more and more invisible and will eventually dissolve. This is part of a massive shift in the IT Infrastructure Industry.
-
ATDD From the Trenches
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.
-
Discover to Deliver: Author Q&A
Ellen Gottesdiener and Mary Gorman have written a book titled Discover to Deliver: Agile Product Planning and Analysis. The book addresses the planning and analysis activities needed in implementing business products, with a focus on software products and business process change initiatives.
-
Interview with Tiago Garcez about Why Agile?
“Would you recommend Agile in every situation?” The answer from Tiago Garcez on this question is “Yes!”. But sometimes people are unsure what agile means and what an organization can do to become agile? Tiago talked at Agile Tour Brussels 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.
-
Modeling in the Agile Age: What to Keep Next to Code to Scale Agile Teams
Now that Agile methods have become mainstream in software development, working code is considered the most important team artifact. There is still a need for modeling. Kenji Hiranabe explores the spaces where modeling fits and plays an important role in this Agile age. With focus on development scaling to multiple teams where a shared understanding of the system’s “Big Picture” becomes essential.
-
Open Agile Adoption: The Executive Summary
Agile adoption is struggling - organisations mandate agile practices expecting teams to change their way of working but the changes don't seem to be sustainable. This is the second in a series of articles which examine why this is happening and suggest an alternate approach - Open Agile adoption based on invitation and engagement rather than mandate and instruction from above
-
Codenvy’s Architecture, Part 2
Tyler Jewell, CEO of Codenvy, unveils in this 2-parts article the architecture of Codenvy - a cloud IDE –, providing details on its platform and plug-in architecture, workspace and cluster management, multi-tenancy implementation, IDE collaboration, release model and SCRUM process used for development.
-
Creating a Culture of Learning and Innovation
Jeff introduces some of the steps the employees of a large engineering corporation took to begin building a culture of innovation by fostering continuous learning in the workplace. In an environment where engineering tended to wait for business direction and execute to that direction, they are now seeing engineering selling the business on new directions to explore.
-
Much Ado About Commitment
Great projects are generally the end result of commitment from three basic sets of actors: individual team members, teams and projects. With agile teams committing based on the needs of the business and their capabilities, and delivering against the commitment they make.