Project planning and risk management Flashcards
What can we do to physically measure the quality of code?
- Lines of code
- Fog index (readability of code)
- Number of reported faults after delivery
- Number of person days for coding
Define software risk
Potential hazards in software system which lead to security and privacy breeches
Define project risk
Likelihood of events or circumstances that affect successful project execution
How do we reduce software risk?
- Conduct functional risk analysis as early as possible
- Create some clear “shall nots”
- Ongoing risk monitoring
What are shall-not requirements?
What our system definately SHOULD NOT do
What are the two types of shall-not requirement?
Functional shall-not requirements
Non-functional shall-not requirements
Explain functional shall-not requirements?
What should not happen
What should happen for non-correct usage or errors
Explain non functional shall-not requirements
Define the reliability and availability of software
Can be measured by:
- availability
- rate of failures
- recovery time
What could be some security concerns when developing software?
- Credit card data
- Customer patients data
- Proprietary algorithms
What are 4 project management concerns?
- Deliver the software to customer on schedule
- Keep overall costs within budgets
- Deliver software that meets the customer expectations
- Maintain a happy and well functioning dev team
What is the role of the project manager in terms of risk?
- Considering and preparing for possible problems in the future so the project goes smoothly
- All risks should be listed and a strategy considered
What are some risk types?
Technology
People
Organisational
Tools
Requirements
Estimations
Explain risk prioritisation
Rank risks by the probability of them (low, moderate, high) and their effect (insignificant, tolerable, catastrophic)
What are 3 different strategies to manage project risk
Mitigate, Avoid or handle (contingency)
Avoidance is the best strategy
What are the four different types of traditional planning diagrams?
PERT
Critical path method
Gantt chart
Staff allocation charts
What is a PERT chart?
Diagram for tasks and dependencies with bubbles and arrows.
Can be simple or more detailed (annotated with optimistic time, pessimistic time and most likely times)
What is a critical path method?
Take a PERT chart and identify all the paths through it, identifying the length of time it takes for each path
- Longest path is the critical path
This is known as the bottleneck route, but can be complicated in large projects (use software to derive this)
What is a GANTT chart?
Adding time to tasks/dependencies, kinda looks like a bar chart
- Milestones to review progress
- Plan is an estimate so look for slippage (ignoring small, if big replan)
What is staff allocation charts?
Who can do the tasks/dependencies
What is agile planning?
Fixed number of people in team
Setting deadlines
- Output is always working software
Estimate what work can be done in between deadlines
- Pick a user story and assign points for how hard they are
- Productivity is then daily points score
What are two approaches to estimating project budgets?
Analyse the work and estimate developer time
- Done by management experience or algorithmic cost modelling
Analyse developer time and define how much work to do
- Scrum methodology, agree on num of sprints and cost revolves around this. Expanding a project = buy more sprints
What is the disadvantage of algorithmic cost modelling?
- Often complex and people are nervous of using them
- Typically inaccurate
What factors affect project price?
- Market opportunity
- Cost estimate uncertainty
- Contractual terms
- Requirements volatility
- Financial health
Generally, how do we estimate the cost for a project?
Break down and plan order of work
- estimate time and effort accounting for risk
Cost will be at least this
- Sales people figure out profit
Management use experience to guide cost
Give an example of how to use each type of risk strategy.
Avoidance
Handling risk
Mitigating risk
Give an example of avoiding a risk
Follow good coding practices to prevent vulnerabilities being introduced
Give an example of handling risk
Code reviews to address problems in code
Give an example of mitigating risk
Paired programming and reorganising team to ensure that staff illness doesn’t affect development
