Number of views (374)
*The views, opinions and positions expressed within these posts are those of the author alone and do not represent those of Seavus Group.
We accept no liability for any errors, omissions or representations.
The copyright of this content belongs to the Seavus Group and any liability with regards to infringement of intellectual property rights remains with them.
12/30/2008 3:35 PM
Brad, great piece! How would you implement the proposals in projectoffice.net? More specifically the task reporting? Thanks, alek
12/31/2008 12:52 AM
Alek- unfortunately I'm not familiar with ProjectOffice.net, but I'm open to learning or a demo. I'm assuming it has some custom reporting capabilities...and that's really what I created in MS Project with the filters. Let me know how I can get in and learn some of the details of ProjectOffice.net. I may have a client that could use it - the pricing looks like it would be right for them. Thanks!
1/2/2009 5:56 PM
I see big risks on having the scope fixed at the start of the project:
-committing to impossible/impractical features
-committing to ill defined features
-leaving out higher value features
1/2/2009 6:06 PM
Gabriel- I agree with you. I don't think you can ever have your project scope 'fixed' at the beginning of a project. That's what gave and take is for, that's what phased implementations are for and that's what change orders are for. However, I do believe that if the PM or the PM organization is more involved in the sales process up front before the SOW is finalized, then you have a better chance of your SOW more closely matching the true customer needs and business requirements than if it is just thrown over the fence to the PM after the deal is done and the project is ready to be kicked off. Because, ultimately, it becomes the PMs responsibility to manage the scope, track all changes to it, and negotiate the change orders with the customer. A customer who is bombarded with change orders because the SOW was off is not likely to be a happy, referenceable customer.
1/9/2009 10:25 PM
Change orders should not be thought of as a bad thing. If a change order review committee (with budget authority) decides it is in the best interest of the company to add something, then that improves the project. It may cost more money, but what are the alternatives? A bad system.
Also, I chuckled a little to myself about the phasing. I don't know how many times I have responded to some great ideas that came up during a design phase with the term, "we will definitely look at that for phase 2" or after a while just "phase 2" for short. :) Unfortunately, many IT projects never get to phase 2 because the business elements that are important to make the phase 1 launch successful (process, change management, etc..) are not done well and/or the requirements were not performed with the right stakeholders.
change management model
9/10/2009 11:13 PM
change management model...
Have you read my change management model blog post? Usually applying those steps towards change are useful in any situation....
cheap mac make up 134221
2/12/2015 7:00 AM
cheap mac make up 134221...
mac cherish lipstick 224454 mac cosmetics uk sale 242444 contour powder mac 430310 mac makeup gift sets cosmetics 212441 blue brown mac pigment 044254 sitemap.xml...
If you are interested in conveying your message to your target market, please contact us at firstname.lastname@example.org!
Share you project management knowledge and expertise with the hundreds of thousands readers of PMTips.net. Apply here!