This week in the pm-clinic discussion forum: Topic #42 – Managing the 2nd class project:

I am tasked with the creation of a strategy for a relatively low priority product. We have a small team of programmers (Team B) and everyone understands that what we’re making is built to support what one of the other teams is doing (Team A). My questions:

1) How do I keep my team motivated given that we know we’re 2nd class?
2) How do I protect ourselves, and our work, from changes made by Team A?
3) How does a low priority project (and its team) get its share of the limelight?