Project Management in IT

Arseniy IgnatyevContributor: Veronika Olenik

2

Arseniy Ignatyev

3

C.T.Co

4

What is Project Management? Necessary skills Software development project management

and related techniques Failure and Success Q&A

Agenda

5

“Go ahead and do it” approach Run the business / operations approach Project approach

Need Something Done?

6

Project - Planned set of interrelated tasks to be executed over a fixed period and within certain cost and other limitations.◦ New Airplane◦ New Cell Phone◦ New Software

Why Project?

7

Process planning and control Timely risk identification and mitigation Grater assurance in the positive result

Why Management?

8

Project Management is the application of knowledge, skills and techniques to execute projects effectively and efficiently.◦ project management brings a unique focus shaped by

the goals, resources and schedule of each project.

Why Project Management?

9

Until 1900 projects were managed as "go ahead and do it" by the chief engineers

1900 – 1950 – a transition period. Henry Gantt and Frederick Winslow Taylor developed the structured processes and tools: WBS standing for “Work breakdown structure” and Gantt chart

At 1950 project management became structured. Fields that could be considered as starting point: civil engineering and military

IMPA – 1967 in Europe and PMI – 1969 in US

History

10

Integration Cost Human Resources Scope Quality Communications Time Procurement Risk Management

Project ManagementKnowledge Areas

11

Leadership Negotiation Planning and controlling Domain knowledge Critical thinking Psychology Expectations management

Project Management Fields of Expertiese

12

•Define Result•Define Business case and Justification•Define high level milestones•Identify constraints and costs•Identify Sponsor and stakeholders•Define Success & Failure

•Identify Deliverables and WBS•Scope management•Cost management•Resource management•Risk and response planning•Estimating time and cost for activities

•Direct and Manage Project execution•Manage expectations•Distribute Information•Manage team•Quality Assurance of deliverables

•Measuring the ongoing project activities•Monitoring the project Scope, cost and other variables•Identify and Address Risks

•Lessons learned•Project transition

Project StagesInitiating Planning Executing Monitoring

& Control Closing

13

Software Development Life Cycle - Software development life cycle models describe phases of the software cycle andthe order in which those phases are executed: Waterfall model V-Shaped model Spiral model Incremental model

Set of general project stages:

Project ManagementSoftware Development

Requirements Design TransitionImplementation Testing

Initiating Planning Executing Monitoring & Control Closing

14

15

Advantages Disadvantages

Simple and easy to use.Easy to manage due to the rigidity of the model – each phase has specific deliverables and a review process.Phases are processed and completed one at a time.Works well for smaller projects where requirements are very well understood.

- Adjusting scope during the life cycle can kill a project- No working software is produced until late during the life cycle.- High amounts of risk and uncertainty.- Poor model for complex and object-oriented projects.- Poor model for long and ongoing projects.- Poor model where requirements are at a moderate to high risk of changing.

SDLC ModelsWaterfall(1 of 4)

16

Advantages

Simple and easy to useEach phase has specific deliverablesHigher chance of success over the waterfall model due to the development of test plans early on during the life cycleWorks well for small projects where requirements are easily understoodDisadvantages

- Very rigid, like the waterfall model- Little flexibility and adjusting scope is difficult and expensive- Software is developed during the implementation phase, so no early prototypes of the software are produced- Model doesn’t provide a clear path for problems found during testing phases

SDLC ModelsV-Shape(2 of 4)

17

Advantages Disadvantages

Generates working software quickly and early during the software life cycleMore flexible – less costly to change scope and requirementsEasier to test and debug during a smaller iterationEasier to manage risk because risky pieces are identified and handled during its iterationEach iteration is an easily managed milestone

- Each phase of an iteration is rigid and do not overlap each other- Problems may arise pertaining to system architecture because notall requirements are gathered up front for the entire software lifecycle.

SDLC ModelsIncremental (3 of 4)

18

Advantages

High amount of risk analysisGood for large and mission-critical projectsSoftware is produced early in the software life cycleDisadvantages

- Can be a costly model to use- Risk analysis requires highly specific expertise- Project’s success is highly dependent on the risk analysis phase- Doesn’t work well for smaller projects

SDLC ModelsSpiral (4 of 4)

19

C.T.Co - Agile SDLC is appliedProject Manager = Scrum Master / Coach

20

SW Projects typically fail when:◦ People begin programming

before they understand the problem

◦ The team has an unrealistic idea about how much work is involved

◦ Defects are injected early but discovered late

◦ Programmers have poor habits – and they don’t feel accountable for their work

◦ Define Failure!!!

Applied Software Project Management [ASPM] (1 of 2)

21

How can we make sure a project to succeed:◦ Make sure all decisions are based on

openly and timely shared information◦ Don’t second-guess your team

members’ expertise◦ Introduce software quality from the

very beginning of the project◦ Don’t impose an artificial hierarchy

on the project team◦ Remember that the fastest way

through the project is to use good engineering practices

◦ Define sucess !!!

Applied Software Project Management [ASPM] (2 of 2)

22

Software Development Life Cycle Models, Raymond Lewallen, 2005, http://codebetter.com/raymondlewallen/2005/07/13/software-development-life-cycle-models/

Applied Software Project Management, Andrew Stellman & Jennifer Greene, 2005, http://www.stellman-greene.com/aspm/content/view/28/33/

Bibliography

23

Questions?

Comments?

Thank You!