In a wide-ranging interview, LMAX's Trisha Gee talks to Charles Humble about using Java for low latency programming, and the Disruptor, an open source concurrent programming framework developed by LMAX. She also discusses the agile management techniques used at LMAX, and issues around gender and ethnic diversity in IT.
Forrester have recently released the results of their November 2011 Global Agile Software Application Development Online Survey in a report entitled "Survey Results: How Agile Is Your Organization?" It contains a number of interesting findings around how organisations that have adopted Agile are dealing with their implementation.
Story points are about estimating relative effort, gauging how difficult it will be to complete one feature relative to another. They are an abstraction of the cost, effort, and labor needed to produce that feature. Simple enough concept right? Wrong. Some teams are using story points to rank features rather than estimate effort. Hard to believe? Read on.
What's happened with scrum extensions since our 4th quarter 2011 update? We asked Alex Armstrong, VP Business Development and Director of Programs at Scrum.org. This article summarizes our interview and discussion with Alex and gives the latest proposed scrum extensions.
In projects that are implementing Scrum, the role of the Scrum Master is very crucial as he is a team facilitator. This article focuses on what is Servant Leadership, origins of servant leadership, how to transfer leadership to teams, the role of the Scrum Master as a Servant Leader and it expounds on the principal characteristics and traits of a Servant Leader.
In the second of two articles Claudio Kerber talks about his experiences in team formation and collaboration and explains the process whereby he "became unnecessary" as the team he was working with built trust and cohesion through trust, shared knowledge and shared experiences. He examines the theoretical underpinnings and discusses ways in which servant leadership emerges.
In the first of two articles Claudio Kerber talks about his experiences in team formation and collaboration and how empowerment, refinement and facilitation enable the free flow of knowledge and value across team members and how cohesion emerges in collaborative teams.
Simon Brown discusses the role of the software architect, challenging some of the current assumptions and trying to redefine it in the context of Agile development.
Rafael Maranzato tells the story of a team who initially failed to adopt Scrum, but they tried again, successfully adopting it and moving to Scrum of Scrums within one year.
Alan Shalloway discusses the challenges associated with transitioning companies to Lean and Agile methods on an enterprise scale. The interview discusses how Lean and Kanban can be used to encourage encourage incremental change and ongoing improvement, the cultural factors that can hamper Agile adoption, and why practices that benefit teams can actually harm the organization as a whole.
In this interview, Jesper Boeg, author of the new InfoQ book – Priming Kanban, discusses the keys to using Kanban effectively, and how to get started if you are currently using other approaches. Jesper also discusses the benefits of integrating elements of Kanaban into existing Scrum teams and what can be achieved from the team seeing the entire value chain and owning the whole process.
Scrum, arguably the fastest-growing Agile methodology, is well described in the original Scrum books, which tend to be read once and put aside. Scrum is a framework with simple rules. This Scrum Checklist will help you to remember these simple rules in the heat of daily work and stress. It enable you to create an enjoyable and productive work environment with your Scrum-Team.
Scrum and Kanban are two flavours of Agile software development. So how do they relate to each other? Part I illustrates the similarities and differences between Kanban and Scrum, comparing for understanding, not for judgement.Part II is a case study illustrating how a Scrum-based development organization implemented Kanban in their operations and support teams.
For those getting started with Agile, this book offers a detailed first-person account of how one Swedish company implemented Scrum and XP with a distributed team of 40 people, and how they continuously improved their process over a year’s time.
