Software Project planning 1 Flashcards
What is a framework for Software Project management?
A framework is something that is reusable that can help us safe time and reduce complexity of a project. ensuring everyone is on the same page
Qualities of a framework
Adaptable and flexible to project needs
reduce risks, stay organised, increasing chance of success
Stepwise
breaking down projects in steps
Prince2
Project in controlled environment
Structured approach for frameworks
list the main steps involved with planning
suggest best practices on carrying out these steps
indicate step order iterations through sequences of steps
What makes a project successful
Everyone Agrees on Project goals
Developed clearly assigned responsibilities ad accountabilities.
Manage project scope effectively, keep close watch on scope so it stays on track
Consistent communication
Management support
StepWise
Answers the question of what do I do now?
Useful for small and Large projects
Best suited for projects that require tailored planning.
Inhouse vs Out sourcing
Inhouse is done in the organisation and outsourcing is external, third party services
Factors to consider in house vs outsourcing
Criticalirty of task
budget
desired control you want to have.
functions crucial for success, we will keep in house
Functions that are less strategic, we use outsourcing to increase efficency
off the shelf
urgent and generic
new internal payrll offic eto be setup
Software Addons will be needed.
Custom developed
Unique closeknit to the organisation
mat take longer but the long termbenefits will pay off
0 Selecting a Project
Potential Impact of the project
Resource requirements for the project
strategic valley, Does he project mov in the same direction as the organisation?
1 Identifying Project Objectives
Identify objectives and measures of effectiveness
– how do we know if we have succeeded?
– From Unit 1: objectives must be SMART:
– Specific, Measurable, Achievable, Relevant, Time-constrained
Establish a project authority
– who is the boss?
Identify all stakeholders in the project and their interests
– who will be affected/involved in the project?
Modify objectives in the light of stakeholder analysis
– do we need to do things to win over stakeholders?
Establish methods of communication with all parties
– how do we keep in contact?
2 Identify Project infrastructure
Establish link between project and any strategic plan
– why did they want the project? Identify installation standards and procedures
– what standards do we have to follow?
Identify project team organisation
– where do I fit in?
3 Analyse Project Characteristics
Distinguish project as objective based or Product based
Analyse other project Characteristics
Identify potential risks
–what can go wrong an what can we do to stop it
consider user requirements for implementation
development methodology-Agile-Waterfall-incremental
review overall resource estimates
4 Identify products and activities
Identify and describe project products
–What do we have to produce in terms of both customer deliverables and intermediate artefacts
-PBS (product breakdown structure)
Document Generic Product flows
– some products need one or several other products to exist before they are created
–PFD product flow diagram- to represent these relationships
Recognise Product Instances
–PBS and PFD will already have generic products, Specific instances can be identified.
Produce Ideal Activity network
–Identify the activities needed to create each product in the PFD
–draw Activity network-Activities order and flow
Add Checkpoints and milestones
–to ensure products are compatible and ca proceed without risk
Modules
Components, software consists of components or features.
5 estimate efforts for each activity
Carry out bottom up estimates
– distinguish between effort and elapsed time
Revise Plan to create controllable activities
– break up long activities into smaller ones that are easier to controll
6 Identify activity risks
Identify and Quantify risks for activities
– estimate damage f risk occurs
Plan risk reduction and contigency plan
-reduce likely hood of risk
reduce impact
7 Allocate resources
Identify allocate resources to activities
–Record staf type needed
-Identify staff available
reviseplans and estimates to reflect research constraints
- staff not being available until later date
8 Review and plublicise plan
Review quality aspects of the projet plan,
–ensure quality criteriaare defined for all activities
Document plan and obtain agreement
9 Execute plan & 10 lower level planning
Detailed plans are required and feasible for the current activities
detailed plan for later project stages are often not possible
Estimates effort, Start dates etc are associated with confidence intervals that are too large
PRINCE 2
