Agile Process Definition

Recently I have been challenged by coming into a new startup which is still finding it’s way with agile and just work item management.  Over the years, I have managed and lead many different teams and below is the outline that I have found to work in my experiences.  That being said though, remember that agile is also about being nimble and fulling adopting the phrase inspect and adapt. Continue reading


Agile planning poker with remote teams

Anyone that has been working in agile software development has undoubtedly used some form or planning poker.  A common standard is to have sizing meetings with the team, and in these meetings the team comes together and measures the complexity of a unit of work commonly referred to as a user story.

During these meetings, the team will commonly use what is referred to as the Fibonacci sequence to rate the complexity of the unit of work to be done.  Some people will by default try to tie this back into hours to complete the story.  Please understand that this is not the purpose of this exercise.  The team should rate each story for the level of complexity to complete.  Some people will even discuss and agree on a comparison sheet in that they will look back at completed work items and say an example of a “3” would be a particular user story, an example of a “5” would be this, and so forth for each of the ratings. Continue reading

To be agile

Some time ago I found myself interviewing developers for a position that we had and quickly found that being “agile” for many either means that they are doing iterative waterfall development or that they are just simply not doing waterfall so by default it must be agile.

What I found is that while people have varying opinions on agile and even more varying practices, I found that there are a few key pieces that most often got skipped. Continue reading