Intro to Software Project Management Test 2

0.0(0)
studied byStudied by 0 people
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
Card Sorting

1/127

encourage image

There's no tags or description

Looks like no tags are added yet.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

128 Terms

1
New cards

What does Release Planning Do

Helps set expectations for stakeholders and ensures a steady flow of value to the customers

2
New cards

Increment Planning Sessions

Define increment goals, solidify estimates, and identify external dependencies.

3
New cards

How is Total Project Capacity Estimated

based on resources available for each team

4
New cards

How do you Calculate Capacity for Increment by product

X points for Product A, Y points for Product B, Z points for Product C, Total Points = X + Y + Z

5
New cards

How do you Calculate Total Capacity for Increment

(points_per_sprint x N sprints) for each Product

6
New cards

What is on a High-Level Schedule

Requirements submitted and finalized by Due Dates, Conduct quarterly releases with maintenance releases in between (sprints), and Major Phases and SETR events

7
New cards

What is the main purpose of a high-level schedule?

To communicate to customer, stakeholder and team about the key milestones of the project

8
New cards

What is a Work Breakdown Structure (WBS)?

A hierarchical decomposition of a project into smaller, more manageable components or tasks. Each level of the WBS provides a more detailed breakdown, from major project phases to individual tasks. Basically a table of contents

9
New cards

What is the purpose of a WBS

It organizes and defines the total scope of the project by breakingdown the deliverables and work into smaller elements, oftenrepresented as a tree structure

10
New cards

What does the Project Time Management include

the processes required to accomplish timely completion of the project

11
New cards

What are the 6 Scheduling Basics

Activity Definition, Activity Sequencing, Activity Resource Estimating, Activity Duration Estimating, Schedule Development, Schedule Control

12
New cards

What are Work Packages in the Activity Definition Process

planned into smaller components call schedule activities to provide a basis for estimating, scheduling, executing, and monitoring and controlling the project work

13
New cards

What are the 3 types of dependencies in diagramming

Mandatory, Discretionary, and External

14
New cards

What are the 6 benefits of Network Diagramming

Show interdependencies, Show workflow, Aid in effective planning, organizing and controlling, Compress the schedule, Show program progress, Help justify time estimate

15
New cards

What are the 4 Artifacts involved in creating a project schedule in Agile

Product Backlog, Sprint Backlog, Burndown Charts, and Release Plan

16
New cards

How are the 4 steps to create a project schedule

Define project start and end dates, Add tasks based on our Agile Product Backlog, Set task durations and dependencies, Assign team members to each task

17
New cards

How do you Monitor Progress in MS Project

Update task status regularly, Review Gantt charts and reports to assess progress, Identify and resolve potential delays, Adapt the plan if required based on feedback and changes

18
New cards

Release Planning

deciding which items from the Product Backlog will be included in a release

19
New cards

What are the Increment Planning Objectives by Session

Requirements elicitation, prioritization, and product management executed in close collaboration with stakeholders.

20
New cards

What are the Primary Goal of an Increment Functional Review

Ensures that product backlog items are clearly identified and the release functional baseline is established.

21
New cards

What does an Increment Functional Review act as?

acts as the SRR for each increment and acts as the PDR for the upcoming increment release to ensure the system proceeding into development can meet requirements within the iron triangle

22
New cards

What is a WBS a Blueprint for?

laying out a project schedule

23
New cards

What is the Purpose of the Activity Definition Process

identify the deliverables at the lowest level in the Work Breakdown Structure, which is call theWork Package

24
New cards

What are MS Project Dependencies

dependencies between activities define the sequence and relationships between different tasks or activities in a project

25
New cards

What is the purpose of MS Project Dependencies

help determine the order in which tasks should be executed and how they affect one another

26
New cards

What are the 4 Main Types of MS Project Dependencies

finish-to-start, start-to-finish, start-to-start, finish-to-finish

27
New cards

What is Finish-To-Start

the successor activity cannot start until the predecessor activity is completed

<p>the successor activity cannot start until the predecessor activity is completed</p>
28
New cards

What is Start-To-Start

the successor activity cannot start until the predecessor activity begins

<p>the successor activity cannot start until the predecessor activity begins</p>
29
New cards

What is Finish-To-Finish

the successor activity cannot finish until the predecessor activity is completed

<p>the successor activity cannot finish until the predecessor activity is completed</p>
30
New cards

What is Start-To-Finish

the successor activity cannot finish until the predecessor activity begins

<p>the successor activity cannot finish until the predecessor activity begins</p>
31
New cards

What is Arrow Diagraming Method (ADM)

Task to Task when Activity A happens

<p>Task to Task when Activity A happens</p>
32
New cards

What is Activity on Arrow (AOA) Method

Activity A goes to Activity B

<p>Activity A goes to Activity B</p>
33
New cards

What is MS Project

Project Management Tool that helps with planning, scheduling, resource allocation, and progress tracking

34
New cards

How do you represent Agile Sprints in MS Project

Set up the first Sprint phase, Add User Story tasks to the Sprint, Assign resources to each User Story, Set the duration for each User Story task

35
New cards

Primary Goals of Release Planning

Establish what is to done during release, Set Primary Plan, Set Stretch Plan, and Identify Dependencies and Risks

36
New cards

What is the goal of Increment Planning Sessions

to mitigate risks and present increment plans to stakeholders for review.

37
New cards

What is an Increment Functional Review

review to be conducted when all increment planning sessions are completed

38
New cards

Why Do we need a Stretch Plan?

In case we get blocked for some stories, In case dependencies dont meet agreed upon need dates, or In case our Velocity is running faster than planned

39
New cards

What is Activity Sequencing

identifying and documenting the logical relationships among schedule activities

<p>identifying and documenting the logical relationships among schedule activities</p>
40
New cards

What is a Sprint Backlog

a subset of the Product Backlog items selected for a specific sprint. It contains the tasks necessary to complete the selected items and is created during the Sprint Planning meeting.

41
New cards

What does Sprint Planning in JIRA Involve

assigning user stories to specific sprints based on their priority and the team's capacity

42
New cards

What does JIRA allow you to do

create and manage sprints, which are time-bound iterations of work

43
New cards

What happens during Sprint Planning

user stories are selected from the backlog and added to the sprint based on their priority and estimated effort

44
New cards

What are some of the artifacts needed for a Sprint Plan brief?

Schedule Overview, Dashboard Status, Sprint Objectives with target velocity, Demo Plans

45
New cards

What is the purpose of Agile Project Metrics

help measure progress, identify bottlenecks, and track the team's performance

46
New cards

What are some common agile project metrics

Velocity and Burn-Down Chart

47
New cards

What is a Cycle Time

Measures the time it takes to complete a user story from start

48
New cards

What is a Burn-Down Chart

tracks the progress of the team's work during a sprint

49
New cards

Role of PM in Design

Overseeing the design process, Managing the development of design documents, and Collaborate with the Development Team

50
New cards

Role of PM in Implementation/Development

Track progress, Facilitate Communication, Address Roadblocks and Risks

51
New cards

What is Design Thinking

a problem-solving approach that emphasizes empathy, creativity, and iterative prototyping to address complex problems

52
New cards

What are the Phases of Design Thinking

Empathize, Define, Ideate, Prototype, and Test & Iterate

53
New cards

What is the Empathize Phase in Design Thinking

Understanding the needs, wants, and challenges of end-users through observation, interviews, and research (e.g. creating empathy maps)

54
New cards

What are the common artifacts of the Empathize Phase

User Personas, User Stories, and Business Process Modeling

55
New cards

What is the Define Phase in Design Thinking

Synthesizing user research findings to define the problem statement and identifying goals (e.g. Creating Journey Maps and Defining design principles)

56
New cards

What are the common artifacts of the Define Phase

Problem Statement, User Needs, and User Goals

57
New cards

What is the Ideate Phase in Design Thinking

generating a wide range of ideas to address the defined problem statement (e.g. Mind mapping, Sketching, and Crazy 8s technique)

58
New cards

What are the common artifacts of the Ideate Phase

Brainstorming, Ideation techniques, Divergent thinking, and User Goals

59
New cards

What is the Prototype Phase in Design Thinking

creating low-fidelity representations of the ideas to quickly test and gather feedback (e.g. Creating a clickable prototype)

60
New cards

What are the common artifacts of the Prototype Phase

Paper prototypes, Wireframe diagrams, and Mock-ups

61
New cards

What is the Test & Iterate Phase in Design Thinking

gathering feedback from users on the prototypes to refine and improve the design (e.g. Conducting usability tests and A/B Testing)

62
New cards

What are the common artifacts of the Test & Iterate Phase

Usability Testing, Feedback collection, and Iteration

63
New cards

What is A/B Testing

Two different versions are tested with two groups to see which performs better based on metrics

64
New cards

How to Apply Design Thinking to SW Project Management?

Integrate it into the SDLC, Use it to understand user needs and align project goals, Apply iterative prototyping and user feedback

65
New cards

What is Crazy 8 Technique

fast-sketching exercise that challenges people to sketch 8 distinct ideas in eight minutes

66
New cards

What are Agile Design Practices

design approaches that prioritizecollaboration, adaptability, user-centered design and iterative development

67
New cards

What are the 3 Agile Design Practices

Collaborative, User-Centered, and Iterative and Incremental

68
New cards

What are Working Groups in Agile Design Practices

time-boxed series of collaboration meetings to define functionality, user experience, and content that empowers successful completion of project

69
New cards

What is a Special Topic Working Group

Chartered by a Process Owner to enable Self-service feature execution of workflows, members gather requirements, determine a suitable Minimum Viable Product, and create demand signals for required data and system interfaces

70
New cards

What are Technical Working Groups

members identify technical enablers and supporting systems to accelerate capability development

71
New cards

What are Content Working Groups

Members identify content owners, create production-ready content, and propose guidelines and governance to ensure content remains "evergreen"

72
New cards

What are the 3 Working Groups

Special, Technical, and Content

73
New cards

What elements does Agile use

user stories, sprints, and regular sprint reviews and retrospectives to drive continuous improvement

74
New cards

What is a Product Backlog

ordered list of tasks, features, and bugs that the team maintains project.

75
New cards

What is Increment planning

The process used to identify the scope of tasks to be completedduring the Increment

76
New cards

What is Sprint Planning

planning session to select what work will be done in the sprint

77
New cards

Daily Scrum Meeting

very short team meeting to communicate what was done the day before, what is planned to be done during the day, and any issues that may impede work

78
New cards

Clean Code and Refactoring

Writing simple, maintainable code that adheres to standards like SOLID principles

79
New cards

Test-Driven Development (TDD)

tests are written before the actual code, ensuring that the code is aligned with expected behavior

80
New cards

Test-Driven Development Process

Write a failing test case that defines desired functionality, write code to pass the test case, refactor code to improve quality

81
New cards

Benefits of Test-Driven Development

Clear requirements, safer refactoring, higher code quality, and faster debugging

82
New cards

Pair Programming

collaborative coding approach where two developers work together, switching roles as driver and navigator to enhance code quality and reduce errors

83
New cards

What are the 3 Agile Coding Practices

Clean Code and Refactoring, TDD, and Pair Programming

84
New cards

Continuous Integration/Continuous Delivery (CI/CD)

An approach to automate the build, testing, and deployment processes to ensure reliable, frequent releases of working software

85
New cards

Agile Metrics

crucial for tracking progress and ensuring delivery goals are met

86
New cards

Velocity

Measures the number of story points or features completed in each sprint

87
New cards

Burn-Up and Burn-Down Charts

Track progress toward completing the project scope

88
New cards

Cycle Time and Lead Time

Measure how quickly features are completed andmoved into production

89
New cards

Defect Density and Code Coverage

Track the quality of the code and the levelof testing performed

90
New cards

Code Reviews

systematic examinations of the code to improve quality and ensure compliance with standards

91
New cards

Agile testing

emphasizing continuous feedback and iterative improvements

92
New cards

Key Testing Types

Unit, Integration, User Acceptance, and Regression

93
New cards

Unit Testing

Validates individual components; typically conducted by developers

94
New cards

Integration Testing

Ensures components work together; detects interface issues

95
New cards

User Acceptance Testing (UAT)

Conducted by stakeholders to validate business requirements

96
New cards

Regression Testing

Ensures new code does not break existing functionality

97
New cards

Specialized Testing Types

UI, Performance, Security, Automated

98
New cards

UI Testing

Focuses on the user interface, checking layout, and usability across devices

99
New cards

Performance Testing

Assesses responsiveness, scalability, and stability under load

100
New cards

Security Testing

Identifies vulnerabilities to prevent potential attacks