The document outlines the project management process and includes 26 steps organized across various project phases: initiation, planning, execution, quality assurance, intermediate delivery, UAT, final delivery and closure, and change management. The initiation phase involves kickoff meetings with internal and external stakeholders. Planning develops the project plan and risk registry. Execution covers task assignment, standups, demos, and escalation. Quality assurance ensures testing approval. Intermediate delivery requires client approval. UAT involves client testing. Final delivery deploys the code and database. Closure gets client signoff. Change management defines change requests and approvals.

1. Project Management Process
Presented by : Jay Shah
Presentation Date: 05/01/2017

2. Agenda
• Explain Project Management Process
• Q&A?

3. Project Phases
• Project Initiation
• Project Planning
• Project Execution
• Quality Assurance
• Intermediate Delivery
• UAT
• Final Deployment, Delivery and
Closure
• Change Management

4. Project Initiation

5. Step 1: Sales Kick-off
•Initiator/Accountable: Sales Member
•Other stake holders: PM
•Pre-requisites: Proposal Document, Estimation document, Any
other document, Project Handover Sheet along with client
behaviour and time zone
•Communication medium: Email invite a day before to the
Project Manager with all prerequisites supplied
•Description: Very important meeting for project understanding
by PM
•Post-requisite: MoM to be shared by Sales Member

6. Step 2: High Level SRS Start and
Requirement Gathering Checklist
•Initiator/Accountable: BA and only if not available then PM
•Pre-requisites: Step 1, Proposal Document, Estimation
document, Any other document, Project Handover Sheet along
with client behaviour and time zone
•Communication medium: Word doc in PM docs template
repository
•Description: Here initial understanding of PM should be jotted
down in form of high level feature listing and if possible
wireframes
•Post-requisite: SRS and Requirement Gathering Checklist

7. Step 3: Internal Kick-off
•Initiator/Accountable: PM
•Other Stakeholders: DU, TL, PTL, QA
•Pre-requisites: Step 1, Step 2, Proposal Document, Estimation
document, Any other document, Project Handover Sheet along
with client behaviour and time zone
•Communication medium: Email on the day or a day before the
meeting.
•Description: Here initial understanding of PM should be
transferred and shared with the development and QA Team. PM
should either answer their queries or jot it down to ask client.
•Post-requisite: MoM to be prepared by PM with list of queries.

8. Step 4: External Kick-off
•Initiator/Accountable: PM
•Other Stake Holders: Client and Sales
•Pre-requisites: Step 1, Step 2, Step 3 MoM
•Communication medium: Email on the day or a day before the
meeting.
•Description: Here PM introduction, initial understanding of PM
along with queries from internal kick-off should be talked about.
Decide Communication Channel and High Level Resource
Engagement plan.
•Post-requisite: MoM to be prepared by PM with list of queries,
their answers and/or any clarifications/additional conversations.

9. Step 5: SRS Modification
•Initiator/Accountable: BA and only if not available then PM
•Other Stake Holders: NA
•Pre-requisites: Step 1, Step 2, Step 3 MoM, Step 4 MoM
•Communication medium: Doc used in Step 2
•Description: Update SRS
•Post-requisite: NA

10. Step 6: External-Internal Handshake
Meeting
•Initiator/Accountable: PM
•Other Stake Holders: PM, Development Team, QA
•Pre-requisites: Step 1, Step 2, Step 3 MoM, Step 4 MoM
•Communication medium: Email on the day or a day before the
meeting.
•Description: Here PM talks/shares his conversation with other
stake holders in the meeting.
•Post-requisite: MoM to be prepared by PM.

11. Step 7: Final SRS update and Approval
•Initiator/Accountable: BA and only if not available then PM
•Other Stake Holders: Client
•Pre-requisites: Step 5 & Step 6 MoM
•Communication medium: Update the Doc used in Step 2
followed by Step 5 and an email.
•Description: Here BA/PM updates the SRS and sends an email
for client to approve it.
•Post-requisite: Approval from client

12. Project Planning

13. Step 8 & 9: Project Plan/WBS and Risk
Registry
•Initiator/Accountable: PM
•Other Stake Holders: DU
•Pre-requisites: SRS Document
•Communication medium: WBS/Project Plan Template
•Description: Here PM makes the project and send DU for
approval. This should adhere the estimated time sent by
development team while getting the project in. In case of any
deviation, DU must share with PM as to what made the
estimated time slide ahead.
•Post-requisite: WBS/Project Plan, Risk Registery Approval from
DU/TL/PTL

14. Project Execution
Note: Kindly maintain Project Credentials Sheet

15. Step 10: Get, Update and Feedback
•Initiator/Accountable: PM
•Other Stake Holders: Development Team, Client
•Pre-requisites: Task Lists
•Communication medium: Email template supplied
•Description: Get from Development Team and then Update
Prospective Weekly Tasks to Client/ User Stories (Agile), Tasks
Done in current week and Task/Team based feedback from
client
•Post-requisite: Weekly/Daily Work report, feedback from client
on tasks, Daily Work Report to DUH and PMO

16. Step 11: Task Assignment to Team
•Initiator/Accountable: PM
•Other Stake Holders: Development Team, Client
•Pre-requisites: Task Lists
•Communication medium: ERP
•Description: Assign task on daily or weekly basis
•Post-requisite: ERP entries filled up by employees on regular
basis. Resource are self responsible for the same.

17. Step 12: Stand-up Meeting – Routine
•Initiator/Accountable: PM
•Other Stake Holders: Development Team
•Pre-requisites: Task understanding by resources
•Communication medium: Verbal away from desk
•Description: This stand-up is meant to make sure resources are
aware of what needs to be done, what are possible obstacles,
any back logs and any dependencies within the resources.
•Post-requisite: PM should take note of commitment for during
the day monitoring.

18. Step 13: Constant interaction with
resources
•Initiator/Accountable: PM
•Other Stake Holders: Development Team
•Pre-requisites: Step 12 awareness
•Communication medium: In person
•Description: This is to constantly interact with resources to
know what has been accomplished, what is remaining and what
they are currently going through. This should ideally happen at
least twice a day.
•Post-requisite: Deliver as per daily expectations

19. Step 14 & 15: Escalation and Update
•Initiator/Accountable: PM
•Other Stakeholders: PMO, DU, TL, PTL, Client
•Pre-requisites: NA
•Communication medium: Email and/or in person
•Description: This step is important if any related to resource
availability, skills, project requirement
•Post-requisite: Follow ups on action plan

20. Step 16: High Level Test Cases From QA
Team
•Initiator/Accountable: PM
•Other Stakeholders: QA Team
•Pre-requisites: SRS
•Communication medium: Email the test case document
•Description: This step is not in sequence and should happen as
soon the SRS is submitted to QA team
•Post-requisite: Test Cases/ Test Scenarios

21. Note: Daily check of payment
milestones and raising invoices and
follow ups

22. Quality Assurance (QA)

23. Step 17: QA Approval (Follow QA
Processes)
•Initiator: PM
• Accountable: QA Team
• Pre-requisites: Project Credentials
•Communication medium: Email the test case document with
test results. Bugs registered in bug tracking tool
•Description: This step should be before any intermediate
delivery to client
•Post-requisite: Approval from QA

24. Intermediate Delivery

25. Note: Mandatory to take approval from
client that what we have delivered is as
per his/her expectations and payments
are inline with that. This should be
strictly followed on basecamp/emails at
priority. This will be official Proof Of
Delivery. We would be responsible for
this.

26. Step 18: Demo/Delivery to client with
release notes
•Initiator/Accountable: PM
•Other Stake Holders: Development Team, QA
• Pre-requisites: QA Approval
•Communication medium: Email to client with test cases we
have checked
•Description: This step is important and earlier note should be
taken into account after delivery.
•Post-requisite: Release note and positive feedback

27. User Acceptance Testing (UAT)

28. Step 19: UAT Follow up
•Initiator/Accountable: PM
•Other Stake Holders: Client
• Pre-requisites: All intermediate deliveries accepted
•Communication medium: Email to client with test cases we
have checked
•Description: This is the phase where user acceptance testing is
carried out by client himself/herself or with prospective clients.
Constant follow up should take place to keep this period as little
as possible and as productive as possible.
•Post-requisite: Production environment setup ready to deploy
the latest code-base, Approval for final delivery from client and
project-support.

29. Final Delivery and Closure

30. Step 20: Installation of all
pre-requisites
• Initiator/Accountable: PM
• Other Stakeholders: IT Team, Developer, TL, PTL
• Pre-requisites: Client Approval for final delivery
• Communication medium: Email, in person and glip
• Description: All pre-requisites should be available
• Post-requisite: Ready environment for delivery

31. Step 21: Deploy code and DB
• Initiator/Accountable: PM
• Other Stakeholders: IT Team, Developer, TL, PTL
• Pre-requisites: Client Approval for final delivery
• Communication medium: Email, in person and glip
• Description: All pre-requisites should be available, code
should be latest from repository, current DB backup and
dump as per instructions by client
• Post-requisite: Delivered working copy of project

32. Step 22: Last run of QA
• Initiator/Accountable: PM
• Other Stakeholders: QA Team
• Pre-requisites: Step 21
• Communication medium: Email, in person and glip
• Description: Last over view and approval from QA team
• Post-requisite: Delivered working copy of project to client

33. Step 23: Get Delivery
Confirmation
• Initiator/Accountable: PM
• Other Stakeholders: Client
• Pre-requisites: Step 22
• Communication medium: Email, Base Camp
• Description: Send Email/BaseCamp Message to client
regarding delivery and confirmation
• Post-requisite: Yes, I approve (or may be some other text)
message from Client.

34. Project Closure

35. 3 Step process
Step 24: Client Sign Off based on proposal and
deployment on BaseCamp
Step 25: Client Testimonial and Case Study
Step 26 : Project Closure in ERP

36. Change Management

37. Following to be done by PM
• Define CR based on SRS and Proposal
and if > 1 hrs of work and not regular
• Impact Analysis Document- Which
tasks would it impact ? and estimated
time
• Get Approval from PMO Head and DU
and provide it to Sales who would
inform to client
• Update SRS and send it to all
stakeholders

38. Q & A?