InfoQ Homepage Agile Content on InfoQ
-
Q&A with Johanna Rothman and Jutta Eckstein on Cost of Delay
The book Diving For Hidden Treasures - Uncovering the Cost of Delay in Your Project Portfolio by Johanna Rothman and Jutta Eckstein explores how projects become delayed and provides tools and methods to analyze and limit the costs of delay in projects.
-
An Organization Development(OD) Approach to Agile Adoption
Is there an approach that can make Agile adoption successful at a systemic level, and not remain just an engineering practice? Organization Development (OD) is an interdisciplinary field of research, theory and practices. It has the right methods for organizations to become organic entities, to implement learning systems, empower teams to become self-organized and reduce resistance to change.
-
Pair Programming Is No Panacea
Is pair programming all that it's cracked up to be? Contrary to popular belief, pairing can lead to a decrease in creativity, groupthink, inappropriate feedback, and can be demoralizing. Wes Higbee explores why it definitely shouldn't be mandated, and why you should consider other options where it could be beneficial.
-
User Stories Are Placeholders for Requirements
It can be difficult to change from a Waterfall approach where ‘business analysts write big requirements up front’ to the Agile practice in which requirements are prepared ‘just in time’, and are the responsibility of the entire team. The secret to success in Agile is ruthless management of scope.
-
Using SEMAT and Essence at Fujitsu UK
Fujitsu UK is using a large number of processes and methods which have developed over the period of many years. Looking for a way of combining agile and traditional methods, they became aware of SEMAT and the Essence Kernel. This article explores how they applied SEMAT and Essence to systems engineering, and used it to look at the whole programme of work across all disciplines.
-
Inner Source—Adopting Open Source Development Practices in Organizations
Although inner source offers numerous benefits, many practitioners are unclear about what it is and how to adopt it. When adopting inner source, organizations should consider nine factors pertaining to product, process, and organization.
-
Exercises for Building Better Teams
Have you ever seen a team perform so great that you wanted to join it? If you examine the values of such a team, you may discover a perfect balance of orientation on people and results. If you are trying to discover how far away your own team is from this state, read this article and try the exercises to find your own state of perfection.
-
InfoQ at 10
We know that software is changing the world, and we’ve come to see our impact as accelerating the software side of that change. With that passion, we started InfoQ 10 years ago, in the context of some unusual beliefs and concerns.
-
A Reference Architecture for the Internet of Things (Part 2)
This is the second article of a two article series in which we try to work from the abstract level of IoT reference architectures towards the concrete architecture and implementation for selected use cases. This second article will show how to apply this architecture to real world use cases - one being in the field of smart homes, one in the field of insurance.
-
Building a Team with Complementary Testing Skills
Imagine meeting with a group to implement a high-level test strategy, then coming back in six months and finding there has been little progress because the director-level executives have been trying to staff projects. I wish I could tell you this was uncommon. Today we'll talk about how the delivery team can acquire all the skills it needs to release software when the number of testers are low.
-
DevOps Lessons Learned at Microsoft Engineering
Thiago Almeida from Microsoft shares how adopting DevOps practices resulted in better engineering and happier teams, and the lessons learned in that journey.
-
The Volcano - Prioritize Work for Multiple Teams & Products
It is always a challenge to pick the correct priorities. Which one of work item A, B or C shall you do first, and why? Tomas Rybing presents the Volcano, a tool to visualize and prioritize work for multiple teams working with several products.