L7 - Process: Why Do We Scrum?

This set of flashcards covers key concepts and processes discussed in the CPSC 310 lecture on software engineering, focusing on Scrum, Agile methodologies, and project management risks.

What is the importance of process in software development?

Processes provide clarity about decision-making and help software evolve.

What are the 6 dimensions of software project risks?

User, Requirements, Project Complexity, Planning & Control, Team, Organisational Environment.

What does a software process define?

Who does what, when, and how, to reach a goal.

What are the phases of a software process?

Requirements elicitation, Architectural design, Detailed design, Implementation, Integration, Testing, Deployment, Maintenance.

What is a common misconception about process-oriented teams?

They may seem less productive early on but become more effective over time.

What is the goal of requirements in software projects?

To ensure clarity and detail, preventing misunderstandings during implementation.

What is Agile development?

A software development approach that emphasizes iterative progress, customer collaboration, and responsiveness to change.

What are User Stories in Agile development?

Lightweight specifications defining the role, goal, and benefit of a feature.

What are the main Scrum ceremonies?

Sprint Planning, Daily Standup, Review and Retrospective.

What is a Product Backlog in Scrum?

A prioritized list of customer-centric features (User Stories) for the project.

How does Kanban differ from Scrum?

Kanban is a continuous process without fixed sprints, emphasizing work-in-progress limits.

What is a Burndown chart in Scrum?

A chart that tracks the remaining task hours within a sprint.

What is the role of the Scrum Master during Daily Standups?

To track team progress without addressing specific problem-solving.

What is Test Driven Development in Agile?

A practice where developers write tests before writing the code that needs to pass those tests.

What does 'Defintion of Done' mean in Agile?

Acceptance criteria that determine when a user story is considered complete.