http://www.ssbits.com/home/ http://www.ssbits.com/blog/2011/5-tips-for-working-with-a-silverstripe-project-manager/#PageComment_498 Hi Darren Thanks for the feedback. As not all projects are the same I use different tools depending on the size of project, who is involved and how much reporting is required. For example if its a small project sometimes a five minute daily verbal catch up is enough. However for a bigger project especially where there are a few people doing the same role involved I've used google docs. On some occasions i have had to use the clients own project management software as this is how they have requested the project progress to be tracked. There are also lots of great (and sometimes free) online programs you can use but you need to find the one that works best for you and everybody involved. RSSName http://www.ssbits.com/blog/2011/5-tips-for-working-with-a-silverstripe-project-manager/#PageComment_498 http://www.ssbits.com/blog/2011/5-tips-for-working-with-a-silverstripe-project-manager/#PageComment_497 "White lies are good lies" I'd say "beware your optimism" - mostly all developers think of that moment when the function works for the first time in a protoype, not writing a complete test suite (considering all eventualities and combinations) and executing that testplan. There is a lot going on with Software estimation (http://en.wikipedia.org/wiki/Software_development_effort_estimation) and most of the time I'm under the most pressure to estimate the hardest things - e.g. brand new things using new technology. I still remember a lecture at uni where I was told to think of the inital number, double it and then if it's very complicated double it again. I don't often say it out loud because it is not the number people want to hear - they go crazy if you say too much of a large number or "I don't know" - but I've often found that simple rule to be very accurate. RSSName http://www.ssbits.com/blog/2011/5-tips-for-working-with-a-silverstripe-project-manager/#PageComment_497 http://www.ssbits.com/blog/2011/5-tips-for-working-with-a-silverstripe-project-manager/#PageComment_483 Thanks for sharing, @kulsoomkausher - as one who has worked as a PM and a Tech Dev, I can definitely say that your 5 tips are on point! Very relevant to a developer. You know, another thing that kills developers is all the reporting that some PMs make them do. A nice Agile Project Management methodoogy with a good Agile tool such as Agilo or Teambox really helps to keep the PM and Clients/Stakeholders up-to-date, while allowing the developers to focus on what they do best with minimal administrative duties ;) What methodology and tools do you use to manage your projects/clients/stakeholders and developers? Thanks again for the post. RSSName http://www.ssbits.com/blog/2011/5-tips-for-working-with-a-silverstripe-project-manager/#PageComment_483 http://www.ssbits.com/blog/2011/5-tips-for-working-with-a-silverstripe-project-manager/#PageComment_447 Thanks for the comments. As a PM I have been a culprit of some of the above myself (promising things before checking, and not liking the 'no'). Over the years having worked with some great developers who do say no, suggest alternatives, and educate as to why, have shown me the way. RSSName http://www.ssbits.com/blog/2011/5-tips-for-working-with-a-silverstripe-project-manager/#PageComment_447 http://www.ssbits.com/blog/2011/5-tips-for-working-with-a-silverstripe-project-manager/#PageComment_446 I've been a web developer for 8+ years now and I've found that those 5 steps can save your skin in many occasions. My boss is essentially the PM (which is good and bad), but when he asks how long it will take to build feature X, I tell him roughly double the amount of time it will take. So when I finish the new feature in "half the time" he is impressed and happy to know that I can move on to feature Y. This also allows for hiccups throughout the process, I have time to fix bugs and improve little things on the way. If he is uncomfortable with the amount of time I can adjust it as needed and still get things done with out stressing out too much. Being part of the planning stages is key. My boss will attend a meeting and over promise things I might not be able to deliver (has happened more times that I wish to remember). So now, if I know about the meeting, I will tell him that I want to attend and everything seems to go much smoother. Maybe this should be part of 4 or 5, but Don't be afraid to say "No", without actually saying "No". My boss and designer wanted Feature Z to sing and dance, and I bluntly said "No, I wont do that". I got yelled at, so now when I know something can't be done, or shouldn't be done, I help them to see that it will probably be a bad idea, and I can focus on the stuff that needs to get done and the cool stuff. RSSName http://www.ssbits.com/blog/2011/5-tips-for-working-with-a-silverstripe-project-manager/#PageComment_446 http://www.ssbits.com/blog/2011/5-tips-for-working-with-a-silverstripe-project-manager/#PageComment_444 Agreed, maybe tell the PM you have built in an additional 'half day / one day' to allow for unforeseen technical issues or tidy up. RSSName http://www.ssbits.com/blog/2011/5-tips-for-working-with-a-silverstripe-project-manager/#PageComment_444 http://www.ssbits.com/blog/2011/5-tips-for-working-with-a-silverstripe-project-manager/#PageComment_443 My experience is to try and ignore them as much as possible... Ok, no, not really, but indeed giving them something to be happy about works pretty fine, until they find out you can work faster then you say you can. Careful with the exaggerating the time needed for a project! RSSName http://www.ssbits.com/blog/2011/5-tips-for-working-with-a-silverstripe-project-manager/#PageComment_443 http://www.ssbits.com/blog/2011/5-tips-for-working-with-a-silverstripe-project-manager/#PageComment_442 Thanks Aaron. Agree with the diagrams especially as they take away technical jargon that often confuses clients! RSSName http://www.ssbits.com/blog/2011/5-tips-for-working-with-a-silverstripe-project-manager/#PageComment_442 http://www.ssbits.com/blog/2011/5-tips-for-working-with-a-silverstripe-project-manager/#PageComment_441 Great article with some great points that will make any developer's life easy with their PM. Giving the pm screen shots, flow diagrams and outlines of your understanding of what they want helps no end. Especially if you put them in a way that they can share them with the client to clarify what's required. Buying them the odd expensive coffee often helps as well From my experience giving the PM bad news early with reasons why and options that they can then take to the client so that they are prepared is a must. RSSName http://www.ssbits.com/blog/2011/5-tips-for-working-with-a-silverstripe-project-manager/#PageComment_441