Project Management  IT  Construction  Finance 
Process Downloads Articles Tools Training Discussions About Us Search
 advertisement
Enable Agile Process; Support Agile Teams
CollabNet announces ScrumWorks Pro 4.4. As intuitive as Scrum itself, this version offers improvements in estimation and integration to CollabNet TeamForge. Improve your Scrum team's performance, enable tracking, view reports instantly, and effectively manage your Agile projects. Request a Trial

topic list
Posted by Subject: Re: Design, Build, Implement,... then what?
Anonymous post Posted Oct 21, 2005 08:19 AM
For any IT projects; Design, build and implement are important as well as crucial. what comes next is definitley the ongoing support from the project team and the co-operation of stakeholders; specfically the end-users. As a project team u gotta go back and check their requirements once again to develop a better system. Anyways, if you don't define the users requirements, your project is going to fail.

 

Anonymous post Posted Apr 02, 2004 01:46 PM
No IT project will be 100 % complete. There might some thing you always need to do [better].. You can first start from your bug tracking tool to see what types of bugs that can [still] be fixed, what are the enhancements list Ofcourse after talking to your stake holder and getting his acknowledgement and approval. You can have a survey from your clients and see the strengths and weakness of the project and ofcourse the developers will definetly know their area of weakness in the project and you can also start thinking how to build it.

 

Mike Barry Posted Mar 12, 2003 07:04 AM
I would start with my ERP Vendor, they should have experience here or could put you in touch with previous customers so you can talk to them about their experiences. A word of warning about Case Studies from Vendors - they can be a bit idealised. Also try talking to the users and your IT support, I am sure they will be able to express their expactations of the ERP system and have opinions of what they want to see from it in the future. This should give you a good lead to building that framework.

 

Anonymous post Posted Feb 05, 2003 06:05 PM
I'm currently working on a major ERP implementation that is coming to the end of the Implementation phase. Apparently not much thought has gone into what will happen after the last plant goes live because I've been asked to look into our options for leaving behind a framework to support/maintain the system... and possibly improve and expand upon it in the future. We are currently experiencing a lack of resources and, as a result, are suffering a lack of communication to the end users regarding changes within the system. Therefore, my focus of late has been on improving communications... which is a role that some project members will migrate to when their implementation activities end. What other things should I look at? What questions should I ask management? Are there checklist, articles, case studies that demonstrate how other companies have undergone this type of transition?

 

topic list

Post to This Topic


Copyright © 2003 projectmanagement.com
Publish on projectmanagement.com | Submit a Template | Privacy Policy | User Agreement | Advertise