Scrum Flashcards
What are the three pillars of Scrum?
Transparency, Inspection and adaptation
Iteration
A timeboxed cycle of development on a product or deliverable in which all of the work that is needed to deliver value is performed.
Iteration Plan
A detailed plan for the current iteration
Iteration Planning (Sprint Planning)
A meeting to clarify the details of the backlog items, acceptance criteria, and work effort required to meet an upcoming iteration commitment.
Iteration (Sprint) Review
A meeting held at the end of an iteration to demonstrate the work that was accomplished during the iteration.
Test-Driven Development
A technique where tests are defined before work is begun, so that work in progress is validated continuously, enabling work with zero defect mindset.
Spike
A short time interval within a project, usually of fixed length, during which a team conducts research or prototypes an aspect of a solution to prove its viability.
Spikes are also described as time-boxed research or experiments and are useful for estimation.
impediment
an obstacle that prevents the team from achieving its objectives. It is also known as a blocker.
“Simplicity” in agile
Maximizing the work that is not done
Continuous Integration
Continuous integration aims to merge code and have a working build once a day, then executes automated tests quickly to see if anything is broken. This frequent checking ensures less time passes before a problem is identified. It is designed to merge all changes made to the software and test them automatically, discovering any defects or issues on a daily basis.
Fast Failure
Agile operates on the concept of delivering increments of value. Fast failure means that particular feature or proof-of-concept effort was not successful. By failing fast and in small increments, the project team is able to learn and adjust quickly and at a much lower cost.
Technical Debt
Technical debt, where code may be rushed to production without being simplified or refactored. With each subsequent release it creates more work to build on and work around disorganized code.
What are the 3 C’s on user story creation?
The three C’s on user story creation are: Card, Conversation and Confirmation. Once the user story card is created, have a conversation with developers and testers to ensure understanding, can for any gaps, and estimate the effort required. Finally, confirm the acceptance criteria. You then place it in the backlog for prioritisation in an upcoming sprint
Push + Pull Communication
Push communication is used to send information to specific recipients who need to know. Push Communication is done using letters, faxes, memos, etc.
Pull communication is used for large volumes of information. The methods for this type of communication include internet sites and blogs. Example: Information to public on the website.
Grade and Quality
Quality is the degree to which the product meets the customer’s requirements
Grade is the category assigned to products that have the same functional use but different technical characteristics.