APM Flashcards
REVISION
1
Q
What is the Waterfall approach?
A
A linear model where each phase must be completed before moving to the next.
2
Q
What is a key reason to consider Agile over Waterfall for a final year project?
A
Requirements may evolve, and Waterfall does not easily accommodate changes.
3
Q
List two benefits of Agile methodologies.
A
- Iterative development
- Continuous feedback
4
Q
What are the four core values of the Agile Manifesto?
A
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
5
Q
What is the purpose of Sprint Planning in Scrum?
A
Defines what will be accomplished in the upcoming sprint.
6
Q
Describe the Daily Stand-up in Scrum.
A
A quick meeting to discuss progress, roadblocks, and plans.
7
Q
What is the significance of the Sprint Review?
A
Demonstration of completed work to stakeholders for feedback.
8
Q
What does the Sprint Retrospective focus on?
A
Team reflects on the sprint to identify improvements.
9
Q
What is Backlog Refinement in Scrum?
A
Ensures the product backlog is well-prioritized and detailed.
10
Q
When is Scrum most suitable to use?
A
For projects requiring structured iterations with planned deliverables.
11
Q
What is Kanban best suited for?
A
Continuous maintenance tasks with variable priorities.
12
Q
How does testing differ between Agile and Waterfall?
A
- Waterfall: Testing occurs after development is complete.
- Agile: Testing is continuous and integrated within sprints.
13
Q
What is refactoring in software development?
A
The process of improving code structure without changing its functionality.
14
Q
What does the statement ‘If it ain’t broke, don’t fix it’ imply?
A
Can lead to outdated and inefficient systems.
15
Q
Name a stakeholder and their influence in a project.
A
Government – Defines policies and funding.
16
Q
What are some technical options for managing a project?
A
- Smart Cards/Digital IDs
- Mobile App/Web Portal
- Blockchain
- Cloud-based System
- POS Integration
- AI & Data Analytics
17
Q
List operational impediments that can affect a project.
A
- Retailer Resistance
- Fraudulent Claims
- Technical Failures
- User Adoption
- Budget Constraints
- Data Privacy Concerns
18
Q
What is a Public-Private Partnership in a business model?
A
Government funds initial costs; retailers benefit from increased sales.
19
Q
What is one of the major features of a crypto trading platform?
A
Digital Wallet – Secure storage of cryptocurrencies.
20
Q
Provide an example of a user story for a crypto trading platform.
A
As a user, I want to buy crypto securely using my payment method.
21
Q
What is the purpose of effort, value, and risk estimation?
A
To assess the feasibility and prioritize user stories.
22
Q
What is a primary criterion for prioritization of user stories?
A
User Value – Features that enhance user experience.
23
Q
What is the goal of Sprint 1 in a release plan?
A
Account Verification and Wallet Setup (Security & Compliance).
24
Q
What is a characteristic of projects that make the Waterfall approach less applicable?
A
Projects with evolving requirements.
25
What is waste in Lean software development?
Any activity that does not add value to the customer.
26
List two tenets of Lean software development.
* Eliminate waste
* Build quality in
27
What is the main practice of Kanban?
Visualizing work to optimize flow.
28
Identify two actors from the emotional support service case study.
* Members
* Government
29
Describe a user story for the emotional support service.
As a member, I want to book emotional support so that I can alleviate loneliness.
30
How does relative software estimation differ from absolute software estimation?
Relative estimation compares stories against each other, while absolute estimation assigns fixed time or effort.
31
What is the value-risk method in setting priorities?
It evaluates user stories based on their value to users and associated risks.
32
What is the goal of the release plan for the emotional support service?
To ensure a gradual and functional rollout of features.
33
What is the purpose of the Daily Scrum Meeting?
To track daily progress and coordinate activities
## Footnote
Also referred to as daily huddle or daily standup
34
What are the four statuses tracked on an Agile taskboard?
* To Do: user stories not yet started
* In Process: user stories currently under development
* To Verify: completed but not yet checked
* Done: verified by product owner
35
Who is responsible for managing and resolving roadblocks?
Scrum Master
## Footnote
Includes tactical issues and organizational impediments
36
What is the maximum duration for a Daily Scrum Meeting?
15 minutes max
37
What should team members specify during the Daily Scrum?
* Items completed the previous day
* Items to be addressed today
* Impediments faced
38
What practices improve the quality of development in Agile?
* Pair programming
* Following design standards
* Test-driven development
39
Fill in the blank: The Daily Scrum is carried out standing to limit _______.
duration
40
What is the role of the Product Owner during the verification process?
Reviews functionality developed and provides feedback and approval
41
What are the types of testing focused on in Agile?
* Automated testing
* Unit testing
* System testing
* Static testing
42
What should be done if new nice-to-have features appear during development?
Add them to Product Backlog, not to sprint backlog
43
What is the focus of the Daily Scrum?
Immediate priorities for the day
44
True or False: Status reporting is a key part of the Daily Scrum.
False
45
What should team members do if they arrive late to the Daily Scrum?
Pay a fine
46
What does each team member do in peer-review?
Reviews each other’s code
47
What is the purpose of integrating changes coded during the day one at a time?
To ensure quality and manage complexity
48
What is meant by 'creating shippable functionality' in Agile?
Developing and verifying usable functionality
49
What practices should be avoided when detailing user stories?
Going into detailed analysis
50
What does the Scrum Master specify during the Daily Scrum?
* Problems resolved yesterday
* Impediments to work on today
* Problems to escalate
51
What is the role of the Product Owner in Scrum?
Represents and speaks for the business needs of the project
## Footnote
The Product Owner is an IT person with in-depth domain knowledge.
52
Who comprises the Development Team in Scrum?
Software developers doing the daily work
53
What is the main function of the Scrum Master?
Promotes the Scrum methodology, protects the team, and clears hurdles
54
Who are considered stakeholders in a Scrum project?
Anyone affected by the project
55
What defines Agile approaches?
Development in iterations, emphasis on simplicity, transparency, and contextual strategies
## Footnote
Involves frequent inspection and immediate adaptation.
56
What is pair programming in Extreme Programming?
Two people working on one task (driver + navigator)
57
What is the purpose of intensive testing in Extreme Programming?
Coding only done after tests are designed and developed
58
What is a Product Backlog in Scrum?
Set of high level requirements for the system developed from user input
59
What occurs during a Sprint in Scrum?
A set of useful functionality is developed and meetings are held daily to review progress
60
What is the focus of Extreme Programming?
Customer satisfaction by developing software features when the customer needs them
61
What is a key principle of Lean software development?
Eliminate waste
62
What are some types of waste in Lean software development?
* Building the wrong feature or product
* Mismanaging the backlog
* Rework
* Unnecessarily complex solutions
* Extraneous cognitive load
* Psychological distress
* Waiting/multitasking
* Knowledge loss
* Ineffective communication.
63
What is the Lean-Kanban approach adapted from?
Toyota Production System
64
What does Kanban practice emphasize?
* Visualizing workflow
* Limiting work in progress
* Managing the flow
65
What is a major Agile method introduced in 1995?
Scrum
66
What does the concept of 'empower the team' in Lean software development entail?
No managers to give instructions; team members should be autonomous
67
What is the significance of 'amplifying learning' in Lean software development?
Learning improves predictability and increases inspections and adaptations
68
Fill in the blank: The Scrum methodology includes a _______ to assess performance and change for the better.
Sprint Review
69
True or False: Continuous improvement is a concept emphasized in Agile methodologies.
True
70
What is the role of an Agile mentor?
Experienced coach on Scrum
71
What does 'sustainable pace' mean in Extreme Programming?
Maintaining a working week of 40 hours
72
What is a key outcome of frequent inspection and immediate adaptation in Agile?
Quick delivery and continuous improvement
73
What is a sprint retrospective?
A meeting where the product owner, development team, and scrum master discuss how the sprint went and how to improve the next sprint
## Footnote
It includes evaluation of both good and bad aspects of the sprint.
74
How does a sprint retrospective differ from a sprint review?
A sprint review is a demo of work done, while a sprint retrospective is a discussion on how to improve things.
75
What is the ideal nature of a sprint retrospective meeting?
It should be as self-directed as possible, without supervisors interfering.
76
What is the benefit of improving processes in a sprint retrospective?
To improve team velocity, efficiency, and morale.
77
What should each team member focus on when planning for the sprint retrospective?
* What went well and why
* What went wrong and why
* How can we implement the required change
78
What techniques can be used if the team is not open to discussing issues in a sprint retrospective?
Group moderating techniques such as anonymous notes or the Delphi technique.
79
What evidence can be used to identify areas needing improvement in a sprint retrospective?
Sprint backlog or sprint burndown chart.
80
What should be avoided during the sprint retrospective meeting?
The blame game.
81
How long should a sprint retrospective meeting last based on the sprint duration of one week?
0.75 hours.
82
What are some areas for discussion in a sprint retrospective?
* Results: work completed vs. work planned
* People: team composition
* Relationships: communication/collaboration
* Processes: design, development, review, testing
* Tools: technology and tool effectiveness
* Productivity: team’s productivity
83
What is the first step in the proposed modus operandi for a sprint retrospective?
Set the stage: remind the goals of the meeting.
84
What is a potential problem that can occur in a sprint retrospective due to repetitive questioning?
Apathy.
85
How can emotions affect a sprint retrospective meeting?
It can get tense; avoiding judgmental behavior is crucial.
86
What should the team discuss regarding actions in a sprint retrospective?
What they would like to start, stop, and continue doing.
87
What can be done to keep a sprint retrospective engaging?
Incorporate novelty and varying tactics, such as games.
88
What is the purpose of a project retrospective?
To complete work, negotiate another sprint, and ensure all obligations are fulfilled.
89
What should be communicated to manage changes during a project retrospective?
Reassurance to mitigate fear of the unknown.
90
What should be prepared after a product is implemented?
A post-implementation review.
91
Main limitations of waterfall-type software processes
Inflexibility – Requirements are fixed early, making changes difficult.
Late Testing – Testing is done at the end, increasing the risk of undiscovered defects.
Slow Feedback Loop – Clients cannot see progress until the later stages.
