After doing the ‘prep work’ for the project, you are ready to begin. When “the boss†asks for a project plan, tell him to wait 6 weeks.
Going Agile, 10 Mistakes: Fail To Define Roles
We have to define the roles and responsibilities of each person within the team. This helps both with execution and communication (to people outside the team).
Going Agile, 10 Mistakes: Fail to Identify The Sponsor
If we don’t identify the champion of the endeavor to convert to agile processes, we can’t keep them informed of progress. Their expectations need to continually adapt to progress just like every element of agile.
Flashback: A Year Ago This Week on Tyner Blain [2005-12-23]
A look back at the best from a year ago.
Going Agile, 10 Mistakes: Ignore the Corporate Culture
Many companies operate with each department acting as a silo. Agile techniques rely upon cross-functional contributions. When there are barriers (“not my jobâ€, “not your jobâ€) within an organization, they have to be addressed before agile will work.
Going Agile, 10 Mistakes: Go Fast To Go Fast
In this mistake, Levent warns us that “just doing it†without training and explaining won’t work. Everyone needs to understand exactly what agile is and what it isn’t.
Going Agile, 10 Mistakes: Go All In
Levent points out that the biggest mistake is to not do a pilot project, but rather to convert a large and risky project – or even worse, all projects. He points out that it is a mistake because you won’t have time to learn from mistakes.
Holiday Semi-Vacation
I’m taking a vacation thru the end of the year. Hooray! We’ve already written a series of short articles about migrating a development team to an agile process. Those articles will appear over the next several days – we hope you enjoy them. When I can get online, I will […]
To Buy, or Not To Buy. To Build? is the Question
Should we buy this application, or build it in house? How should we make that decision today?