Project Types, Structure & Cycle-2
Project Types, Structure & Cycle-2
Project Types, Structure & Cycle-2
Intangible Products
A tangible project is one in which the primary value is in
its intellectual property(content)
Class – I
Class – II
Class – III
Class - IV
Class – I Class – II Class – III Class - IV
More than 18 Between 9 to 18 Between 3 to 9 3 Months or
Time Span
Months Months Months less
Level of Risk High Medium Low Very Low
A B
Project Members
Basis of organization:
Complicated information and control flow
across hierarchical boundaries
Chief Programmer
Assistant
Chief Programmer
Junior Programmer
Analyst
Tester Programmer
Designer Librarian
Project
Leader
Coaches
A B Team
Members
Basis of organization:
Nonlinear information flow across dynamically formed units
Reporting association:
Used for reporting status information
Decision association
Used for propagating decisions
Communication association
Used for exchanging information needed for decisions
(e.g., requirements, design models, issues).
Hierarchical structures
“Reports”,“Decides” and “Communicates-With” all
mapped on the same association
Do not work well with iterative and incremental software
development process
Manager is not necessarily always right
Project-based structures
“Reports”, “Decides” and “Communicates-With”are
different associations
Cut down on bureaucracy reduces development time
Decisions are expected to be made at each level
Hard to manage
Projects with high degree of certainty, stability,
uniformity and repetition.
Requires little communication
Role definitions are clear
When?
The more people on the project, the more need for a
formal structure
Customer might insist that the test team be independent
from the design team
Project manager insists on a previously successful
structure
Project with degree of uncertainty
Open communication needed among members
Roles are defined on project basis
When?
Requirements change during development
New technology develops during project
Initiate the project
Identify the Project Manager
Develop the Project Charter
Conduct a Feasibility Study
Define Planning Phase
Sign off on the Project Charter
Organize and staff the project
Develop a Project Plan
Sign off on the Project Plan
Execute the Project Plan
Manage the Project Plan
Implement the project’s results
Sign off on project’s completion
Document the lessons learned during the
project
After-implementation review
Provide performance feedback
Close-out contracts
Complete administrative close-out
Deliver project completion report