Join Harrison Ferrone for an in-depth discussion in this video Handling leapfrogging bugs, part of Agile Development Practices.
- [Instructor] Now that we've talked…about test-driven development and manual testing,…we're going to take a detour into something…I call leapfrogging bugs.…The basic idea is this.…Let's say we have Sprint 1 finished up…and we're starting Sprint 2 right away.…Ideally, we'd have done some quality assurance…testing as part of the end of Sprint 1.…But it's not always that easy.…There will always be bugs that come up after the fact.…Now we're in the middle of Sprint 2…and a few bugs and change requests come…back into the backlog.…
Now here's the problem.…We're already doing new work on a new sprint deliverable,…and the rules of agile are designed…to keep sprint tasks locked in once the sprint starts.…This stops them getting added to on-the-fly…and generally making everybody angry.…So how do we deal with this?…First, it's a good idea to record…what version specific bugs are found in.…This is just good practice and common sense.…Second, you want to address bugs as early as possible.…The product owner or client could decide…
LinkedIn Learning (Lynda.com) is a PMI Registered Education Provider. This course qualifies for professional development units (PDUs). To view the activity and PDU details for this course, click here.
The PMI Registered Education Provider logo is a registered mark of the Project Management Institute, Inc.
- Planning and design
- Developing flexible architecture
- Documentation considerations
- When to optimize
- Determining velocity
- Agile programming techniques
- Testing and handling bugs
- Structuring a release pipeline