Software Project Management

Comment

Comment by Etheralking on February 28, 2010 at 2:04am

Hi Everyone,

Let's say that we are working in the Airline Industry, for a carrier owned by the employees. Hold-on, only sounds familiar. The ENV is highly automated from an Engineering perspective. The CERTLAB Team consists of 6 other depts, and maybe 20+ individuals.

The questions:

How do we keep everyone honest about when the activity needing activated should be executed, and a reasonable amount of time of turn-around when the Engineering Activity can be accessed and tested by the CERTLAB Team?

How do we keep everyone on-track with MPP and Engineering Activities in an organization this size?

What do we do as PM/PME to have success in the somewhat "lazy" environment?

(If this client sounds familiar it is known organizational wide there are serious performance related issues, needing immediate testing/resolve due to the impact on the end-user. The result is a failed network and NO ticketing agents can access the network to book customers!)

(I am using VMWare for faster ENV deployment)

(Each engineer only does what their skil set allows)
(Each status meeting everyone kinda shrugs shoulders as to the delay of building activities!)

Comment by Nootan Singh Rajput on May 10, 2009 at 2:39pm

I want to explore deeply in this domain.

Comment by Vara Prasad on May 5, 2009 at 3:21pm

Hi Jay,

I joined in your group. Surely I will contribute in your group.

Regards,
Vara Prasad

Comment by Ritu on October 18, 2008 at 1:49pm

Thanks Jay for providing this group.

Comment by Kiran Kumar on October 13, 2008 at 10:34am

Jay, I joined in your group.

Comment by JAY on October 12, 2008 at 2:00pm

Hi Sridevi!
Yes, you are the first member to join this group.Thanks for joining and request to add any knowledge you have on this topic.
I have displayed the information you required and I have transferred the discussion on SPM in FORUM to here.

Thanks again
______ JAY _____

Comment by JAY on October 12, 2008 at 1:52pm

Hi Uma Mahesh!

The important topics to be covered in Project management are as under:

1. What is S/W PROJECT MANAGEMENT?
2. S/W Project Planning
3. Project Contents and Deliverables
4. Task Analysis
5. Project Resource Planning
6. Risk Analysis and planning
7. Project Oganising and Preparing
---Human resources
---Processes, Methods and Tools
---Goals and Measurements, say costs
8. S/W Project Monitoring
---Collecting Project Information
----Analysis and Evaluation of Info
----Presenting and Communicating Data
9.Adustments and Actions
---Planned and Unplanned
---Release M Council
10. Some Skills
----Team
----Change Control
---Task Scheduling
---effort Estimation
--- Audit concepts
---Estimating

________ JAY _______
Share

Comment by JAY on October 12, 2008 at 1:48pm

A BRIEF DESCRIPTION ABOUT SOFTWARE PROJECT MANAGEMENT
( SPM ) :

A simple,short. well defined S/W project usually requires services of one competent and disciplined S/W Engineer So there is no need for sophisticated Project management. In a current scinario, the number of S/W projects
that are large, complex, and ill-defined are on the rise. Hence, the importance and necessity of applying Project Management skills are also growing.
Without the management,such projects future is nowhere and we then hear the horror stories of failures of large projects.For example,Disastrous London Ambulance Service Project which has to be scrapped after six years for the lack of S/W Project Management and millions of Pounds spent stood as loss.

SPM:

A software project may not be clearly defined, in that there is no clearly accepted standard set of deliverables to be produced at the end of software project.

Software Project Management involves the application of good management practices to the development and support of software.

By necessity it is a multidisciplinary subject.

SPM ( Software Project Management ) is concerned with ensuring that, for a S/W project, the most appropriate process and methodologies are chosen, the desired internal product structure is attained, and the external product properties are achieved.
It must be viewed as applying sufficient resources to ensure that S/W artifacts
( S/W artifact is a unit of material, in the form of a document, presentation,or code, that is developed as a part of, or as a contribution to, the final solutuion to theusers.) evolve in a manner such that-
** They meet all the product functional and other requirements
** They are developed within the cost constraints
** They are developedwithin the alloted schedule.

Satisfying the project requirements, budgetary, and schedule constraints is THE ESSENCE OF PROJECT MANAGEMENT.Because S/W projects heavily depend on the availability on human resources,SPM also requires people management.
Software Engineering, which begins with a development and support processes and then appliesmanagement to that process. As opposed to s/w engineering SPM starts with management and then applies S/W Engineering's domain-specific knowledge, such as requirements solicitationmethod or s/w measurement method, at various stages along the way.
The phases of SPM are called as POMA :
* P-Planning
* O-Organising
* M-Monitoring
* A-Adjusting
POMA models the S/W Management Life Cycle ( SMLC ) much as a waterfall s/w process models the S/W Development Life Cycle( SDLC ).

POMA activies are not essentially sequential and they may overlap.
All managers, at different levels are involved in the above four activities of POMA. The difference is merely the degree to which they are involved.

_______ JAY ________

Comment by Sridevi on October 11, 2008 at 1:53pm

Jay,
I am the first person joining in your group.

Actually QT Team people don't approve groups, you are lucky. Long back i created one group called HYDTesters. But they don't approve my group.

Anyway nice group Jay. You can add more information in this group i mean what is this group it is?

Thanks

~Sridevi