New answers tagged

0

An always-true answer on either of these two alternatives does not--or should not--exist. This is a benefit / cost and risk decision that should be carefully and thoughtfully examined. Then, whichever answer you choose, the costs and risks of that answer need to be mitigated to the degree possible. You launch too early, you run the risks of having your ...


0

Completely(!) Disagree! "Whatever else you do, make the Lady look Beautiful." I'm the customer. I had no idea that your product was even available for me to buy(!!)(!!)(!!) until this very moment. Within the space of the following two minutes, one of two things is going to happen: I'm gonna luv it, and I'm gonna tell all of my "friends.&...


3

Launch the MVP, if it does the job Welcome to pm.stackexchange! You would have made many assumptions about what the users need and how they will use your product. These assumptions need to be validated by letting early customers use it. Based on the feedback you gather from them, you may have to make drastic changes to the app. When you do that, all the '...


0

Work is probabilistic. There is always variability in work efficiency caused by an unknown number of variables, including skill, but also including random noise. An individual will also produce variable outcomes doing the same work. Also, duration = hours under few circumstances. None of us is 100% productive when we work. So if the duration equals five ...


0

This is the way we should think correct? That depends entirely on your type of project. Most likely, no, this thinking is way oversimplified and will lead you to operate on numbers that do not reflect reality. A woman can deliver a baby in nine months, two women can not deliver a baby in four-and-a-half months. A skilled woman will not be able to deliver a ...


Top 50 recent answers are included