best-practice in ERP Project Team

Testing is moving forward as expected.  We need to close down user testing and start with integrated activities.  This is a best practice we need to follow

The project is moving forward as planned.  We need to get started on integration testing.  It is a best practice we need follow.

Team,

We are tracking the following issues that I would like you to update as soon as possible.  As you know this is a best practice that we all need to follow:

1. Architecture
2. Data Migration
3. Training

All,

Please make sure you post all RFI responses to the GroupSwim site as soon as you send them out.  This is a best practice for the team.  Redaction and other topics are important to capture.

The project is proceding as planned.  We are about to begin integration testing next week, which is a best practice for a project this size.

The ERP project is on schedule.  We've had a couple of delays related to the XML interface but we feel we have it under control.  Putting this kind of interface in is a best practice for leveraging the rest of our infrastructure.

See the attached issue log for status on this week's project.  Adding this information is a best practice that we all need to follow.  Please reply with any questions or comments.

The team met today and reviewed the attached issue log.  This is a best practice and I encourage everyone to follow.  See attached code sample

This is a capital budgeting spreadsheet that everyone should review before we fund the project.

It is a best practice to document all decisions that are made by the project management team.  Here is the latest version of the document.

This file was posted as an attachment. Original text: