shariyaz abdeen software / technical project management presentation

By Shariyaz Abdeen

[email protected]

Software Project Planning

Copyright © 2014 by Shariyaz Abdeen

Identify Clients Problem Why does the client need a new System ? What are the GAP they expect to fulfill b investing on the new

product ?

Accountability Transparency User Satisfaction Adopt to ITIL Standard Improved Analytics


Problem / Solution Analysis

• Requirement Gathering• Requirement Analysis• GAP Analysis• Root Cause Analysis• Cost benefit Analysis• Business Process Mapping • Business Process Reengineering



Putting the Project Manager in context – Possible Solution

Owner/sponsor“I want it allI want it now

I want it for free”

Solutions developers“Given all the other projects we are

already doing for you, the best we can do is a bit, in 6 months and it will of course

cost a bit”

Subject Matter Experts/Users“We must have this

- and soon! -or our business will fail”

Project Manager

Sales Manager“The sponsor will get it all,

now and for free”


More chaos stats

Source: http://blogs.msdn.com/b/dannawi/archive/2009/05/15/2009-standish-chaos-report-we-are-successful-in-the-failure.aspx

http://www.standishgroup.com/newsroom/chaos_2009.php


Applications technology

Organisationunit

Locations Processes

Scope of the Project

reason reason reason

reasonreason

reason

scope

anotherexternal

entity


User migration / ADRequirement

Analysis

Start

Set up Admins

Chat/Email Config

Password Reset / Remote Desktop

Config

Customizable Survey

BRS Documentation

Config Plants / Categories

Routing Rules

Escalation Rules

Dash board x 5

Reports x 5

Change Management

MSI Agent Deployment/Out of

office / F11 / Remember me –

other config

SMS Gateway Integration

SMS Application integration- inbound

Implementation Manuel -

Documentation System Testing

Train the TrainerShariyaz / Ananth

Deployment

Confirm – SMS application creation

Our Team

MAS

BPMN

Tracking Gantt- Scope / Time management


Resource planning - Team Planner


Microsoft Projects Team Planner provides you a over view of Resource allocation and at a time what is a particular resource is allocated. It is a nifty tool to affective to plane you resource with out over allocating.

Analytics - Work Overview


Work Overview Dash board


Project Progress


• Weekly Status ReportWeekly status report is used to alert the project stake holders about the project status ,

risks and upcoming activities. This provides a over view of the project status. • Minutes Of Meeting (MOM)After every meeting by maintaining a MOM document, we are able to keep track of

the meeting discussions , tasks what was agreed and the responsible party. Ones a Meeting is over we should loop all of the attendees and send a MOM document by email.

• LogI specially maintain a log file using Microsoft one note, which highlights the events ,

discussions and tasks which we supposed to do and the relevant documents attached to it. This is a very effective way to maintain project data because ones there is a issue or ones you are at a meeting , you are able to go through the log and find what exactly we have agreed and provided.

Weekly Status Report – Email body summery


Project Log


PMAT (Priority Metrix)


Here is the framework which I use to help determine how I allocate my own time across these areas.

Home Runs: These are project which has a high value and a high probability to be success. I Delegate it to a star on my team, set guidelines and goals, ensure it has the right resources, and watch it closely by getting weekly project status to ensure that it maintains a high probability of success.

Small Wins: these are project which has high probability of success but low value. I delegate these projects, but I am less focused on selecting the Team Lead. Its best suite to provide the opportunity to a team member who seeks an opportunity to develop a new skill set such as lead a small team. We should not worry about tracking these projects explicitly, and try to make sure that my big stars are not working on them either.



Big Bets: This is where I can add most value, so I DOUBLE DOWN and get personally involved. Should scrutinize these opportunities before getting involved though since I can only handle one or two of these projects at a time. They must be high value, but also not too low probability. My goal is to use Analytical skills and problem solving skills to turn this project into a "Home Run". I also watch for signs that the likelihood of success is so low that the project should be cancelled, in which case I facilitate the shut down.

Junk: Should not ignore Junk projects. In fact, should Focus on them. I get directly involved and Destroy, so as to free up the organization’s resources for other projects. This is where managers can spend time very effectively and make a difference. Everyone has Junk projects occurring at their company and removing them can be tremendously helpful.

Q&A? Q&A?


shariyaz abdeen software / technical project management presentation

Leadership & Management