The Trouble With Software (and what to do about it)

Leandro Faria on Scrum of Scrums: Running Agile on Large Projects

Posted in Agile Development,Extreme Programming,Programming by Ernie Schell on June 6, 2013

Want to use Agile practices on large projects? Does Agile only apply to small projects, or only to the simplest of projects?

By no means! — says Leandro Faria post on ScrumAlliance


The IT Revolution Press

I highly recommend The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Grow by Gene Kim, Kevin Behr, and George Spafford. This excellent business novel is a great read and realistic portrayal of the trials and tribulations of in-house software development and management in a large corporation. It is also “prescriptive,” suggesting a three-level approach to resolving issues that often cripple the IT process by isolating it from the rest of the business. Also see the related IT Revolution Website.

5 Common Mistakes Writing User Stories in Agile Development

Posted in Agile Development,General Overview by Ernie Schell on December 9, 2012

Krystian Kaczor writes on the Scrum Alliance Website: “Most of the issues with gathering requirements in agile software development and agile testing derive from issues with User Stories. Somehow expressing requirements in such a simple form causes a lot of trouble to agile teams.”

He further asserts that mistakes in User Story scenarios lead to wrong Test Cases, a poor understanding of requirements, and inappropriate implementation, which can be a “direct cause of rejecting the deliverables of the iteration.”

His five most common mistakes people make writing User Stories:

1. Not clearly identifying who “The User” is

2. Not understanding the Business Role of The User

3. Defining the Business Role incorrectly

4. Providing no Business Value or Benefit for The User

5. Defining no Acceptance Criteria or Conditions of Satisfaction for The User

As a perfect analog to these Role & Development ambiguities, there is also what I will call “Function Ambiguity.” For instance, how do you define “Customer Relationship Management?” Everyone probably has their own way of conceiving what it is, so how in the world are developers supposed to meet a generic set of needs and requirements, since, in Venn Diagram style, there is probably a small area of overlap among these different definitions. For a good example of this, see “Defining CRM: Thoughts from three experts” on the Marketing Sherpa blog.

Biggest Agile Challenge Is Communication

Posted in Agile Development by Ernie Schell on December 9, 2012

Application Development Trends notes that “A new survey indicates that while software development projects using the Agile methodology are doing OK, they could be doing better, with communication reported as the biggest impediment to success. The survey, conducted by Serena Software at the Agile 2012 Conference held in August, focused on the state of Agile projects underway at the time.”

Click here for more information

Agile graphic

Posted in Agile Development by Ernie Schell on March 20, 2012

Twitter post from Dan Tousignant
Twitter ID:@ScrumDan

A lot of people keep asking about a visual to compare Agile and traditional project management. Here is what I use.

Agile Success Factors

Posted in Agile Development by Ernie Schell on March 7, 2012

Scott W. Ambler writes in Dr. Dobb’s Journal that “at many sites, Agile approaches work at scale, although it’s harder for them to succeed at scale. Agile is no longer the province of small teams. Geographical distribution, however, correlates negatively with good results.”

See the entire article HERE.

Agile Development

Posted in Agile Development by Ernie Schell on August 31, 2011

Please add your comments, insights, issues, and gripes about Agile Development Solutions below.