While I just started reading Effective Software Project Management, and I liked the beginning (well, I'm not spoiled with PMBOK), I have raised some questions for myself from the first pages. Robert discusses choosing the software development landscapes, which he divides into 4 quadrants of the relevance between Goal and Solution (by the way, personally, I like this approach). However, what if my project is so called "liquid" (sorry, it's weird my therminology), which can be born in one state (say, Goal is Clear and Solution is Clear) and dramatically moves into other state (like, Goal is not Clear and Solution is not Clear, too). It's pretty easy, nowadays. I.e., I've a profitable business model, and I want to clone it to wider my business space. At some point I am changing the business model - Goal (come on, it happens more often than you have a vacation!), so the Solution changes as well. Does it necessary become a separate software development project, with its own landscape and how flexible should I be (as the project manager) to move between two quite different approaches? What if I am keeping the core model trying to keep as much profit as I can from an old business model, adding a new, "featured" business model to it? Well, its weird and I guess its all about the "moment of change". If you was able to catch it, you can have a two different software developmen projects. Otherwise, you screwed up.
BossTalks.com » General (English)
Effective Software Project Management, a question from the book
(1 post)-
Posted 4 years ago #
Reply
You must log in to post.