Learn about the definition of technical debt and how to help your team avoid it. Angela describes how the team can recognize the two major contributors to minimizing technical debt and some ways to overcome it.
- What happens when teams work fast and furious…without an eye towards the product vision and road map,…and they take shortcuts,…rather than doing it right the first time?…Well, they typically create a lot of rework and pain,…and in Agile, it's no different.…Technical debt is the cost incurred for cutting corners…in the short term, and Agile teams can create more…than an appropriate amount of it,…when only focused on the current sprint.…When too much technical debt happens on a solution,…over time, the team's pace and velocity slows down.…
The shortcuts taken earlier can create more work to unravel…and refactor, as the team adds more functionality.…Some technical debt is good and strategic, and typically…this is the case when there are major unknowns,…and things like experiments and prototyping,…where the team is taking shortcuts to learn…and later commit to a technical path.…In this case, it's all about the learning and experimenting.…Well there are two major contributors…to minimizing technical debt.…
First, is having a solid…
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.
- Rallying your team around the product vision
- Creating an agile product roadmap
- Creating a release plan focused on value
- Breaking down features
- Setting up, creating, and analyzing user story maps
- Collaborating on the big picture
- Leveraging user stories
- Prioritizing the product backlog
- Working with your team
- Defining what "ready" and "done" mean
- Avoiding technical debt
- Guiding your team through estimating exercises
- Making sprint planning and standup meetings beneficial