10/3/2012 by Elinor Slomba
Couldn't make it to Scrum Gathering Barcelona 2012? Read about what CSM Elinor Buxton Slomba has to say about attending our sold-out event.
9/21/2012 by Brent Reid
Traditionally, most systems used to track defects and work items on a development or maintenance program include the concept of priority. James O. Coplien addresses the topic of priority in his 2011 article "It's Ordered — Not Prioritized!"I agree with Mr. Coplien that the product backlog should be ordered, not prioritized — and here I present slightly different reasoning to support the same conclusion.
9/18/2012 by Victor Szalvay
Technical debt describes the cumulative consequences of cutting corners in software development, but it escapes the attention of many project managers as they focus on scope and schedule. That’s a mistake because it impacts both. Here are questions to help you ascertain the real state of technical affairs.
9/13/2012 by Paul I. Pazderski
Transitioning toward Scrum practices isn't easy for every team. I've used a visual image that I call the Scrum team scorecard to help. It's a one-page "snapshot" of the level of transformation of a project team into a Scrum team. An independent o...
9/13/2012 by Michele Sliger
There’s going to be a lot more talk about Agile now that the Project Management Institute has introduced a new certification program for Agile Project Practitioners. Let’s clear up some initial confusion and look at what Agile is and is not, and why you should care.
9/11/2012 by Skip Angel
Organizations and teams must come to understand why they need agile before choosing a methodology or tool to implement it. A mandate alone will not work. It is the overarching goals, values and principles of Agile that must ultimately guide teams in the adoption and adaptation of its practices.
9/10/2012 by Rahul Jain
In the software industry, professionals hold different views on processes. Some say processes are bureaucratic and rigid, making their lives difficult. "Why in the world does a simple software installation have to go through X number of approvals when I have such an urgent task at hand?" Others (mostly members of organizational process groups) relentlessly endorse standardized processes and talk about how the organization could be benefited by the data collected from following those processes. Project teams, though, are often unconvinced, since what the data says and what the customer says can differ.
9/7/2012 by Brian Barr
Projects, projects, projects! You know you don't like them, but do you know why? Is there a better approach? In this article, I'll outline why we've chosen to be project oriented in the past and why pulling "the Big Lever" toward release orientation is so important in making the move toward Agile solution delivery a real success.
9/5/2012 by Mukesh Chaudhary
Scrum and other Agile methodologies rely heavily on a set team structure to succeed. In Scrum, you have a team, a ScrumMaster, and a product owner. These teams work on features that are iteratively developed. As explained by Mike Cohn, the teams are commonly called "feature teams." However, quite frequently...
9/3/2012 by Mathai Boben
When I set out to practice and preach Agile methods, the world looked rosy to me. A team built on qualities that are human made much more sense than a team kept together by command and control. A team where everybody valued each other's individuality and uniqueness yet functioned toward one goal in an orderly manner seemed possible.But at the runway, I realized I didn't have any wings. Why? Because stakeholders were yet to come out of the comfort zone of spreadsheets, where command and control made a lot of sense.