-
Continuous Integration
Advanced Scrum software development processes implementing Extreme Programming's Continuous Integration (CI) technique allows team members to integrate their work and achieve a new level of technical excellence. In this video; Kevin McManus discusses how to provide a greater degree of efficiency and confidence in a software development project by introducing CI.
-
Scrum
After watching this video; you will be able to recall the basic features of the Scrum agile approach.
-
Daily Standups and Progress Reporting
In advanced Scrum; the daily standup is one of four meetings that make up the Scrum framework. In this video; Kevin McManus uses the daily standup to raise awareness of issues and refer action items and problems to external meetings.
-
Dealing with Unpredictability
The advanced Scrum principles of iterative and incremental planning and delivery; allows you to mitigate the unpredictable nature of a software development project. In this video; Kevin McManus discusses the Scrum empirical processes for dealing with unpredictable software development and the advantages of Scrum over the Waterfall development model.
-
Definition of "Done"
"In Advanced Scrum; the definition of ""Done"" determines whether a feature or user story has reached the status of the potentially shippable product increment. In this video; Kevin McManus discusses the definition of ""Done""; which can be subjective based on who is establishing the criteria."
-
Detecting Potential Risks
Advanced Scrum development uses an empirical process framework that allows you to quickly and efficiently detect and mitigate the risks associated with software development projects. In this video; Kevin McManus discusses how specific Scrum roles; artifacts; and meetings improve the quality and frequency of communication that helps development Teams mitigate risk.
-
Distributed Scrum Challenges
Advanced Scrum provides a framework of artifacts; roles; and meetings that can be used in distributed development environments worldwide. In this video; Kevin McManus discusses the need for timely; accurate; and deliberate communication between cross-functional and co-located Scrum Team members.
-
Emergent Design
Advanced Scrum practices allow you to respond to change and allow the design to emerge in a flexible and responsive way by harnessing the evolutionary nature of Agile software development through Emergent Design. In this video; Kevin McManus discusses how Emergent Design provides a solution to changing requirements and the evolving skills of Team members in software development projects.
-
Establishing Accountability
In Scrum; the expectation/accountability loop is a mechanism that conveys requirements and measures accountability for software development project teams. In this video; Kevin McManus demonstrates how accountability is communicated and measured in Scrum teams.
-
Estimating User Stories
In advanced Scrum; the Scrum Team provides detailed estimates of the tasks associated with completing user stories. In this video; Kevin McManus uses the Planning Poker method to reach consensus within the team on a relative estimate for each user story.
-
Evaluation of User Stories
Advanced Scrum requires that User Stories are created by the Product Owner and project stakeholders. In this video; Kevin McManus discusses how User Stories are prioritized in the Product Backlog before evaluation by the Scrum Team and committal to the Sprint Backlog.
-
Excessive Durations
In an Advanced Scrum development process; the excessive duration of iterations can negate the advantage of receiving feedback and increase risk to the project. In this video; Kevin McManus discusses the negative impact an iteration that goes beyond four weeks can have on the Team and the overall project.
-
Excessive Process Changes Per Iteration
In Scrum; continual improvement and integration through the software development process involves an iterative and incremental approach. In this video; Kevin McManus discusses how to plan and prioritize the process of continuous integration.
-
Excessive User Stories
In Advanced Scrum; a user story is a short narrative describing a feature of a system. Some user stories provide excessive detail and tend to become large. This is known as an Epic – a large user story made up of smaller; more granular user stories. In this video; Kevin McManus discusses excessive user stories.
-
Feature-driven Sprints
In Advanced Scrum; you will learn about feature-driven sprints. In this video; Kevin McManus demonstrates two ways for scoping a sprint by using either time-boxing or feature-boxing; including a basic comparison of their features.
-
General Communications Best Practices
In Scrum; it is vital for software development teams to maintain deliberate and frequent communication. Technology can play a key role in facilitating communications across distributed Scrum teams. In this video; Kevin McManus demonstrates the best practices for communicating within distributed software development teams.
-
Identifying Risk and Sequencing
Advanced Scrum project management principles necessitate that the Team is responsible for educating the Product Owner on the impact of technical risks and sequencing tasks associated with a user story. In this video; Kevin McManus uses an application's authentication requirements to describe the Product Owner and Team's responsibilities regarding user story technical details.
-
Importance of the Product Increment
In an advanced Scrum software development process; the Product Increment is a key artifact delivered after each Sprint that allows feedback to be provided based on a working product. In this video; Kevin McManus demonstrates the Product Increment and the importance of satisfying the customer through early and continuous delivery of valuable software.
-
Incomplete Product Backlog
In Scrum; the product backlog is the primary repository for specifying the requirements and associated priorities that drive the overall work of a software development team and influence the outcome of a project. In this video; Kevin McManus explains how the risks posed by an incomplete product backlog may be prevented and mitigated.
-
Inconsistent Scheduling
By addressing inconsistent scheduling in an advanced Scrum development environment; leveraged Teams supporting multiple projects can effectively find a balance in maximizing utilization while being agile. In this video; Kevin McManus discusses how to mitigate the negative impact of context switching by managing the number of projects and project requirements when assigning projects to Team members.
-
Inexperienced Team
You may have an inexperienced Scrum team who lack the know-how to work with the process framework. The ScrumMaster can act as the facilitator or coach to help the team learn about the Scrum process. In this video; Kevin McManus discusses how to alleviate the problems associated with a lack of experience in Scrum.
-
Lack of Estimation Data
Advanced Scrum teaches you how to overcome a lack of estimation data used to determine initial velocity. You can; for example; make an educated guess; use commitment-driven planning; or use a similar team's history as a starting point. In this video; Kevin McManus demonstrates how to obtain an initial velocity without initial estimation data.
-
Lack of Sprint Retrospective Meetings
In Scrum; the Sprint Retrospective meeting is a built-in mechanism that allows Scrum teams to continually improve and refine the software development process. In this video; Kevin McManus discusses why it is important to hold regular Sprint Retrospective meetings which enable Scrum teams to make improvements and build recommendations into the next sprint.
-
Lack of Sprint Reviews
In Scrum; Sprint Review meetings are an opportunity for the Product Owner; the ScrumMaster; and the software development team to communicate; receive feedback from the stakeholder; and view a demonstration of the working software. In this video; Kevin McManus discusses the purpose and benefits of Sprint Review meetings in Scrum.
-
Negative Impacts of Team Changes on Velocity
Team changes in an advanced Scrum software development process can negatively affect the velocity when failing to give careful consideration to the capabilities of new members and the impact of team members leaving. In this video; Kevin McManus discusses evaluating new Team member's skill sets and mitigating Team redundancy to maintain a predictable velocity.
-
Non-Attendance
In an advanced Scrum development process; the daily stand-up meeting acts as the heartbeat of the project and any non-attendance should be addressed and resolved as soon as it becomes apparent. In this video; Kevin McManus discusses the motivation of the daily stand-up meeting; the significance of Team member attendance; and how to deal with non-attending members.
-
Outside Interference
Addressing outside interference in an advanced Scrum development process allows the Team to remain focussed and helps prevent Sprint objectives from being derailed. In this video; Kevin McManus uses a scenario to illustrate how the Scrum Master can protect a developer from the outside interference of a business stakeholder and keep the Sprint on track.
-
Polishing the Cannonball
In an Advanced Scrum software development environment; addressing a mode of "polishing the cannonball" will allow you to adhere to the Agile principle of keeping it simple. In this video. Kevin McManus uses a scenario to illustrate how adding unnecessary functionality without consulting the Team or Product Owner can introduce risk to a Sprint.
-
Positive Impacts of Team Changes on Velocity
An advanced Scrum development process allows changes to be made to the composition of the Team; providing additional capacity and experience that will ultimately impact positively on the Team's overall velocity. In this video; Kevin McManus demonstrates how the addition of Team members that include experienced personnel; domain experts; seasoned Scrum Masters; and engaged Product Owners can improve velocity.
-
Predictable Process
Advanced Scrum software management allows you to improve upon the Waterfall process when developing software products with a high degree of predictability. In this video; Kevin McManus demonstrates how the well-defined features in a financial software package can be managed successfully following the waterfall approach with the benefits of delivering software at incremental steps.
-
Prioritization of User Stories
Advanced Scrum requires that the Product Owner prioritize User Stories in the Product Backlog to avoid ambiguity in the development environment. In this video; Kevin McManus demonstrates how prioritizing User Stories by business risk and value facilitates flexible development without impacting deadlines.
-
Product Owner Proxy
Advanced Scrum requires that; if the Product Owner is absent; the role and its responsibilities must be transferred in full to a proxy. In this video; Kevin McManus demonstrates how appointing a Product Owner proxy mitigates against assumptions by the Scrum Team.
-
Release Planning Meeting Overview
Advanced Scrum requires that a high-level set of logical; flexible project milestones be established during a release planning meeting. In this video; Kevin McManus demonstrates how to prioritize requirements and set a time frame in which to complete a Scrum project's tasks.
-
Responsibilities of the Product Owner
Advanced Scrum requires that a Product Owner collaborates with the Scrum Team and external stakeholders to prioritize User Stories in a Product Backlog. In this video; Kevin McManus discusses how the Product Owner mitigates assumptions about project requirements and determines their completion.
-
Responsibilities of the ScrumMaster
Advanced Scrum requires that the ScrumMaster guides the Scrum Team through Sprints to project completion. In this video; Kevin McManus demonstrates how the ScrumMaster resources and protects the Scrum Team while gathering requirements with the Product Owner for future Sprints.
-
Responsibilities of the Team
Advanced Scrum requires that the Scrum Team contributes to and completes the requirements of the prioritized Product Backlog. In this video; Kevin McManus demonstrates how the Scrum Team discharges its responsibilities to the ScrumMaster and Product Owner by adhering to Agile principles.
-
Risks of Ignoring Technical Debt
In the Scrum framework; changes implemented during software development may result in a technical debt. In this video; Kevin McManus discusses a scenario which illustrates the risks that build when a technical debt is ignored or is not promptly addressed by the software development team.
-
Scrum as a Control Tool
In advanced Scrum; you can establish accountability within the Scrum Team across the Product Owner; the ScrumMaster; and the team itself. In this video; Kevin McManus uses an analogy to show how Scrum can act as a control tool and emphasizes the importance of setting clear expectations.
-
Sprint Duration Issues
Addressing Sprint duration issues in an advanced Scrum software development process allows you to benefit from delivering potentially shippable product increments in a relatively short timeframe. In this video; Kevin McManus discusses the risks associated with Sprint durations that are either too long or too short; and the advantage of delivering valuable software at the correct frequency.
-
Test-driven Development
Advanced Scrum practices allow you to reinforce iterative and incremental software design; and produce high quality applications by repeatedly conducting unit tests on source code using the Extreme Programming test-driven development (TDD) technique. In this video; Kevin McManus discusses the TDD methodology; and how TDD and refactoring benefits development in a Continual Integration (CI) environment.
-
The Agile Philosophy Core Values
In advanced Scrum; the Agile philosophy has four core values. In this video; Kevin McManus uses Scrum and Extreme Programming to illustrate multiple Agile methods used in combination with the Agile core values.
-
The Agile Philosophy Principles
In advanced Scrum; there are twelve Agile philosophy principles. In this video; Kevin McManus uses the Scrum Agile method to discuss the appropriate sprint duration to deliver working software.
-
The Communications Richness Spectrum (CRS)
Advanced Scrum's communication richness spectrum (CRS) ranks the efficacy of communication media while allowing for flexibility and diversity. In this video; Kevin McManus discusses how to convey and process information between Scrum Team members of different personality types and language groups.
-
The Daily Standup (Pigs & Chickens)
In an advanced Scrum development process; the focused nature and productive success of the daily stand-up meeting relies on clear understanding of who does and who doesn't participate. In this video; Kevin McManus uses the Chicken and Pig fable to illustrate the difference between those who actively participate in the daily stand-up; and those who attend in a listen-only capacity.
-
Absent Product Owner
Advanced Scrum requires the Product Owner to act as a critical intermediary between external stakeholders and the Scrum Team. In this video; Kevin McManus discusses the Product Owner's crucial functions and considers factors contributing to; and mitigating against; his or her absence.
-
Adding Additional Work
In Advanced Scrum; the addition of tasks or user stories to an existing Sprint Backlog needs careful consideration by the Product Owner to prevent jeopardizing the delivery of Sprint commitments. In this video; Kevin McManus demonstrates how additional work is evaluated by the Product Owner and the importance of consulting the Product Owner before adding tasks to a Sprint.
-
Addressing Ambiguity in Requirements
Defining requirements at the appropriate level of detail within an advanced Scrum software development project; addresses vagueness and ambiguity; helping to ensure that the Team delivers a product that meets the customer's expectations. In this video; Kevin McManus demonstrates how to take a hypothetical requirement from a subjective specification to a well-defined and verifiable requirement.
-
Agile Philosophy and Extreme Programming
In advanced Scrum; you will find that Extreme Programming (XP) is based on five values. In this video; Kevin McManus uses the XP values to do a comparison with the principles and values of the Agile philosophy.
-
Agile Philosophy and Kanban
In advanced Scrum; Kanban relies on visuals to show the status of products as they progress through a particular workflow. In this video; Kevin McManus uses a project to illustrate the visual flow of all requirements flowing from the To Do to the Done columns in the progress chart.
-
Agile Philosophy and Lean
In advanced Scrum; a number of Lean Software Development principles draw inspiration from Agile principles. In this video; Kevin McManus uses the amplify learning principle to allow the team to reflect on how to become more effective.
-
Agile Philosophy and Scrum
In advanced Scrum; you will find that Scrum consists of three roles; three artifacts; and four meetings; and is governed by four values and twelve principles of the Agile philosophy. In this video; Kevin McManus uses the three Scrum roles to explain the responsibilities of the Product Owner; ScrumMaster; and team.
-
Allowing Room for Discovery
The iterative and incremental nature of the advanced Scrum process and correlation with Agile principles allows room for discovery in the requirements during the course of a software development project. In this video; Kevin McManus discusses how Scrum's empirical process allows requirements to evolve; allowing the Team to move forward with the project's development.
-
Assembly Line Example
Advanced Scrum requires that the software-development environment accommodates and implements dynamic; creative; people-driven processes that enhance Team capability. In this video; Kevin McManus discusses how the Scrum development environment differs from that of a robotic; automated assembly line.
-
Benefits of Addressing Technical Debt
In Scrum; a software development project involves decisions and concessions over deadlines and requirements that may result in a technical debt. In this video; Kevin McManus discusses a scenario where a Scrum team has to deal with the technical debt incurred by implementing a suboptimal solution because of a deadline concession.
-
Burndown Charts
In advanced Scrum; you can use a burndown chart to track the number of hours expended during a sprint. In this video; Kevin McManus uses an example to show the trend line for a project that is on schedule.
-
Code Reviews and Redundancy
Advanced Scrum practices allow you to streamline the code review process and develop a level of Team redundancy by implementing paired programming redundancy. In this video; Kevin McManus discusses the benefits of paired programming and the principle of a mastermind when two developers collaborate on a single piece of code.
-
Commitment-driven Planning
Advanced Scrum involves an understanding of commitment-driven planning; which is a form of sprint planning. In this video; Kevin McManus demonstrates how commitment-driven planning focuses on the team and their efforts to work together to achieve a goal. This commitment is not just to the work; but also towards each other.
-
Conflicting Product Goals
Advanced Scrum requires that the Product Owner avoid conflicting product goals by setting User Story priorities. In this video; Kevin McManus demonstrates how a Product Backlog featuring User Stories of equal priority produces sequencing issues before being prioritized by the Product Owner.
-
Consulting the Team
Advanced Scrum principles require continual consultation and collaboration with the Scrum Team to ensure that the best possible product is delivered on time and without any unwanted surprises along the way. In this video; Kevin McManus discusses the principles contained in the Agile Manifesto that give structure to the communication between the Product Owner; Scrum Master; and the Development Team.
-
The Importance of Team Velocity
Team velocity in advanced Scrum software management is a valuable metric that allows you to measure the work a Team can achieve in a Sprint and predict future output. In this video; Kevin McManus demonstrates the velocity metric and the contributing factors for determining the natural velocity of a Scrum Team following the Agile principle of sustainable development.
-
The Power of Leverage
In advanced Scrum; you will find a myriad of industries leveraging the power of Scrum and Agile methods. In this video; Kevin McManus uses the three basic questions to exchange updates and data at the daily standup meetings.
-
Unavailable Product Backlog
Advanced Scrum requires that a Product Backlog prioritizes its business; technical; and other requirements. In this video; Kevin McManus discusses how a Product Backlog's availability relies on its requirements being prioritized to maximize business value and mitigate risk.
-
Unprepared Team
In Scrum; it is imperative that the software development team is adequately prepared for using an Agile software development framework that involves iterative and incremental planning and development. In this video; Kevin McManus discusses the challenges of introducing a new process framework like Scrum in an organization.
-
Unrealistic Expectations
In Scrum; collaboration; coordination; and communication are the three Agile core practices that allow the software development team to mitigate the potential of unrealistic expectations. In this video; Kevin McManus discusses how Scrum teams can manage expectations and promote confidence in their ability to deliver customer expectations within set timeframes.
-
User Registration Iteration 1
Advanced Scrum requires a phased; iterative approach to software development. In this video; Kevin McManus demonstrates how a web application's first iteration is realized by the Scrum Team committing to its estimates and the development of the application's deliverable components.
-
User Registration Iteration 2
Advanced Scrum requires a phased; iterative approach to software development. In this video; Kevin McManus demonstrates how a web application's second iteration is realized by the Team adhering to Scrum processes following the Product Owner's approval of its component deliverables.
-
User Registration Iteration 3
Advanced Scrum requires a phased; iterative approach to software development. In this video; Kevin McManus demonstrates how a web application's third iteration is realized by the Scrum Team adhering to Scrum processes and delivering a potentially shippable product increment.
-
Utilizing Technology for Effective Communications
Advanced Scrum requires the appropriate use of technology for effective communication between Scrum Team members. In this video; Kevin McManus discusses the uses of e-mail; instant messaging; telephone calls; and video conferencing; and makes recommendations for enhancing their efficacy.
-
Variable Sprint Durations
In Advanced Scrum; a team's natural velocity is described as the number of user stories a team can accomplish on a sustainable basis. This velocity is calculated using uniform sprint durations due to the higher degree of predictability. Conversely; variable duration affects velocity because it provides less predictability. In this video; Kevin McManus discusses variable sprint durations.
-
Velocity-driven Planning
In Advanced Scrum; you learn about two forms of sprint planning – commitment-driven and velocity-driven. In this video; Kevin McManus discusses velocity-driven planning; explores the assumptions that allow you to create uniformity between sprints; and examines an example of velocity-driven planning.
-
Wrong Product Owner
Advanced Scrum requires the Product Owner to play a critical intermediary role between external stakeholders and the Scrum Team. In this video; Kevin McManus discusses a successful Product Owner's skill sets and considers scenarios in which inappropriately-qualified candidates might be appointed.
-
A Scrum Tester
After watching this video; you will be able to describe the role of an agile tester within the specific context of a Scrum life cycle.
-
Acceptance Test-driven Development
After watching this video; you will be able to describe how acceptance test-driven development is applied in agile projects.
-
Agile and Independent Testing
After watching this video; you will be able to outline options for using independent testers on agile projects.
-
Agile Project Work Products
After watching this video; you will be able to describe the project work products that are important to agile testers.
-
Agile Software Development and the Agile Manifesto
After watching this video; you will be able to recall the statements of value expressed in the Agile Manifesto; on which the principles of agile software development are founded.
-
Collaborative User Stories
After watching this video; you will be able to describe how collaborative user stories are created to capture requirements in agile projects.
-
Communicating Test Status and Product Quality
After watching this video; you will be able to describe how test status; progress; and product quality can be communicated in an agile project.
-
Communication and Information-sharing Tools
After watching this video; you will be able to describe the types of tools used for communication and information sharing in agile teams including agile testers.
-
Creation of User Stories
After watching this video; you will be able to describe the techniques for collaborative creation of user stories; such as INVEST; and describe the components of a user story.
-
Definition of Done
After watching this video; you will be able to outline the importance of the definition of done in test levels and in different stages in the agile process.
-
Early and Frequent Feedback
After watching this video; you will be able to recall how the agile software development model incorporates early and frequent feedback.
-
Estimation of Testing Effort
After watching this video; you will be able to describe how to estimate testing effort in an agile project based on content and risk.
-
Extreme Programming (XP)
After watching this video; you will be able to recall the basic features of the XP agile approach.
-
Functional and Nonfunctional Black Box Test Design
After watching this video; you will be able to describe how functional and nonfunctional black box testing techniques can be applied in agile testing.
-
Identify Agile Testing Techniques and Tools
After watching this video; you will be able to practice identifying testing techniques in agile approaches and tools in agile projects.
-
Identify Testing Features in Agile Projects
After watching this video; you will be able to identify features of testing and the skill set of an agile tester in agile approaches .
-
Kanban
After watching this video; you will be able to recall the Kanban management approach that can be incorporated into agile projects.
-
Managing Risk Regression
After watching this video; you will be able to describe how risk regression in agile development can be managed using evolving manual and automated test cases.
-
Quality Risks in Agile Projects
After watching this video; you will be able to describe how quality risk analysis takes place in agile projects.
-
Release and Iteration Planning
After watching this video; you will be able to recall the agile concepts of release and iteration planning.
-
Role of an Agile Tester
After watching this video; you will be able to describe the role of a tester in an agile team.
-
Skills of an Agile Tester
After watching this video; you will be able to describe the skill set an agile tester should have.
-
Task Management and Tracking Tools
After watching this video; you will be able to describe the types of task management and tracking tools used in agile projects and available to agile testers.
-
Test Basis in Agile Projects
After watching this video; you will be able to describe the types of test bases; including user stories that are available to agile testers.
-
Test Development and Configuration Tools
After watching this video; you will be able to outline the tools available for agile test design; development; and execution and outline available configuration management tools; including virtualization tools for agile tests.
-
Test Levels
After watching this video; you will be able to describe test pyramids; testing quadrants; test levels; and testing types in the context of agile projects.
-
Test-driven and Behavior-driven Development
After watching this video; you will be able to describe the complementary techniques of test-driven development (TDD); acceptance test-driven development; and behavior-driven development used in agile projects.
-
The Twelve Principles of the Agile Manifesto
After watching this video; you will be able to outline the twelve principles of the Agile Manifesto; on which agile software development is based.
-
The Whole Team Approach
After watching this video; you will be able to describe the whole team approach promoted by agile software development.
-
Agile Test Levels
After watching this video; you will be able to describe test levels in the context of agile testing.
-
Agile Testing and Development Activities
After watching this video; you will be able to compare testing and development activities in traditional and agile approaches.
-
Agile Testing and Configuration Management
After watching this video; you will be able to describe testing and test configuration management in the context of agile projects.
-
Agile; Scrum; and Kanban
After watching this video; you will be able to distinguish between Agile; Scrum; and Kanban.
-
Behavioral Aspects in Applying Kanban
After watching this video; you will be able to select correct description of the behavioral aspect of interest on a Kanban project.
-
Creating an Online Kanban Board
After watching this video; you will be able to create an online Kanban board using the default template for your project.
-
Evolution of Methodologies
After watching this video; you will be able to recognize limitations of the waterfall approach.
-
Foundational Lean Concepts
After watching this video; you will be able to match foundational Lean concepts to their description.
-
Identifying and Reducing Wastes
After watching this video; you will be able to label example of waste to the waste category in Lean.
-
Introduction to Kanban Boards
After watching this video; you will be able to describe features of Kanban Boards.
-
Kanban and Pull
After watching this video; you will be able to describe characteristics of Kanban-pull system.
-
Kanban and Visual Signs in the Real World
After watching this video; you will be able to distinguish between visual display and visual control signs.
-
Kanban Drivers and Application
After watching this video; you will be able to recognize drivers and application of Kanban.
-
Kanban in IT and Software Development
After watching this video; you will be able to identify key considerations for Kanban in IT and software development.
-
Kanban Process: Creating a Kanban Board
After watching this video; you will be able to list activities in creating a Kanban board.
-
Key Concepts in Kanban Application
After watching this video; you will be able to match key concepts in Kanban application to their descriptions.
-
Lead Time and Cycle Time
After watching this video; you will be able to compare lead time to cycle time in a given scenario.
-
Lean and Kanban
After watching this video; you will be able to describe characteristics of Lean and Kanban.
-
Limiting WIP
After watching this video; you will be able to use Little's law for reducing lead time by limiting WIP.
-
Making Policies Explicit
After watching this video; you will be able to recognize examples for making policies explicit on Kanban projects.
-
Managing Flow
After watching this video; you will be able to match techniques for alleviating bottlenecks to their correct description.
-
Mindset and Cultural Change
After watching this video; you will be able to distinguish between cultures using the Schneider Culture model.
-
Software Development Life Cycle
After watching this video; you will be able to match SDLC phases to activities carried out in them.
-
The Kanban Process
After watching this video; you will be able to list steps in the Kanban Process in the correct order.
-
The Theory of Constraints
After watching this video; you will be able to describe principles of the Theory of Constraints.
-
The Visual Workplace
After watching this video; you will be able to select valid examples of visual workplace.
-
Ways to Limit WIP
After watching this video; you will be able to select most plausible way to limit WIP in a given scenario.
-
WIP and Flow
After watching this video; you will be able to differentiate between WIP and flow.
-
Working for Continuous Improvement
After watching this video; you will be able to label examples with the Kanban metric being used for monitoring and control.
-
Accumulation of Technical Debt
SCRUM is a software practice that can be used to keep technical debt in check. In this video; Brigitte Birze discusses how technical debt accumulates.
-
Business and Data Patterns for Splitting User Stories
SCRUM is a software practice which has some business and data patterns that can be used to breakdown User Stories. In this video; Brigitte Birze discusses how to use the business data patterns to breakdown large User Stories into small feature slices.
-
Committed and Involved Roles
In Agile; when practicing Scrum software development; roles are defined as committed or involved. Each role has a set of rules that need to be understood to complete a Scrum project successfully. In this video; Brigitte Birze uses the chicken and pig fable to define the two types of project members and the rules they must obey in Scrum development.
-
Encouraging Self-Organizing Team Behavior
The Scrum framework dictates that the Scrum Team should be cross-functional and self-organizing; choosing how best to accomplish their work without outside interference and with the encouragement of the Scrum Master. In this video; Brigitte Birze describes how the Scrum Master can encourage the Scrum Team to be self-organized and achieve optimal performance while upholding the Scrum Values.
-
Ending a Scrum Project
In Agile; a Scrum project ends when all the milestones are met in the Sprints; or the product owner and stakeholders decide to end the project. In this video; Brigitte Birze uses the roadmap release schedule to determine the end of a Scrum project.
-
Epics and User Stories
SCRUM is a software practice that enables breaking down of large User Stories known as EPICs. In this video; Brigitte Birze discusses how to break down EPICs into multiple User Stories.
-
Fat Product Backlog Items (PBI)
The Scrum Project's Fat Product Backlog items (PBIs) contain too much information; or too many loosely-related items; to be testable or made Sprint ready. In this video; Brigitte Birze identifies the shortcomings of fat PBIs containing oversized functionalities and ill-defined requirements; before suggesting they be split into smaller User Stories containing single slices of functionality subject to clear acceptance criteria.
-
Gathering Data and Insights to the Sprint Retrospective Meeting
In Scrum; the Sprint Retrospective Meeting is an opportunity for the team to review events from the last sprint and devise measurable actions that they can implement to improve performance. In this video; Brigitte Birze demonstrates how Scrum artifacts can provide information from the last sprint and give insights into how performance can be improved for the following sprints.
-
Heuristics for Splitting User Stories
SCRUM is a software practice which has some heuristics that can be used to determine how to breakdown User Stories. In this video; Brigitte Birze discusses how to use the heuristics to split the User Stories into small feature slices.
-
Identifying and Reducing Technical Debt
SCRUM is a software practice that enables you to mitigate technical debt. In this video; Brigitte Birze discusses how to identify and reduce technical debt.
-
INVEST User Story Guidelines
SCRUM is a software practice which uses the INVEST guidelines to set the quality of the User Stories. In this video; Brigitte Brize discusses how to use the INVEST guidelines while developing the User Stories.
-
Limiting Work in Progress
SCRUM is a software practice that encourages members of a team to work in parallel to ensure on time delivery. In this video; Brigitte Birze discusses how limiting work In-Progress helps the team stay focused; increasing their velocity and the quality of the work completed in each sprint.
-
Making the Complex Simple – Patterns for Splitting User Stories
SCRUM is a software practice which has some patterns that help to breakout the simple from complex and vice-versa and split the User Stories. In this video; Brigitte Birze discusses how to use simple and complex patterns to split the User Stories.
-
Managing the Sprint
SCRUM is a software practice that allows teams to work as a cohesive unit to reach a common goal. In this video; Brigitte Birze discusses how to manage the sprint cycle.
-
Principles Behind the Agile Manifesto
The Agile Manifesto was created based on 12 main principles. In this video; Brigitte Birze discusses and explains each of the 12 principles behind the Agile Manifesto.
-
Product Backlog Items (PBI)
The Scrum Project's Product Backlog items (PBIs) comprise multiple outstanding tasks; including User Stories; spikes; risks and defects; defining customer requirements which constitute the Product Backlog. In this video; Brigitte Birze defines multiple PBIs and explains how User Stories are defined; constructed; prioritized and groomed for inclusion into the Sprint Backlog during Sprint Planning.
-
Protecting the Sprint
In Agile; protecting the Sprints ensure that the Scrum framework functions properly. In this video; Brigitte Birze uses the Scrum values and rules to assist the Scrum Master; team members; and stakeholders to protect the Sprints.
-
Scrum and Culture Change
In Agile; implementing Scrum involves a fundamental transformation of the way work is managed in a company as emphasis changes from command and control to trust; communication; and collaboration. In this video; Brigitte Birze highlights the culture changes influenced by the different roles when implementing Scrum and discusses the recommended best practices when assigning Scrum roles.
-
Scrum and Deferring Detailed Specifications
In Scrum; deferring specifications helps ensure that the Scrum Team is focused on the highest priority items in the Product Backlog. In this video; Brigitte Birze highlights the advantages of deferring the definition of detailed specifications until a User Story is ready to be pulled into a Sprint and describes how the User Story changes throughout the project's lifecycle.
-
Scrum Values
In Agile; the five Scrum values; namely focus; courage; openness; commitment; and respect; can mean different things to team members. In this video; Brigitte Birze uses the five Scrum values to explain how to provide a foundation for teamwork and continuous improvement for a team.
-
Sizing User Stories
In software practices based on Scrum; there are various tools and options for sizing user stories in the product backlog. In this video; Brigitte Birze explains how to size user stories during the Product Grooming Meeting.
-
SMART Tasks
SCRUM is a software practice which uses SMART tasks while implementing the User Stories. In this video; Brigitte Brize discusses how to use SMART tasks to breakdown tasks while implementing the User Stories.
-
Team Velocity
SCRUM is a software practice that allows teams to record and track their velocity after each Sprint. In this video; Brigitte Birze discusses how to use a Teams Velocity to estimate the time required to complete backlog items in future releases.
-
The 4 SCRUM Artifacts
The four Scrum artifacts; namely the Product Backlog; the Sprint Backlog; the Burn Down Chart; and the Product Increment; are objects created during the Scrum Project to provide transparency to the project's and the Team's progress. In this video; Brigitte Birze expands on each artifact and explains its role in the context of the Scrum Team and Scrum Theory.
-
The Agile Manifesto
The Agile Manifesto is the umbrella over all of the Agile software frameworks. In this video; Brigitte Birze discusses why and how the Agile Manifesto was created and what the very important values are to finding Agile.
-
The Backlog Grooming Meeting
In Scrum; the Product Backlog Grooming Meeting is an opportunity for the team to review the top priority items in the product backlog. In this video; Brigitte Birze demonstrates the importance of product backlog grooming to help ensure that top level user stories are well understood and ready for the next sprint.
-
The Burn Down Chart
The daily updated Scrum Sprint Burn Down Chart depicts the Scrum Team's progress against an ideal Burn Down line mapped to the time and story points available. In this video; Brigitte Birze compares three Burn Down Charts and explains how blockages and spikes marking areas of uncertainty can prevent the Scrum Team accruing all its story points during a Sprint.
-
The Customer User Story
In Scrum; the consumer user stories in the product backlog need to bridge the communication gap between the customer and the technical team. In this video; Brigitte Birze demonstrates the importance of a customer user story that can clearly convey what is required so that the technical team can deliver value to the end user.
-
The Definition of Done (DoD)
In Scrum; the Definition of Done (DoD) tool is a checklist of the tasks that need to be completed during the software development process. In this video; Brigitte Birze demonstrates how the Definition of Done can be applied to all tasks and processes during software development for quality assurance.
-
The INVEST Estimable Criteria
In Scrum software practices; the 'E' in the INVEST guidelines for writing high quality user stories stands for Estimable. In this video; Brigitte Birze discusses estimating features; and how this affects the way in which user stories should be created.
-
The INVEST Independent Criteria
In Scrum software practices; the 'I' in the INVEST guidelines for writing high quality user stories stands for Independent. In this video; Brigitte Birze discusses why independence is important; and how this affects the way in which user stories should be created.
-
The INVEST Negotiable Criteria
In Scrum software practices; the 'N' in the INVEST guidelines for writing high quality user stories stands for Negotiable. In this video; Brigitte Birze discusses why being negotiable and collaborative is important; and how this affects the way in which user stories should be created.
-
The INVEST Small Criteria
In Scrum software practices; the 'S' in the INVEST guidelines for writing high quality user stories stands for Small. In this video; Brigitte Birze explains why user stories should be small; and how this affects the way in which user stories should be created.
-
The INVEST Testable Criteria
In Scrum software practices; a user story must have testable acceptance criteria on which the team; Product Owner; and customers can agree when it's "Done". In this video; Brigitte Birze uses the acceptance criteria to test the user story's implementation and determine when it is "Done".
-
The INVEST Valuable Criteria
In Scrum software practices; the 'V' in the INVEST guidelines for writing high quality user stories stands for Valuable. In this video; Brigitte Birze discusses the importance of value in user stories; and how this affects the way in which user stories should be created.
-
The Management Role
In Agile; the Scrum framework dictates that there's no Project Manager in the core Scrum roles. However; the manager is a stakeholder whose collaboration with the development team is critical to the successful execution and delivery of the final product. In this video; Brigitte Birze highlights the role of the Project Manager and their responsibilities in the Scrum environment.
-
The Product Backlog
The Scrum Project's Product Backlog; consisting of User Stories and other Product Backlog items (PBIs) defining final product features; is populated by the Product Owner following interaction with customers and stakeholders. In this video; Brigitte Birze explains how the Product Backlog constitutes a prioritized; ordered list of user product requirements to which the Scrum Team commits itself at Sprint Planning.
-
The Product Increment
The Scrum Product Increment is the current working software in potentially shippable form; demonstrating to the customer functionality developed during the Sprint that satisfies the Product Backlog's highest-priority items. In this video; Brigitte Birze compares Scrum Theory to the Waterfall Process and explains the value Scrum Theory offers by delivering Increments of working code at the end of each Sprint.
-
The Product Owner Role
In Scrum; the Product Owner is a key role; owning the product vision and providing a vital link between the stakeholders and the Development Team. In this video; Brigitte Birze describes how the Product Owner represents the interests of all stakeholders and collaborates with the Development Team to define the features of the product and prioritize the Product Backlog.
-
The Scrum Daily Standup Meeting
In Scrum software practices; Daily Standup meetings keep the project team updated on the project's progress. In this video; Brigitte Birze uses the Daily Standup meetings to explain the roles of the Scrum Master and Scrum Team as they keep up-to-date with the project's progress and eradicate impediments as they occur.
-
The Scrum Empirical Process
In Agile; the Scrum Empirical Process allows people from cross-functional groups to communicate and collaborate on a particular project. In this video; Brigitte Birze uses the Scrum Empirical Process to explain how inspection; adaptation; and transparency can improve how people work together toward common goals.
-
The Scrum Team Role
In software development using Scrum; a self-organized and empowered Scrum Team includes the expertise necessary to build and deliver the product increment at the end of each Sprint. In this video; Brigitte Birze describes the characteristics of a Scrum Team; their relationship with the other Scrum roles; and their responsibilities in ensuring the product is successfully delivered.
-
The ScrumMaster Role
In software development using Scrum; the Scrum Master owns the Scrum process and is responsible for protecting the Team during a Sprint and ensuring they live by the values and practices of Scrum. In this video; Brigitte Birze highlights the key responsibilities of the Scrum Master that allows the team to produce high quality results while following the Scrum process.
-
The Spike Product Backlog Item
SCRUM is a software practice that enables a team to gather information about an issue and come up with a strategy. In this video; Brigitte Birze discusses how to set clear objectives for a SPIKE to come up with the correct outcome for the issue.
-
The Sprint
In Agile; Sprints divide the lifespan of your project into manageable time-intervals for monitoring and reviewing of your Product Increment. In this video; Brigitte Birze uses Sprints to explain how the Product Increment is developed throughout the lifecycle of your project.
-
The Sprint Backlog
The Scrum Sprint Backlog consists of Product Backlog items (PBIs) selected by the Scrum Team; Product Owner; and Scrum Master during Sprint Planning for completion as "Done" in a single Sprint. In this video; Brigitte Birze explains how the Scrum Team commits to a Sprint Backlog comprising well-understood; actionable items; the completion of which is essential to the Sprint Goal.
-
The Sprint Planning Meeting
In Scrum software practices; the Sprint Goal and Sprint Backlog are created during the Sprint Planning meeting. In this video; Brigitte Birze uses the Sprint Planning meeting to determine the plan; as well as a list of items that must be completed during the Sprint.
-
The Sprint Retrospective Meeting
In Scrum software practices; the Sprint Retrospective meeting is held after a Sprint for the project team to review and reflect on how to become more effective. In this video; Brigitte Birze uses the Sprint Retrospective meeting to show how the Scrum Master; Scrum Team; and Product Owner can adapt their practices and behaviours toward continual process improvement.
-
The Sprint Review Meeting
In Scrum; the Sprint Review Meeting is an opportunity to demonstrate work completed in the last sprint to both the Scrum team and the stakeholders. In this video; Brigitte Birze demonstrates how the Sprint Review Meeting enables and encourages customer collaboration.
-
The Story Board
SCRUM is a software practice that enables teams to manage projects by breaking them down into simpler tasks. In this video; Brigitte Birze discusses the concept of the Story Board in SCRUM and how to use it to categorize User Stories and track the team’s progress during a sprint.
-
The Three Scrum Roles
In Agile; the Scrum framework defines three core roles with their own functions and ownership of specific parts of the process who work closely together to deliver increments of high value to the customer. In this video; Brigitte Birze highlights the key functions of the Product Owner; Scrum Team; and Scrum Master and how they combine during a Sprint.
-
The User Story Lifecycle
Teams can work on several projects using SCRUM. Each User Story has a lifecycle; it starts out as an idea which is written down; prioritized; estimated; and finally accepted into the Sprint Backlog where the feature is created in the Product Increment. In this video; Brigitte Birze discusses the lifecycle of a User Story.
-
User Story Breakdown
Using SCRUM; teams break down the project into smaller; easy to accomplish tasks. User Stories are created to capture features the user wants. In this video; Brigitte Birze discusses how to break a Project down into User Stories.
-
User Story Overview
SCRUM is a software development framework that allows a team to work in sync; yet separately to complete a User Story. In this video; Brigitte Birze discusses User Stories and how they capture the features and functionalities that the customer wants to see in the final product.
-
User Story Tasks
SCRUM is a software practice which has tasks that are used to describe how the team will implement a particular User Story and is used to measure the team’s progress and keep the entire team on track. In this video; Brigitte Brize discusses how to use tasks to implement a User Story.
-
What is Scrum?
Scrum is an incremental; iterative; Agile framework for software project development. In this video; Brigitte Birze discusses and explains how Scrum works and what some of the key concepts of Scrum are.
-
Why Do Teams Break Down User Stories into Tasks
In software practices based on Scrum; there are various tools and options for splitting user stories into tasks. In this video; Brigitte Birze explains how and why user stories are split into smaller user stories to fit into a single sprint.
-
Why Should User Stories be Small?
In Scrum; a high quality user story that is ready for use in a sprint should be sized appropriately. Smaller stories are easier for the team to understand; estimate and complete. In this video; Brigitte Birze demonstrates how smaller user stories boost the team’s productivity and avoid the potential bottlenecks that may occur when user stories are too large.
-
Retrospectives
After watching this video; you will be able to recall the role of retrospectives in an agile project and describe the role of testers within retrospectives.
-
Scaling Scrum
In Scrum; the Scrum of Scrums Meeting can be used to scale very large projects that have hundreds of people working on them. In this video; Brigitte Birze demonstrates how to scale Scrum to very large projects by breaking the work down between multiple Scrum groups which communicate with each other in the Scrum of Scrums Meeting.
-
Continuous Integration
After watching this video; you will be able to recall how continuous integration is implemented in an agile project; describe how testing occurs in this framework; and describe its benefits and challenges.
-
Exploratory Testing
After watching this video; you will be able to describe the importance of exploratory testing in agile testing.
-
Refactoring
In an Advanced Scrum; software development process; refactoring allows you to continuously improve the design of existing code without impacting the external functionality. In this video; Kevin McManus discusses the methodology of refactoring and unit tests; before demonstrating how to apply Extract Class refactoring to a code example.
-
Agile Software Development: TDD for Complex Systems
After watching this video, you will be able to describe the practices used for complex systems.
-
Agile Software Development: Test-driven Work
After watching this video, you will be able to describe test-driven work.
-
Agile Software Development: Code Visibility
After watching this video, you will be able to describe how TDD should be written in the same project as the code that is being tested.
-
Agile Software Development: Test-driven Development Best Practices
After watching this video, you will be able to identify TDD best practices.
-
Agile Software Development: Acceptance TDD
After watching this video, you will be able to describe what acceptance TDD is.
-
Agile Software Development: Developer TDD
After watching this video, you will be able to describe what developer TDD is.
-
Agile Software Development: Agile Testing Techniques
After watching this video, you will be able to compare TDD to other Agile testing techniques.
-
Agile Software Development: TDD Documentation
After watching this video, you will be able to recognize the importance of TDD documentation.
-
Agile Software Development: Test-driven Database Development
After watching this video, you will be able to describe test-driven database development.
-
Agile Software Development: BDD and TDD Approaches
After watching this video, you will be able to recognize BDD and TDD approaches to Agile development.
-
Agile Software Development: Test-driven Development Issues
After watching this video, you will be able to identify potential issues when implementing TDD in an Agile project.
-
Agile Software Development: Agile Collaboration
After watching this video, you will be able to describe Agile collaboration.
-
Agile Software Development: Seven Pillars of Collaboration
After watching this video, you will be able to describe the seven pillars of collaboration.
-
Agile Software Development: Effective Collaboration
After watching this video, you will be able to describe the three areas that lead to a successful collaboration.
-
Agile Software Development: Collaboration Techniques
After watching this video, you will be able to describe Agile collaboration techniques.
-
Agile Software Development: Collaboration Issues
After watching this video, you will be able to identify the issues of collaboration.
-
Agile Software Development: Agile Architecture Principles
After watching this video, you will be able to describe Agile architecture principles.
-
Agile Software Development: Enterprise Architecture
After watching this video, you will be able to describe enterprise architecture.
-
Agile Software Development: Agile Architecture Challenges
After watching this video, you will be able to identify potential Agile architecture challenges.
-
Agile Software Development: Agile Architectural Modeling
After watching this video, you will be able to identify Agile architectural modeling.
-
Agile Software Development: Apply Test-driven Development
After watching this video, you will be able to recognize how to apply TDD to Agile database development.
-
Agile Software Development: Red/Green/Refactor Cycle
After watching this video, you will be able to describe the red/green/refactor cycle.
-
Agile Software Development: Test-driven Development Best Practices
After watching this video, you will be able to identify TDD best practices.
-
Agile Software Development: Agile Architecture and Design
After watching this video, you will be able to describe Agile architecture and design.
-
Agile Software Development: Agile Architecture Principles
After watching this video, you will be able to describe the Agile architecture principles.
-
Agile Software Development: Agile Architecture Roles
After watching this video, you will be able to describe the role of Agile architecture.
-
Agile Software Development: Emergent Design
After watching this video, you will be able to describe emergent design and how it works with Agile software development.
-
Agile Software Development: Intentional Architecture
After watching this video, you will be able to describe the three objectives of intentional architecture.
-
Agile Software Development: Agile GUI Testing
After watching this video, you will be able to identify the elements of an Agile GUI testing process.
-
Agile Software Development: Testing Data Management
After watching this video, you will be able to identify approaches to test data management.
-
Agile Software Development: Applying Behavior-driven Development (BDD)
After watching this video, you will be able to identify how BDD can be applied to Agile development.
-
Agile Software Development: Agile Testing Lifecycle
After watching this video, you will be able to recognize considerations when implementing an Agile testing lifecycle.
-
Agile Software Development: UI Testing in Agile Projects
After watching this video, you will be able to recognize considerations when implementing UI testing in Agile projects.
-
Agile Software Development: Describe Behavior-driven Development
After watching this video, you will be able to describe the principles of behavior-driven development.
-
Agile Software Development: What Is Test-driven Development?
After watching this video, you will be able to describe what TDD is and how it works.
-
Agile Software Development: Test-driven Development Cycle
After watching this video, you will be able to identify the steps in the TDD cycle.
-
Agile Software Development: Common Codebase
After watching this video, you will be able to identify the benefits of sharing a common codebase.
-
Agile Software Development: Agile Testing Practices
After watching this video, you will be able to recognize the features of Agile testing practices.
-
Agile Software Development: Agile Coding Convention
After watching this video, you will be able to describe the rules for the Agile coding convention.
-
Agile Software Development: Pair Programming
After watching this video, you will be able to identify tips for implementing pair programming.
-
Agile Software Development: Collective Ownership
After watching this video, you will be able to identify tips for implementing collective ownership of code.
-
Agile Software Development: Code Refactoring
After watching this video, you will be able to describe how code refactoring can improve source code.
-
Agile Software Development: Test-first Programming
After watching this video, you will be able to describe test-first programming.
-
Agile Software Development: Behavior-driven Development (BDD)
After watching this video, you will be able to identify the features of BDD.
-
Agile Software Development: Continuous Integration
After watching this video, you will be able to describe how continuous integration works.
-
Agile Software Development: Collaborative Workspaces
After watching this video, you will be able to describe the benefits of collaborative workspaces.
-
Agile Software Development: Agile Simple Design
After watching this video, you will be able to describe what a simple design means.
-
Agile Software Development: Agile Scheduling
After watching this video, you will be able to describe the best practices to Agile scheduling.
-
Agile Software Development: Agile Risk Management
After watching this video, you will be able to describe how Agile can help with risk management.
-
Agile Software Development: Feature Estimation
After watching this video, you will be able to describe how feature estimation works.
-
Agile Software Development: Story Points and Agile Estimation
After watching this video, you will be able to identify techniques for estimating Agile stories.
-
Agile Software Development: Agile User Roles and Proxies
After watching this video, you will be able to recognize the purpose of Agile user roles and proxies.
-
Agile Software Development: Agile User Stories
After watching this video, you will be able to describe what an Agile user story is.
-
Agile Software Development: Agile Planning
After watching this video, you will be able to recognize additional approaches to Agile planning.
-
Agile Software Development: Agile Iterations
After watching this video, you will be able to identify the tasks to perform before executing iterations.
-
Agile Software Development: Identify Scrum Values
After watching this video, you will be able to identify features of Scrum for Agile software development.
-
Agile Software Development: Large-scale Scrum
After watching this video, you will be able to describe the two different large-scale Scrum frameworks.
-
Agile Software Development: Estimating an User Story
After watching this video, you will be able to describe how to estimate an Agile user story.
-
Agile Software Development: Evaluating a User Story
After watching this video, you will be able to describe how to evaluate an Agile user story.
-
Agile Software Development: Scrum Artifacts
After watching this video, you will be able to describe the three Scrum artifacts and the role they play.
-
Agile Software Development: Backlog Refinement
After watching this video, you will be able to describe what backlog refinement is.
-
Agile Software Development: Sprint Review
After watching this video, you will be able to describe the sprint review and retrospective.
-
Agile Software Development: Daily Scrum
After watching this video, you will be able to describe the purpose of a daily Scrum.
-
Agile Software Development: Sprint Planning
After watching this video, you will be able to describe sprint planning and its importance.
-
Agile Software Development: Scrum Workflow
After watching this video, you will be able to describe the Scrum workflow.
-
Agile Software Development: Scrum of Scrums
After watching this video, you will be able to describe how Scrum of Scrums helps improve team coordination.
-
Agile Software Development: Scrumban
After watching this video, you will be able to describe Scrumban and how it is used.
-
Agile Software Development: Scrum Values
After watching this video, you will be able to identify Scrum values and what they mean.
-
Agile Software Development: Scrum Limitations
After watching this video, you will be able to identify the limitations of Scrum.
-
Agile Software Development: Scaling Agile Projects
After watching this video, you will be able to identify issues with scaling Agile projects.
-
Agile Software Development: Team Progression
After watching this video, you will be able to monitor and communicate team progress.
-
Agile Software Development: Documentation Best Practices
After watching this video, you will be able to identify best practicies for documentation in an Agile Project.
-
Agile Software Development: Agile Project Documentation
After watching this video, you will be able to match typical Agile project documentation with descriptions.
-
Agile Software Development: Types of Feedback
After watching this video, you will be able to recognize the type of feedback provided by reviews in Agile projects.
-
Agile Software Development: Charts
After watching this video, you will be able to recognize different charts that provide feedback during a project.
-
Agile Software Development: Managing Iterative Development
After watching this video, you will be able to recognize ways to manage change, quantity and risk during iterative development.
-
Agile Software Development: Iterative Development
After watching this video, you will be able to recognize how to use meetings and charts to support communication and collaboration during iterative development.
-
Agile Software Development: Tracking an Iteration
After watching this video, you will be able to identify how to track an iteration.
-
Agile Software Development: Iteration Balancing
After watching this video, you will be able to recognize how developers select tasks and perform iteration balancing.
-
Agile Software Development: Implementing Agile Modeling
After watching this video, you will be able to describe how to implement Agile modeling.
-
Agile Software Development: Agile Modeling
After watching this video, you will be able to identify features of Agile modeling.
-
Agile Software Development: Iteration Planning Phase
After watching this video, you will be able to complete activities common to the iteration planning phase of an Agile software development project.
-
Agile Software Development: Release Planning Phase
After watching this video, you will be able to complete activities common to the release planning phase of an Agile software development project.
-
Agile Software Development: Commitment-driven Iteration Planning
After watching this video, you will be able to recognize the activities of commitment-driven iteration planning.
-
Agile Software Development: Velocity-driven Iteration Planning
After watching this video, you will be able to list the steps in velocity-driven iteration planning.
-
Agile Software Development: Agile Buffering Plans
After watching this video, you will be able to identify project buffers in a given scenario.
-
Agile Software Development: Creating a Release Plan
After watching this video, you will be able to recognize how to create a release plan.
-
Agile Software Development: Agile Model Driven Development
After watching this video, you will be able to recognize how Agile model driven development (AMDD) activities fit into the agile software development process.
-
Agile Software Development: Extreme Programming Practices
After watching this video, you will be able to describe the extreme programming practices and the areas in which they are grouped.
-
Agile Software Development: Extreme Programming Concepts
After watching this video, you will be able to describe the key concepts to extreme programming.
-
Agile Software Development: Extreme Programming
After watching this video, you will be able to describe what extreme programming is and how it improves software quality.
-
Agile Software Development: Identify Agile Principles
After watching this video, you will be able to identify Agile software development features.
-
Agile Software Development: Issues Transitioning to Agile
After watching this video, you will be able to recognize the issues organizations can face when applying Agile principles in given scenarios.
-
Agile Software Development: Agile Software Development Considerations
After watching this video, you will be able to recognize factors to consider when moving to an Agile software development methodology.
-
Agile Software Development: Agile Management
After watching this video, you will be able to describe incremental and iterative development (IID).
-
Agile Software Development: Agile Methods
After watching this video, you will be able to describe the Agile methods and the design-code-test loop.
-
Agile Software Development: Agile Information Radiator
After watching this video, you will be able to describe what an Agile information radiator is and how it works.
-
Agile Software Development: Agile Software Development Life Cycle
After watching this video, you will be able to describe the Agile software development life cycle.
-
Agile Software Development: Agile Best Practices
After watching this video, you will be able to identify Agile software development best practices.
-
Agile Software Development: Agile Values
After watching this video, you will be able to identify the values of Agile software development.
-
Agile Software Development: Agile Principles
After watching this video, you will be able to identify the principles of Agile software development.
-
Agile Software Development: Advantages of Agile
After watching this video, you will be able to identify the advantages of Agile over the waterfall approach.
-
Agile Software Development: Why Agile?
After watching this video, you will be able to describe why organizations should introduce Agile.
-
Agile Software Development: History of Agile Software Development
After watching this video, you will be able to describe what Agile software development is and its history.
-
Agile Software Development: Scrum Roles
After watching this video, you will be able to identify the roles in the Scrum framework.
-
Agile Software Development: Scrum Software Development
After watching this video, you will be able to describe what Scrum software development is used for.
-
Agile Software Development: Identify Agile Methodologies
After watching this video, you will be able to identify the popular Agile methodologies.
-
Agile Software Development: Disciplined Agile Delivery (DAD) Framework
After watching this video, you will be able to identify the main principles of the DAD framework.
-
Agile Software Development: Essential Unified Process (EssUP)
After watching this video, you will be able to identify the main features of EssUP.
-
Agile Software Development: Agile Unified Process
After watching this video, you will be able to identify what occurs at each stage of an AUP project.
-
Agile Software Development: Dynamic Systems Development Method (DSDM)
After watching this video, you will be able to identify the main principles of DSDM.
-
Agile Software Development: Crystal Methodology
After watching this video, you will be able to recognize the features of Crystal.
-
Agile Software Development: Feature-driven Development (FDD)
After watching this video, you will be able to identify the features of FDD.
-
Agile Software Development: Kanban Development
After watching this video, you will be able to identify the main features of the Kanban approach to agile software development.
-
Agile Software Development: Adaptive Software Development (ASD)
After watching this video, you will be able to recognize what happens at the three phases in an ASD project.
-
Agile Software Development: Lean Software Practices
After watching this video, you will be able to describe the lean software practices.
-
Agile Software Development: Lean Software Development
After watching this video, you will be able to recognize the seven principles of lean software development.