Once (ok, let’s be honest, not just once) I was thinking, “Why not to get rid of estimations?”. I heard a lot from the developers in our company that they hate estimating. That is usually a very painful process for a project manager, too. Not only because of the process itself, but because of what happens afterwards. If you worked on more than one project, you definitely know that the estimation your team created won’t be ok for business people. They certainly know that this feature is very easy and that story can be done in a day… Or, “My colleague – he is a developer himself – thinks this can be done in a week!”. They all need hours, exact numbers and deadlines. Team wishes not to provide that.
If you are a project manager you definitely have ever told your colleagues “I hate these reports! Why do they require those stupid report for every tracked hour? I spend several hours to create it!” You have a weekly call with the customer on the status and have to prepare for it whole the day? You hate Mondays, not only because it is the hardest day of the working week but also because report call? You have to explain each hour spent on the project? It rings the bell? If yes, we are on the same side.
Every PM has a lot to tell you about different fuck-ups on his projects. But why we share our fails so rarely? Of course, it is difficult to tell others about your failures, so we prefer to tell only funny stories or “one of my friends…”. We with my colleagues suggested to create the list of most common problems on our projects. I can’t hope it contains some new and fresh ideas but al least it should persuade you that you are not lonely in this world of failures.
This is a post for PMs only. High risk of PM tricks and manipulations techniques been uncovered.
No doubt, PMs write a lot of emails every day and this is one of the main communication channels for us. As we are trying to communicate more verbally now – emails are usually used for discussion of some important topics with boss, customers, users, etc. – situations, when PM should be rather careful with language and phrases he uses in emails 🙂 So it is time to switch on your brains and create the text, that can be understood by the person on the other end.
The three main techniques for rapid prototyping are: storyboarding, paper prototyping, digital prototypes.
It is one of the first questions PM hears from the client. From the client’s side the ideal situation will be: receive the application he desires for the fixed price and fixed time. And no excuses) But is it as simple as the client thinks? I tied to gather the cons of the fixed price projects and pros of time & materials to prove my point of view – either client and developer receive a great benefits if they work on a time&materials contract.