Chapter 5 Flashcards
(38 cards)
Acceptance Test-Driven Development (ATDD)
Testing approach that considers the perspective of the customers, developers, and testers. The test is written before the coding, and then the developers create code to pass the known test.
AgilePM
Project management framework developed as a subset of the Dynamic Systems Development Method (DSDM) and designed to provide a more focused approach to agile project management. AgilePM is based on the principles of DSDM, but it has been streamlined to provide a more accessible and practical approach to agile project management. It also provides more specific guidance on project management practices, such as risk management, planning, and governance.
Behavior-Driven Development (BDD)
Based on acceptance test-driven development but uses the Five Whys approach to really understand why a feature is to be included in the product. The Five Whys approach asks the question “why?” several times. Each question leads to another question, forming a chain of cause-and-effect that gradually gets closer to the root cause.
Burndown Chart
A downward-trending chart that shows the number of user story points in the product backlog in relation to how many user stories the team can create in each iteration. As more iterations happen and the team completes the user stories, a downward-trending line shows fewer and fewer user stories remaining in the backlog, and this reveals a trend for velocity and expectations about when the project can realistically complete all the user stories.
Burnup Chart
An upward-trending chart that shows the number of user story points in the product backlog in relation to how many user stories the team is able to create in each iteration. As more iterations happen and the team completes the user stories, an upward-trending line shows the accumulation of user stories accomplished and the remaining story points in the backlog. This chart also reveals a trend for velocity and expectations about when the project can realistically complete all the user stories.
Continuous Integration (CI)
A software development practice in which team members frequently integrate their work with the main codebase, usually multiple times a day. The goal of CI is to reduce integration problems by detecting and resolving integration issues as soon as possible.
Cumulative Flow Diagram
A stacked chart that shows the total number of items in each phase of the project, such as the backlog, development, testing, and release. This chart can be used to identify too many items in work in progress (WIP) and bottlenecks in the project.
Daily Scrum
A short and focused meeting held by the scrum team every day. The purpose of the daily scrum is to facilitate communication and coordination among team members, ensuring that everyone is aware of the progress made and the challenges faced in achieving the sprint goal.
Development Team
The team that is responsible for sizing the requirements of the product backlog and getting work done in each sprint. The development team is self-organizing, self-led, and its members are called generalizing specialists because they can often do more than one function on the team. An ideal scrum team has no fewer than five people and no more than eleven people.
Dynamic Systems Development Method (DSDM)
One of the predecessors of today’s agile project management, relies on a business case to show value and a feasibility study to determine if the development team could create the architecture and requirements the customer identified. DSDM provides more structure than rapid application development (RAD), utilizes iterations, and is a great approach when working with vendors as part of your agile project. DSDM also offers a unique approach as it can be blended with Scrum, PRINCE2, and other project management approaches.
Feature/Function
A distinct capability or behavior of a software system that provides value to the user or customer. A feature or function can be thought of as a specific requirement or piece of functionality that the software system is expected to provide.
Feature-Driven Development (FDD)
An iterative approach to software development that bases its progress on the clients’ values of features the software will provide. FDD is an agile approach that utilizes a product backlog to complete the project work but follows a more rigid approach to agile project management than other approaches.
Iteration
A document that records and tracks any challenges or problems that occur in a project. Helps PMs and teams to assign, report, communicate and resolve issues quickly and effectively. May include information such as the issue identifier, description, type, impact, status and resolution.
Iteration Backlog
A collection of work items that a team plans to complete during an iteration, which can be a timeboxed period of any length, such as a week, two weeks, or a month. Iteration backlog is a term commonly used in agile approaches such as Kanban, where sprints are not typically used and instead work is planned in iterations. The iteration backlog lists the prioritized work items, which can include features, user stories, bugs, and technical tasks that the team plans to complete during the iteration.
Iteration Planning
A core practice in agile methodologies that is used to plan and manage the work that will be done during an iteration or sprint. See also sprint/iteration.
Minimum Business Increment (MBI)
The smallest possible deliverable unit that provides some value to the customer and can be independently deployed, tested, and validated. MBIs are often used in agile methodologies to break down larger features or projects into smaller, manageable pieces that can be completed and delivered more efficiently.
Product Backlog
The person who identifies the customer’s need and the larger business objectives that a product or feature will fulfill, articulates what success looks like for a product, and rallies a team to turn that vision into a reality.
Retrospective
See Sprint Retrospective.
Scaled Agile Framework (SAFe)
An agile methodology that provides a framework for implementing agile practices at scale in organizations. SAFe is designed to help organizations achieve better alignment, collaboration, and delivery of value across multiple teams, departments, and business units.
Scrum Master
An individual who serves the team by removing roadblocks, protecting the development team from distractions, ensuring that all members are following the scrum rules, and coaching and educating stakeholders on scrum practices. The scrum master acts as a servant leader to the team by getting the team what they need to be successful. The scrum master facilitates scrum meetings, helps the product owner refine the backlog, and communicates the vision of the project to everyone that’s involved.
Scrum of Scrums
A type of meeting in a large project involving several scrum teams in which a representative from each scrum team discusses the project’s progress, impediments, and if any work may affect other scrum teams. Rather than having a huge daily scrum, the teams meet separately and then a representative from each team meets in a scrum of scrums to report on each team’s progress. The team representatives answer the same questions as in the daily scrum, but for the team rather than individuals. In addition, a fourth question is often posed: “Will our team be putting something in another team’s way?”
Scrum Team
A work team that includes the product owner, the scrum master, and the development team. The typical project management activities are divided among these three roles in a scrum project.
Spike
A timeboxed activity that is used to explore a particular technical or design issue. It is a small experiment or investigation that is conducted by the development team to help them better understand a problem or potential solution before committing to a larger, more complex implementation.
Sprint Backlog
In Scrum, the specific set of user stories, bugs, or features that a development team commits to completing during a sprint. It is a plan for the work that needs to be done in the upcoming sprint and typically includes estimates for each item. The sprint backlog is created during the sprint planning meeting, and it guides the team’s daily work throughout the sprint.
