Project Management and Planning Flashcards
What is a good management?
Not a buffet. All are required, all are important and all have equal weight.
Effective management does not simply mean telling people what to do, not in software engineering.
Characteristics of good management?
Effective Consistent Respectful Inclusive Honest Transparent
Hierarchy of Human Needs?
Self-Realization Esteem Needs Social Needs Safety Needs Physiological Needs
Self-Realization?
Personal development, achievement, attainment
Esteem Needs?
The need to feel included respected, appreciated, acknowledgement
Social Needs?
The need to be part of social group
Inclusivity
Safety Needs?
Physical and mental safety
Physiological Needs?
Food, sleep
Jelled Teams?
Group of people so strongly knit that the whole greater than the sum of the parts
Probability of success goes up dramatically. The team can become almost unstoppable.
Factors that Influence Teamwork?
Informal Teams
Self-Organizing Teams
Hierarchical Groups
Difference in technical ability is a major challenge
Informal Teams?
Ad-Hoc, formed with a specific goal, tend to decide by consensus
Self-Organizing Teams?
Cross-functional team of people who collectively are responsible for all of the work necessary to produce working.
Essential in SCRUM
Hierarchical Groups?
Top down “instructions”
(or orders if you are in the army)
Rarely works for complex software engineering
Factors that affect communication?
Group Size Group Structure Group Composition Physical Work Environment Communication Channels
Risk Areas?
Project
- Affect the project schedule or resources
Product
- Affect the suitability, quality or performance of the software being developed
Business
- Affect the organization developing or procuring the software
Risk Management Process?
Risk Identification
Risk Analysis
Risk Planning
Risk Monitoring
Risk Identification?
Identifies project, product and business risks
Risk Analysis?
Assesses the risk probability and impact
Risk Monitoring?
Ensures risks are continuously monitored and reassessed
Types of Risks?
Estimation Risks Organizational Risks People Risks Requirement Risks Technology Risks Tools Risks Integration Risks
Risks Probability?
Measures the likehood that the risk will affect the project
Risk Impact?
Measures the possible impact on the project
Risk Planning
Mitigation Strategies
Avoidance Strategies
Minimization Strategies
Contingency Strategies
Avoidance Strategies?
Aims to reduce the probability that the risk will occur
Minimization Strategies?
Aim to reduce the impact of the risk should it materialize
Contingency Strategies?
Describe how the team will proceed should the risk materialize
Risk Monitoring? (Longer Def)
The project must be continuously assess for emerging risks in each risk area: product, project and business
Risk Analysis Tags?
Risk Probability
Risk Impact
Risk Probability Tags?
Very high (Red)
High (Orange)
Medium (Yellow)
Low (Gray)
Risk Impact Tags?
Catastrophic Impact (Red) Serious Impact (Orange) Tolerable Impact (Yellow) Insignificant Impact (Gray)
The development process is planned in advance and documented in a project plan?
Project Plan Structure
Scheduling
Estimation
Project Plan must identify?
Resources Available
Work Breakdown
Development Schedule
Project Plan Document?
Introduction Project Organization Risk Analysis Hardware and Software Resources Work Breakdown Structure Project Schedule Monitoring and Reporting Mechanism
Sprints are?
Time-Boxed Iterations
Timeboxing is essential?
In establishing the work-in-progress (WIP) limit and establish velocity
Forces the team to?
Prioritize features and avoid unnecessary polishing or gold-plating.
Software Pricing Factors?
Contract Uncertainty of Cost Estimate Financial Health Market Volatility
