MikeBD Musings of a 24/6 techie (Software Architect / Technical Manager) family guy struggling to find meaning, balance and strong design / implementation supporting excellent user experiences.

7Aug/080

Agile Software Development: an Answer to Procrastination?

A recent LinkedIn question on Software Estimation and Agile Methology included a concern that Agile could lead to Procrastination. I believe otherwise as detailed below. What has your experience been?

Software Estimation and Agile Methodology

I am new to Agile Methodology. I am working on a project which is following Agile. I have the following questions:

  1. What are the estimation techniques for Agile?
  2. Typically which type of Projects use Agile?
  3. In the name of Agile, can people procrastinate every single decision during requirements gathering? For example, we know what is expected but we don't know the most atomic level of the requirement. Say, I know I must build a webpage, but I don't know the validation of the webpage.

My Response:

I think Agile principles can be an antidote against procrastination. I would agree with the thoughts expressed in this post. If you continually drive to keep the design and implementation as simple as possible and don't get overly concerned with anticipating potential future needs, there is nothing left to do but build what you know is needed now. Continue reading...

  • Digg
  • del.icio.us
  • Facebook
  • Twitter
  • Technorati
  • email
  • Print
  • PDF
  • StumbleUpon
  • Yahoo! Buzz
  • Google Bookmarks
  • DotNetKicks
  • FriendFeed
  • Google Buzz
  • Live
  • Netvibes
  • Slashdot
  • Add to favorites
28Feb/080

QA Estimation: Testing hours as a function of development hours

The following question on LinkedIn caught my eye as something that is often assumed in project management and estimation efforts.

Testing hours as function of development hours.

Does it make sense to say that number of testing hours in a project should be a function of the number of development hours, such as
TestingHours = X% * DevHours? If so, what should X% be. What considerations would make it be lower or higher. Are there industry standards around this?

My Response:

In a word - no.

There are just too many variables at play of which some will include: Continue reading...

  • Digg
  • del.icio.us
  • Facebook
  • Twitter
  • Technorati
  • email
  • Print
  • PDF
  • StumbleUpon
  • Yahoo! Buzz
  • Google Bookmarks
  • DotNetKicks
  • FriendFeed
  • Google Buzz
  • Live
  • Netvibes
  • Slashdot
  • Add to favorites