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.
Agile
Posted on:
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.
Administrivia
Posted on:
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 […]
Product Management / Requirements / Software development
Posted on:
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?
Product Management
Posted on:
Successful Product Managers – Seven Traits
Michael Shrivathsan just posted an excellent article on his experiences of the seven traits of successful product managers. Absolutely awesome article. Thanks Michael!
Flashback
Posted on:
Flashback: A Year Ago This Week on Tyner Blain [2005-12-16]
A look back at the best from a year ago.
Product Management
Posted on:
Product Manager Salary Survey – More 2006 Results
Trying to unearth more trends in the 2006 salary data from the Pragmatic Marketing annual product management and marketing survey. In this article, we look at total compensation relative to the revenue of the managed products, the company size, and the company age. More fun with numbers.
Interaction design / UX
Posted on:
Overdoing Personas
Its easy for us to overdo almost anything. Kim Goodwin offers some good advice about how not to overdo it when using personas as part of our software development process.
Interaction design / Requirements / Requirements Models / Use Cases
Posted on:
Actor Hierarchies And Then Some
Actor Hierarchies give us an overview of the people who will interact with the system. We can extend this model to provide a visual indication of how use cases are distributed through the organization. Further, we can leverage a hierarchy to show how use cases are rolled out to the users – a targeted communication for our stakeholders.