Skip to main content

Posts

Showing posts from September, 2010

Core Agile Values

I have always felt that agile is really about values: Openness, Honesty, Courage, and Trust. Personally Whenever I remained true to these values things went OK. In those (rare) cases when I have given into temptation, danger was lurking.

This cartoon illustrates a classic case. Three levels of management get three different answers about the state of the project. As the report moves up the management chain, its status changes from Red to Yellow to Green. Sound familiar?

Why does this happen? A project leader colleague of mine was literally afraid of losing his job if he told his managers the truth about his project. So he didn't. Until one day, the truth could not be hidden any longer. Unfortunately, this was three days before a release party (which had to be canceled). Bad thing.

Did the impact of the truth get smaller as time went on? No. Did it become easier to deal with the problem as time went on? No. So why do people hide the truth? I think lack of trust (and the fear it …

Scrum Breakfast/October: Enhancing agile development with software assessment

An agile process replaces upfront design with the focus on the ability to react and to decide based on the current situation. But, to take the right decision we need to be able to assess the situation accurately and fast. However, software systems are large and complex and they handle large amounts of data. Thus, they present many more details than we can reliably control. Approaching the problem in an ad-hoc manner does not benefit us.

Assessment is a critical activity to ensure proper decisions involving large amounts of details. And it is expensive, too, with various studies reporting assessment to account for as much as 50% of the total development effort. As such, it should be addressed explicitly in the development process.

In this talk, Tudor Girba will provide an overview on the problem of assessment and illustrate how the current popular approaches fail to solve it because they are either ad-hoc or too generic. He then describes agile assessment, a new approach t…