Skip to content
Tyner Blain logo

Tyner Blain

Software product success.

  • Main
  • Profile
  • Tyner Blain
  • Subscribe
  • Book Info
Agile

Going Agile, 10 Mistakes: Fail To Define Roles

Posted on: December 26, 2006November 19, 2006

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).

Agile

Going Agile, 10 Mistakes: Fail to Identify The Sponsor

Posted on: December 25, 2006November 19, 2006

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.

Agile

Going Agile, 10 Mistakes: Ignore the Corporate Culture

Posted on: December 22, 2006November 19, 2006

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.

Agile

Going Agile, 10 Mistakes: Go Fast To Go Fast

Posted on: December 21, 2006November 19, 2006

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

Going Agile, 10 Mistakes: Go All In

Posted on: December 20, 2006November 19, 2006

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.

Product Management / Requirements / Software development

To Buy, or Not To Buy. To Build? is the Question

Posted on: December 19, 2006

Should we buy this application, or build it in house? How should we make that decision today?

Interaction design / UX

Overdoing Personas

Posted on: December 14, 2006December 14, 2006

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

Actor Hierarchies And Then Some

Posted on: December 13, 2006

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.

Agile / Requirements Models / Use Cases

Incremental Delivery and Evolving Use Cases

Posted on: December 12, 2006February 3, 2007

Amazon.com started by selling books. Their initial use case was “Sell books online.” The vision was always “Sell everything” – hence the name. But they started with a simple use case and evolved it.

Posts pagination

Previous page Page 1 … Page 18 Page 19 Page 20 … Page 32 Next page

Categories

Archives

Who Should Read Tyner Blain?

These articles are written primarily for product managers. Everyone trying to create great products can find something of use here. Hopefully these articles help you with thinking, doing, and learning.

Welcome aboard!

Recent Posts

  • You Can’t Always Get What You Want
  • Vibe Coding Into the Gale
  • Reaching Consensus on How
  • The Secret of Diminishing Returns
  • When Clocks Aren’t Reliable
Niche Blog WordPress Theme by Fahim Murshed