General discussion

Locked

Deployment Project Management

By duit4you ·
I have been ask to create project management strategy to Deploy a Bank Application and data migration on 600 branches. I try to start with Assesment of current state but I don't know where to start to assest and how to documented.
Regards,
Delly

This conversation is currently closed to new comments.

4 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Deployment Project Management

by srini In reply to Deployment Project Manage ...

We can do it for you? Some more info

Collapse -

Deployment Project Management

by The Chad In reply to Deployment Project Manage ...

I'll post a WBS for deployment for you at

http://masterdev.dyndns.dk/proj/

It will be available on Tuesday, May 27, 2003.

Collapse -

by kathykeat In reply to Deployment Project Manage ...

1. Start at the very beginning...its the very best place to start...when you count you start with 1 - 2 - 3 when design a network you start with

1. Understand the business benefit desired from the redesign. If you want to be successful you need to know why there is a need for change and what not to break while you are making that change.

Collapse -

by kathykeat In reply to Deployment Project Manage ...

1. Understand the business benefit desired from the redesign. If you want to be successful you need to know why there is a need for change and what not to break while you are making that change. If you make a change on any unbreakable, make sure you can back it out in seconds flat and have permission before you do it from the main users and your CIO.
- can the application be down? How Long? (one time during the cutover? routinely for maintenance?

This will be the basis for the type of network and computer equipment required. If the application must be up 24/7 you will use High Availability design principles. If you are allowed routine maintenance and can stand random outages of x hours, then you can select signficantly less expensive alternatives. You should get this information from your internal business customer or manager.

Make a list of persons involved in the project.
They....are....your....virtual...project team. . . and customers who will judge you in the end.

Call them all and let them know the change is coming and is in the development phase. Ask for their input. Get access to systems- find out who provides passwords,etc if you do not already have root/admin accounts on the system.

Is it a flash cut where everyone needs to start using the new software at the same time...which is another level of difficulty.

Write up a timeline (use excel...don't mess with project unless you already know it well for this first draft.)

Write up a first cut project plan listing each step...make sure you include input from the customers and users (meet their needs whenever practical)
Write up your technical implementation process
Write up your roll back plan
Meet with team to finalize plan.
Meet with Security to reivew plan
Meet with change management team to schedule change time and roll back if required.
Implement
Give lots of cookies out at the end...The users might as well get them since IT personnel rarely do.

Back to IT Employment Forum
4 total posts (Page 1 of 1)  

Related Discussions

Related Forums