10 b-earthsoft-project management-experience based

Making earth little softer

Earthsoft Foundation of GuidanceEdge-Aggressive-Reliable-Trust-Honesty-Soft-Obedient-Fun-Transparent

Project Management- Experience based


Earthsoft Foundation of Guidance (EFG) has uploaded following presentations at http://myefg.in/downloads.aspxAlso https://dl.dropbox.com/u/83265908/Links-events.xls has linksBe mentor using your education, knowledge & experience to contribute for a social cause & do conduct free training seeking help of existing platforms. Kindly share with your friends•Motivation for higher study, Planning for study, Education guidance, Career guidance, Career available after SSC & HSC•Personality development – 3 files •How to prepare resume, Tips to attend interview successfully•Religion related –To understand basic religion, Do &Don’t tips•Health related - Be vegetarian, Be healthy, Stop alcohol, •Corporate - Project management, Assertiveness, Ownership•Finance - To avoid speculation in stock market•Social - Women empowerment, Choosing life partner

About us

http://myefg.in/downloads.aspx


• Relationship• Project Management• While executing• Project Management• Key steps• Right factors • SDLC Phases• Key phases• Output• Phase wise effort

distribution• HL Schedule

Index• Requirement Analysis• Design• Development• Testing• UAT & Deployment• Risk management• Commitment• Quality• Estimation• Success Tips• Reviews• Vision


Relationship

Management

Employees


Project Management

Project Management

Scope & Change control

Schedule

Efforts & Cost

Quality

SMC or FP or LOC

Milestones & Dates

Man-months

Defect per mm


While executing

Project Management

Integration & Deployment

Risk

Communication

Resource

Sign-off from client

Mitigation & owner

Escalation Metrics

InfraPeople

Technology


Project Management• KT sessions across team about requirements• Efficient risk management • Support by seniors• Efficient PMO management

Plan Track Control MeasureEffortsScheduleQualityCostRisksResources


Key steps

Project Execution Cycle

Estimation

Planning & Scheduling

Costing & BudgetingDeployment

Measurement & Matrices


Right factors

Project Execution

Facilities/ Infrastructure

ManagementPlan

ExecuteMeasureControl

CommunicationTeam - Skills & Motivation

Processes


SDLC Phases

Project Execution Cycle

Requirement Analysis

High & Low level design

Development & Unit Testing

Integration & Application

Testing

Users Testing &

Deployment


V Model

Business Requirement

High Level Design

Low Level Design

Coding &White box testing

Application Test cases

Integration Test cases

Unit Test cases

RFP document Acceptance Tests


Other Models• Waterfall• SDLC – V, Customised, Incremental Model • Rapid application development• Extreme programming - XP• Agile and Feature driven design• Dynamic systems development model


Output# Phase Output1 Requirement

AnalysisProto type, Functional documentApplication Overview and diagramBreakdown of application in Modules, Sub Modules, Screen layout & Screens functionalities, common validations & rules, business rulesScreen transition diagramER design/ External filesExternal communicationSoftware/Hardware requirementDeployment DiagramOut of scope


Output# Phase Output2 High

Level Design

Low level design

Design document Class listing, Class diagram, Sequence diagram, Common design rulesDetailed Screen specificationsPhysical Database design; E-R Database design, Integration Test cases, Test dataProgram specifications, Unit test casesScreen specifications (Field level validation) & business rules, Unit Test case, Test data


Output# Phase Output3 Build Code

Test results of Unit testing4 Testing Integration Test results

Application Test resultsBug posting & Tracking till closure

5 UAT & Deployment

Test resultsSystem Manual & User’s ManualsTraining


Phase wise effort distribution # Phase Tentative effort distribution in%

10-15 15-20 35-45 15-20 5-101 Requirement Analysis2 High & Low level Design3 Build4 Testing5 UAT & Deployment

Type 1 T & M FixedType 2 FixedType 3 T & M

Duration = k * SQRT((efforts in mm)), k=0.8 - 1.2Save as much efforts right from the beginning


HL Schedule




Gather & Note

Think Discuss & Brainstorm

FeasibilityConserve

Documents

Flow Diagram Screen Design

Estimation Review

Conclude


High & Low level Design

High & Low level design

Technology & Framework

decisionTechnical Architect,

Framework development

Design Document (Use cases, Class Dia, DB

design, Sequence Dia, Common Design, Screen

specifications)

Interfaces Design

Test cases

Validations & reviews


Development

Development

Guidelines (Do it FIRST time RIGHT),

check listLook & Feel, Traceability,

Coding & review

Strong Code reviews

Unit test cases, test data,

testing, test result

InterfacesIntegration

Testing


Testing

Testing

Absolute matching

environmentsReviewed test

cases, IT & AT, daily

measurement

Test data, right tool,

Performance, Load, regression

Detect maximum defects & Track till closure, Test

results

Plan at least 3 round of

testing


UAT & Deployment

UAT & Deployment

Absolute matching

environments

Staging & Live server

management

Configuration of servers

Installation of software

System manual, Users manual,

Training

UAT & closureClosing

document


Risk management# Risk

/ IssueDate Description Probability

%Impact Exposure Mitigation

planOwner Closure

date

• It’s a skill to envisage the risk• Efficient project manager smells the risk & act

fast to mitigate / close the risk• Tracking the risks till closure is key task of PM


Commitment to customers

Commitment to Customers

Minimum defects per mm efforts

Timely delivery

Minimum total cost

Periodic Reporting

No surprises

Support & comfort levels


What is Quality• Functionality related gap between expectations

of client and actual delivery• Defects are injected during Requirement, High &

Low level Design and coding phase• Continuous reviews help to prevent defect

injection• Rigorous testing during Unit level, Integration

and application level testing detect the defects.• Both of above processes remove the defects

RA R Design R Coding R UT IT AT


Quality measurementNo. of defects 1effort in manmonths 3Loc per hr 10Lines of code 4800no. of defects 1% of defects to LoC 1*100/4800=2.1%Achieved quality 97.9167%

• 1 defect detected by customer for 3 man months of efforts is said to be fairly good quality

• Count each type of defect (minor, normal, major, critical or blocker) ; Minor defect is worst!


CMM 5Level 3 – Defined

-- peer reviews, intergroup coordination-- software product engineering-- integrated software management-- training program-- organization process definition & focusLevel 2 – Repeatable-- software configuration management-- software quality assurance -- software project planning, tracking and oversight-- requirements managementLevel 1 – Initial


CMM 5Level 5 – Optimizing

-- process change management-- technology change management-- defect preventionLevel 4 – Managed-- software quality management-- quantitative process management


Estimation numbersDescription Alt 1 Alt 2

LoC per FP (historical data) 53 40No of FP per month 10 8No. of days per month 20 20No. of FP per day (data) 0.5 0.4Loc per day (without blank & comments)- Java

27 16

LOC per hour 3.3 2.0Screen based estimation

Days Loc1 Simple screen 9 2391 Medium screen 18 4771 Complex screen 27 716


Estimation# Description1 Executive Summary2 Cost Estimation3 Phase breakup4 Estimation5 Schedule 6 Team Structure7 Approach

# Description8 Assumptions9 Risks & Mitigation

10 Deliverables11 Pending list12 Out of scope13 Prerequisites14 Terms & Conditions

Define following• Rate per manmonth –Av. base rate or resource wise• Type of project (Fixed, T & M, Hybrid)• Project execution methodology


• Have you planned entire project?• Do you have appropriate duration?• Would you have enough appropriate resources?• Do we track our assignments? & follow up till

timely closure? • Are tasks completed as scheduled?• What is tracking methodology?• Do you have daily stand up update meetings?• Are assignments piling up? Why?• “First time right” Is it happening?• Single window system – task given & collected?

Or huge overloading?

Ask for


• Anyone getting overloaded? Is this acceptable? • Multi tasking? Need of a day? Is it sustainable?

Do you have choice not to assign multi-tasking?• Tracking & Closing threads? And tasks?• When do we decide to close a day?• Do we update the status before leaving?• Are risks being mitigated?• Are you maintaining measurement matrices?• Are we achieving Key result Area (KRA)?• Ownership? Does each of team member own?• Is quality being achieved?• Are we heading towards tough situation?

Ask for


Success Tips

Right Project Management

Right Team

Right Processes

Project Success(Quality & Timely

delivery)

Ris

k m

anag

emen

t rev

iew

s &

su

ppor

t fro

m s

enio

rs

man

agem

ent


Reviews• Every deliverable must be reviewed• Sharing experience & education from senior

management till project managers levels• Vibrant enablers & making those visible

PMO

QMG

TMG

SEPG

RMG• QMG – Quality Management Group• TMG – technology Management Group• RMG – Resource management group• SEPG – Software engineering process group• PMO – project Management office


Vision

Know

ledg

e / T

ech.

Man

agem

ent

Right Facilities

Right Skills / Motivation

Ri

ght M

anag

emen

t

(Pla

n/M

easu

re/C

ontro

l)

Right Processes

Righ

t

Com

mun

icat

ion

Trust and Comfort Feel

Qual

ity o

f Res

pons

eValue for Money

Tech./ Domain Skills / Experience

Spee

d of

Res

pons

e

Human Resource Management

Faci

lity

/ Inf

rast

ruct

ure

Right Skills / Motivation Finance Management

EXECUTION

MARKETING

ORGANISATION

Minimum Defects Timely Delivery Minimum TCC


Thank You