System Analysis 2 Scrum Programming

5.0(1)
studied byStudied by 5 people
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
Card Sorting

1/37

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.

38 Terms

1
New cards

Scrum Principles

Transparency – Everyone is aware of each other’s challenges to prevent miscommunication and bottlenecks.

Reflection – Frequent reviews help assess progress and guide future planning.

Adaptation – Tasks can be reprioritized based on changing customer requirements.

2
New cards

Scrum Values

Commitment – Team members are dedicated to achieving goals and continuous improvement.

Courage – Members are encouraged to ask honest, challenging questions.

Focus – Teams concentrate on selected tasks from the Product Backlog during a Sprint.

Openness – Willingness to explore new ideas and promote learning.

Respect

3
New cards

Scrum Artifacts

Product Backlog – A dynamic list of features, fixes, and requirements maintained by the Product Owner.

Sprint Backlog – Tasks selected from the Product Backlog to be completed in the current Sprint.

Increment – The usable product or result delivered at the end of a Sprint.

4
New cards

Scrum Roles

Product Owner – Ensures the development team delivers maximum value and prioritizes customer needs.

Scrum Leader (Scrum Master) – Coaches the team, facilitates meetings, and ensures the team follows Scrum processes.

Development Team – Cross-functional team members who collaborate to complete Sprint tasks.

5
New cards

Scrum Events

Regular meetings including :

Planning – The team estimates and plans what can be achieved in the upcoming Sprint.

Sprint – A fixed time frame (typically 2 weeks) where a deliverable is developed.

Daily Scrum (Stand-up) – A short meeting to review daily progress and challenges.

Sprint Review – Informal meeting to showcase work and gather feedback from stakeholders.

Sprint Retrospective – Reflective meeting to discuss what went well and what can be improved.

6
New cards

Importance of Scrum in Software Development

Maintain Quality – Quality checks and iterative reviews ensure high standards.

Increased ROI – Prioritization and early feedback reduce defects and costs.

Happier Teams – Self-managed teams boost creativity and morale.

Better Estimation – Teams choose and refine metrics to predict time and budget more effectively

7
New cards

Scrum vs. Agile

Agile – A mindset promoting continuous improvement and customer value.

Scrum – A specific Agile framework with defined roles, events, and artifacts..

8
New cards

Benefits of a Scrum Team

Scrum enables simultaneous work, clear workflows, better ROI, and higher team morale through structure and autonomy.

9
New cards

Scrum

A management framework that teams use to self-organize and work towards a common goal using defined meetings, tools, and roles.

10
New cards

Scrum Guide

A comprehensive reference co-created by Jeff Sutherland and Ken Schwaber outlining how to apply Scrum effectively.

11
New cards

Transparency

Everyone is aware of each other’s challenges to prevent miscommunication and bottlenecks.

12
New cards

Reflection

Frequent reviews help assess progress and guide future planning.

13
New cards

Adaptation

Tasks can be reprioritized based on changing customer requirements.

14
New cards

Commitment

Team members are dedicated to achieving goals and continuous improvement.

15
New cards

Courage

Members are encouraged to ask honest, challenging questions.

16
New cards

Focus

Teams concentrate on selected tasks from the Product Backlog during a Sprint.

17
New cards

Openness

Willingness to explore new ideas and promote learning.

18
New cards

Respect

Team members respect each other, the process, and leadership.

19
New cards

Product Backlog

A dynamic list of features, fixes, and requirements maintained by the Product Owner.

20
New cards

Sprint Backlog

Tasks selected from the Product Backlog to be completed in the current Sprint.

21
New cards

Increment

The usable product or result delivered at the end of a Sprint.

22
New cards

Product Owner

Ensures the development team delivers maximum value and prioritizes customer needs.

23
New cards

Scrum Leader (Scrum Master)

Coaches the team, facilitates meetings, and ensures the team follows Scrum processes.

24
New cards

Development Team

Cross-functional team members who collaborate to complete Sprint tasks.

25
New cards

Sprint Planning

The team estimates and plans what can be achieved in the upcoming Sprint.

26
New cards

Sprint

A fixed time frame (typically 2 weeks) where a deliverable is developed.

27
New cards

Daily Scrum (Stand-up)

A short meeting to review daily progress and challenges.

28
New cards

Sprint Review

Informal meeting to showcase work and gather feedback from stakeholders.

29
New cards

Sprint Retrospective

Reflective meeting to discuss what went well and what can be improved.

30
New cards

Maintain Quality

Quality checks and iterative reviews ensure high standards.

31
New cards

Increased ROI

Prioritization and early feedback reduce defects and costs.

32
New cards

Happier Teams

Self-managed teams boost creativity and morale.

33
New cards

Better Estimation

Teams choose and refine metrics to predict time and budget more effectively.

34
New cards

Agile

A mindset promoting continuous improvement and customer value.

35
New cards

Simultaneous Work

Teams work in parallel, not sequentially, increasing speed and collaboration.

36
New cards

Clear Workflow

Scrum defines a transparent, iterative process for teamwork.

37
New cards

Improved ROI & Lower Risk

Efficient development with fewer defects saves time and money.

38
New cards

Higher Morale

Empowers team members, fosters feedback, and promotes sustainability.