Slide Deck 1 Flashcards
(34 cards)
What does management allow a company to do?
Understand, Plan, Measure, and Control
What are the goals of software management?
To finish the project on time, on budget, feature-complete , and with high quality
Project management is the ___ of project activities to achieve project ___
Planning, Scheduling, and Controlling
Objectives
What is the capability maturity model?
Ranks company’s software in terms of their capability and their maturity.
2 benefits:
1. find problems and fix them
2. find things that work and spread them
What are some software development processes?
Waterfall model, Incremental Model, Rapid Prototyping, Iterative & Incremental, and
eXtreme Programming
What is the waterfall model?
Traditional approach, Requirements -> Design - > Development -> Testing -> Maintenance
Good for things that have been done before
You don’t have any value until the end, you don’t test until the end, and you don’t get stakeholder approvals until it’s too late
What is the Incremental Life Cycle?
Create an initial build, then continue to test successive builds until the product has been finished.
What is the Rapid Prototyping Life Cycle?
Create an initial prototype at the beginning that is more susceptible to realistic inputs about the design, but the requirements phase is dragged out to be longer
What is the Iterative & Incremental Process?
Architecture-first approach, that leads to component-based development with proper change management and round-trip engineering.
What is eXtreme Programming?
Design as you go, big emphasis on unit and functional testing, everyone owns the code and the clients are closely involved.
What differs planning from estimating from scheduling?
Planning involves identifying activities and has no start or end date
Estimating is about finding out the size and duration of the activities
Scheduling regards the specific start and end dates, relationships and resources
Planning is a ___ step program
12
What are the 4 steps in scheduling?
- Identify what needs to be done - create WBS
- Identify how much (size) is required
- Identify the dependency between tasks
- Estimate total duration of the work to be done
What is a Work Breakdown Structure?
Hierarchical list of work activities needed to complete the project; a description of the work to be performed broken down into its key components, down to the lowest level.
Divide and conquer mentality
Identifies teams with the necessary skills easily for these tasks
What should you avoid with Work Breakdown Structures?
- too much detail and granularity
- dont over plan with too much detail so that you cannot manage it (i.e. dont break down a 2 week “design the UI” work into “data
element identification”, “data flow diagram creation”, and “customer
review”. - Stop when their is sufficient information for the people that are going to be doing the task
- but dont be too general either (i.e. 8 week design UI )
What is a milestone? And when are milestones in I&I and XP?
A milestone is a significant event usually associated with some intermediate deliverable. If there are not enough milestones, progress hard to track and if there are too many it could slow down the project
In I&I, milestones are at the end of each iteration
In XP, milestones are every 1-3 weeks
What is a work package?
Lowest identifiable activities to be completed. It contains description of the work, staffing req., names of those responsible for completion, schedule, budget, and acceptance criteria
What is an activity? task? in WBS
Activities are the smallest component of WBS, usually contains many tasks
Tasks are the lowest level of effort and can be completed by one individual.
Compare Top-Down and Bottom-Up WBS
Top down is designed to increase in detail as you go down, it is quick and can be done once the requirements are understood but it may lack important details specific to the project that have never occurred in earlier projects
Bottom-Up is designed to start at the lowest level tasks and aggregate into summaries and higher levels. It can be time consuming and needs more requirements to complete but it is very detailed which is good.
What is Analogy?
Basing the WBS off a previous project that is similar in nature, like a template.
Analogy can be used for estimation purposes as well
It is good since it is based off actual experience but if there is no similar project than it fails.
What are the 8 reasons for late software delivery?
- unrealistic deadline from someone outside the engineering group
- changing cx requirements not reflected in schedule changes
- underestimate the amount of effort and resources needed
- risks that were not considered upon inception
- unforeseen technical difficulties
- unforeseen human difficulties
- miscommunication among staff members
- failure to recognize a failing project and not correcting it in time
__% of projects are delivered within budget and on schedule
10
__% of projects never finish
25
The 12 step planning process is:
- Set Goal and Scope
- Select Lifecycle
- Set team form
- Start team selection
- Determine risks
- Create WBS
- Identify tasks
- Estimate size
- Estimate effort
- Identify task
- Assign resources
- Schedule work
