Test 2 Flashcards
(24 cards)
Outline the process of creating a project schedule
- Create WBS
- Determine project requirements
- Physical resources, training needs, support documentation, infrastructure changes, compliance requirements, etc.
- Create task network diagram
- Determine task time and resource assignments
- Assign tasks
- Determine project milestones
- Create project schedule
Create a WBS
- Work breakdown, not task breakdown
- The work in WBS are deliverables (work products) not tasks. A work package is a deliverable at the lowest level of the WBS. Work packages are decomposed into tasks in the project schedule.
- 3 levels
- Aim for at least 3 levels where the highest level is the project itself. There may be more or fewer levels depending on the size and complexity of the project
- 100% rule
- Every level of decomposition must make up 100% of the parent level
- Mutually exclusive
- All elements at a particular level in a WBS must be mutually exclusive. There must be no overlap in either their deliverables or their work.
- Tic-Tac-Toe Project
- Executable
- Requirements
- Design
- Source Code
- System Test Cases
- Release Packages
- Alpha
- Beta
- Final
- User Guide
- Online version
- Offline version
- Executable
“Functional Requirements”
- Start game
- X plays
- O plays
- X wins
- O wins
- A draw
- End game
- Start over
Break down each deliverable into tasks and identify the prerequisites for each task
Deliverable
Tasks
Immediate Prerequisite Tasks
Serviced lawnmower
S1 – Check and sharpen blades
None
S2 – Check oil
S1
S3 – Check fuel
S2
Mowed grass and leaves
M1 – Clear obstructions
None
M2 – Start mower
M1, S3
M3 – Mow grass and leaves
M2
Sharpened pruners
SP1 – Get small pruner
None
SP2 – Get large pruner
None
SP3 – Sharpen pruners
SP1, SP2
Branch Pile
B1 – Prune trees
SP3
B2 – Move branches into a pile
B1
Sharpened Trimmer
ST1 – Get trimmer
None
ST2 – Sharpen trimmer
ST1
Brush Pile
BP1 – Trim the hedge
ST2
BP2 – Move trimmings to a pile
BP1
Draw a task network diagram
Using the following task analysis
Deliverable
Tasks
Immediate Prerequisite Tasks
Serviced lawnmower
S1 – Check and sharpen blades
None
S2 – Check oil
S1
S3 – Check fuel
S2
Mowed grass and leaves
M1 – Clear obstructions
None
M2 – Start mower
M1, S3
M3 – Mow grass and leaves
M2
Sharpened pruners
SP1 – Get small pruner
None
SP2 – Get large pruner
None
SP3 – Sharpen pruners
SP1, SP2
Branch Pile
B1 – Prune trees
SP3
B2 – Move branches into a pile
B1
Sharpened Trimmer
ST1 – Get trimmer
None
ST2 – Sharpen trimmer
ST1
Brush Pile
BP1 – Trim the hedge
ST2
BP2 – Move trimmings to a pile
BP1
Create a simple project schedule
Using the following task assignment table
Deliverable
Tasks
Prerequisite Task
Time Estimates
Resources Needed
Assigned to
Serviced lawnmower
S1 – Check and sharpen blades
None
10 minutes
Mower blades, Sharpening file
Jeff
S2 – Check oil
S1
2 minutes
Mower, Oil
Jeff
S3 – Check fuel
S2
2 minutes
Mower, Fuel
Jeff
Mowed grass and leaves
M1 – Clear obstructions
None
10 minutes
None
Dylan
M2 – Start mower
M1, S3
1 minute
Mower
Dylan
M3 – Mow grass and leaves
M2
90 minutes
Mower
Dylan
Sharpened pruners
SP1 – Get small pruner
None
1 minute
None
Darien
SP2 – Get large pruner
None
1 minute
None
Darien
SP3 – Sharpen pruners
SP1, SP2
5 minutes
Small and large pruner
Darien
Branch Pile
B1 – Prune trees
SP3
30 minutes
Small and large pruner
Darien
B2 – Move branches into a pile
B1
10 minutes
None
Darien
Sharpened Trimmer
ST1 – Get trimmer
None
1 minute
None
Evelyn
ST2 – Sharpen trimmer
ST1
5 minutes
Trimmer, Sharpening file
Evelyn
Brush Pile
BP1 – Trim the hedge
ST2
10 minutes
Trimmer
Evelyn
BP2 – Move trimmings to a pile
BP1
10 minutes
None
Evelyn
~188 minutes
Explain what a software development process is
An ordered set of defined activities that describe the definition of requirements, designing, coding, testing, and release for a software artifact. A process may contain some sub-processes, such as the requirements sub-process within the software development process.
Explain what a software methodology is
A set of rules and principles defined to achieve a specific goal and to accomplish a specific task in the development or support of software.
List the activities to plan the requirements process
- Determine whether there is a need for a requirements process. If there is a need, continue to step 2. Otherwise, consider the next type of process planning, which is design process planning.
- Plan for the tasks or activities to be included and defined as part of the requirements process, outlining the order and the sequencing of the activities
- Requirements elicitation
- Requirements analysis
- Requirements specification
- Requirements validation
- Requirements sign-off
- Requirements change and impact management
- For each of the chosen activities, ensure that either a methodology already exists or the plan includes the definition of methodologies
- Include education on the process and the methodology, if necessary, as part of the plan
List the activities to plan the design process
- Architectural design
- Application-specific high-level design
- Application-specific low-level design
- Design analysis
- Design review
- Design change and impact management
List the activities to plan the implementation process
- Programming standards definition
- User documentation, help text, and other information standards definition
- Software code acquisition, procurement, and reuse management
- Program documentation
- Program and information review
- Unit testing
- Integration testing
List the activities to plan the testing process
- Test planning
- Test scenario development
- Test case and test script development
- Test scenario and test case review
- Test result tracking and analysis
- Test execution, problem reporting, resolution, and fix-integration management
List the activities to plan the product release process
- Integration, packaging, and installation
- Product order, release, and shipment management
Identify other process planning considerations
- Configuration management
- Outsourcing and procurement management
- Quality assurance
- Project change management
- Project reporting and escalation process
Outline the process of recruiting and hiring
- Proceeds in two stages
- Building a skills matrix based on the various tasks involved
- Number of people required for each category
- Using the skills matrix to develop a hiring plan
- Building a skills matrix based on the various tasks involved
- The initial offer package should be designed to be competitive in the marketplace, yet should be positioned in such a manner that the compensation can increase as the employee grows in experience after having been hired.
Outline the elements of a hiring plan
- Project managers often need to revisit the task and schedule plans after studying the resources plan.
- The lead time needed for recruiting, training, and team assimilation may force additional time to the schedule for these types of tasks, which may not have been considered during the first pass at planning and the WBS.
- It is possible that a person with some special skill, in spite of planned recruiting lead-time, may not be found in time.
- The project manager may need to revisit the project plan and get some relief in terms of schedule, functional content, or staged releases.
- The people hiring plan matrix can be turned over to the company’s human resources department or to a recruiting company as soon as it is established.
- The matrix should be accompanied by a skills description, thereby ensuring that the right people will be brought on board.
- From the people hiring matrix and the skills description, a more comprehensive recruiting plan may be created.
Outline the elements of a recruiting plan
- A recruiting plan will focus on the following items: job descriptions, job titles, number of openings to be filled, priorities in hiring, compensation and benefits packages, interviewing process and interviewing managers, internal and external avenues to solicit candidates, amount of internal hiring bonuses, range of acceptable recruiter fees, and hiring timing.
- The recruiting plan is described in another matrix that includes all the mentioned items listed by each open position; it should be developed by the personnel department and reviewed with the project management team. In fact, the software project managers may view personnel hiring as a mini-project within the larger project.
Create a simple resource matrix
Project Phases
Requirements Processing
Design
Implementation
Testing
Product Release
Support
Methodologies
Elicitation
Analysis
Specification
Validation
OO Design Analysis
MVC
Unit Testing
Integration Testing
Continuous Integration
System Testing
Acceptance Testing
Continuous Deployment
User call management
Specific tools and equipment
UML Modeling Tool
Requirements management tool
UML Modeling Tool
C#, JavaScript
Visual Studio
NUnit
Acceptance/System Testing tools
Continuous Deployment Tool
Support help desk
Specific human resources
4
2
6
4
2
2
General Process Model
Project Management
Iterative and Incremental Process
General Tools
Project Management Tools
Kanban Board
Software Repository
General support human resources
1 Project manager
1 Quality assurance manager
1 System administrator
Hardware and operating environment
10 computers (4GB RAM, 4TB drives), Windows OS, Chrome
1 Development Server
DBMS
Define risk
A risk is a problem that has a greater than 0% but less than 100% probability of occurrence. A problem is an event that has a negative value associated with it. If a risk is realized, it will have negative consequences. All risks need to be managed.
Outline the process of managing risks
- Risk planning
- Identifying risks
- Prioritizing risks
- Analyzing mitigation alternatives
- Risk mitigation set-up
- Allocating resources
- Setting up a mechanism
- Risk control
- Tracking risk status
- Activating mitigation steps and making adjustments
Outline how to create a list of project tasks
- List the characteristics of the product that may not be well defined
- Create a list of unclear items for each deliverable. These items form the initial list of potential product-related risks.
- List all unresolved issues for the tasks that will be performed in conjunction with the software project.
- Ask if the development process is defined, documented, and practiced. If not, the process may be a risk as it represents an untested element for the team.
- Identify all of the untested elements to create a list of the risks associated with the project’s tasks, processes, and methodologies.
- Idenfity risks associated with the management of resources
- Consider the hardware and software systems required for the project. The associated risk may simply be the capacity or amount of these resources.
- Consider the tools. The risk may be related to the underlying technology or the quality of the acquired tool. Another possible risk may be the timeliness of the availability of the tool.
- Identify risks associated with human resources. There are risks associated with obtaining skilled people in a timely manner. There are risks with the team not cooperating with each other. There are risks of losing skilled people.
Explain different ways to prioritize risks
- Prioritization by recovery cost
- Recovery cost is the cost in terms of effort or financial expense to solve a problem should a risk materialize
- The categories for recovery cost need not be exact but identified with high, medium, and low. The organization can then decide what these categories mean.
- Prioritization by risk value
- Risk value is a recovery cost that is influenced and modified by another criterion or set of criteria. The probability of the risk turning into a problem is such an influencing factor, and when such a factor is taken into account in modifying the recovery cost, the result is the risk value.
- More complex and, as such, poses its own set of risks. It can be made more effective if historical project data is available and can be used.
- Once the risk items are prioritized, the software project managers may decide to consider all of them or just to focus attention on some of the risk items, such as the top 5 risks.
Explain risk mitigation
Risk mitigation is the activity that may reduce, minimize, or totally avoid a risk.
Explain how to choose a mitigation option
- Cost of mitigation
- Estimate the cost to mitigate each risk item and then choose the one with the lowest cost.
- Probability of success
- Each alternative will have an estimated probability of success. The reverse of this value (probability of failure) can be used to calculate the mitigation value cost.
- Ease of mitigation
- Estimate how easy it would be to implement the alternative and choose the easiest one.
Explain risk removal
Each risk item should be given a date by which the risk is supposed to be eliminated. A risk item may be removed from the list after the successful application of the risk mitigation alternative or a change in some other dependency factor.
