It Project Management – Explained: For Software Developers

IT PROJECT MANAGEMENT—EXPLAINED

For Software Developers

KRISHNAN VASUDEVAN

Copyright © 2013 by Krishnan Vasudevan.

ISBN:      Softcover      978-1-4828-1440-8

                Ebook          978-1-4828-1439-2

All rights reserved. No part of this book may be used or reproduced by any means, graphic, electronic, or mechanical, including photocopying, recording, taping or by any information storage retrieval system without the written permission of the publisher except in the case of brief quotations embodied in critical articles and reviews.

Because of the dynamic nature of the Internet, any web addresses or links contained in this book may have changed since publication and may no longer be valid. The views expressed in this work are solely those of the author and do not necessarily reflect the views of the publisher, and the publisher hereby disclaims any responsibility for them.

Partridge books may be ordered through booksellers or by contacting:

Partridge India

Phone: 000.800.10062.62

CONTENTS

Preface

1   IT—A growth enabler

2   Planning for initiatives

3   IT Organisation Structure

4   Request For Proposal (RFP)

4.1   Initiative kick-off meeting

4.2   Receiving the documents related to the initiative

5   Proposal Submission

5.1   Putting together the team

5.2   Opportunity call

5.3   Follow-up call

5.4   Proposal preparation

5.4.1   Effort and Cost Estimation

5.4.2   Scope

5.4.3   Solution

5.4.4   Execution approach

5.4.5   Assumptions and Dependencies

5.4.6   Critical Success Factors

5.4.7   Roles and Responsibilities

5.4.8   Risks

5.4.9   Governance Model

5.4.10   Communication protocol

5.4.11   Contract model

5.4.12   Financials

5.4.13   Contract Termination terms and conditions

5.5   Proposal submission and walkthrough

6   Start of Engagement

7   Project planning and monitoring

7.1   Project Setup

7.2   Project Execution

7.2.1   Project tracking and monitoring

7.2.2   Project Reporting

7.2.3   Senior management reviews

7.3   Project Closure

8   Deliverable verification and sign-off

9   Production roll-out and Warranty support

9.1   Production roll-out

9.2   Warranty support

PREFACE

Have you ever been bogged down and exasperated by the mire of activities to do under what often goes by the name of Project Quality Process? Ever wondered if those reports are even read and if all the data collected has any use and if it is anything more than just a mandate for process compliance? Have you ever discussed with friends on what your Project Manager might be busy with as you struggle for long hours to do the development work on the engagement?

I am sure you would have had atleast some of these normal questions that occur to every software professional at some point in the early part of their career. I too have had these questions arising in my mind and have wondered why someone would add more burden on me instead of allowing me to finish my work and go home at an earthly hour.

All the discussions I have had with my team-mates led me to the desire to produce a short write-up on this topic. I toyed with the idea for a long while and finally started to write in 2012. After a couple of starts and stops where I wrote furiously for a period and then kept it on hold, the write-up is ready for the first look.

In this write-up, I attempt to de-mystify what IT Project Management is, cut through the ominous-sounding terms, discuss the benefits and understand why clients and IT partners alike are keen on a systematic Project Management approach and most importantly, why a structured, objective and comprehensive Project Management approach will help you finish work Well and Fast and save you time to follow your hobbies and enjoy all the wonderful things