We have built an effective Quality Advocacy program that results in fewer defects in the software we create. Do we use better tools and techniques than others? No. We have made quality the responsibility of every person on the team.
Integrating QA into an agile team does not have to be painful. It can be achieved using the Extreme Programming principles of communication, simplicity, feedback, and courage. This experience paper describes our journey to successful integration.
A 48,000+ hour software development effort led by a series of eight different project managers? Yes. Each brought unique strengths, capabilities and working style, but effectively engaged the team and sponsor by using a simple, consistent process.
Brooks' Law states: "Adding manpower to a late software project makes it later." See how we have overcome the constraint of Brooks' Law in the Menlo Software Factory™ and accomplish more when we increase the size of our teams.
Project planning at Menlo is a repetitive cycle of "plan, execute and measure", rather than a single event at the beginning of the project. See how we have applied Extreme Programming practices to professional project management.
How much effort is required for this new project? This critical question is alway asked when we know the least: at the beginning of the project. What approaches and tools are needed to be able to answer this question effectively?
The IT industry has suffered famous and costly failures over the years. It is time for a different team model for software development and delivery. What does that new model look like and how do we put it together?
When teams embrace Extreme Programming there is opportunity for a broad set of meaningful project management practices to become accessible to team members, while also making clear, unambiguous information available to the project managers.
We have experienced that the concept of "paired programming" has worked well. The benefits are significant; far outweighing the "cost" of having two programmers work on the same code. You still have questions. Here are our answers and experiences.
Management can often be frustrated by the inability of software development teams to respond quickly to changes in requirements. This paper recounts one organization's transformation to a high performance team using the practices of Extreme Programming.
Does pair programming in an open and collaborative work room have implications for hiring? You bet it does. This paper describes the unique interviewing and hiring process that has been in place at Menlo Innnovations since the beginning.