Posts Tagged ‘technical debt’
What To Do When Your Team Can’t Finish its Sprint
Having a Team that just can’t finish what it agreed to do in a Sprint is, by far, one of the more painful situations we have in Scrum. This situation may make the Team Members feel bad about themselves, and they may want to do these Stories no matter what…
Read MoreSo What Is Technical Debt in Scrum, Anyways?
Technical Debt is what makes code hard to work with. It is an invisible killer of software and must be aggressively managed. In this post, I define Technical Debt and describe some of the issues…
Read MoreAgile Consulting: A Tale of Two Risks
My work as an Agile Consultant comes in many shapes and sizes. In this consultant role, I work on the skills and standards needed for my clients to be proficient in their line of work. On this particular occasion, I was working with a client (we’ll call this client Acme Marketing and Technology) who delivers technology and marketing services in a Scrum/Agile-like manner…
Read More5 Tips to Prevent Technical Debt
5 Tips to Prevent Technical Debt: It’s a given. Technical Debt kills a Team’s code. So, what can the Team do about it? How can the Team prevent the development of Technical Debt from creeping into its code? Here’s 5 Ways to get your Team on the right track to preventing Technical Debt.
Read MoreThe 4 Types of Technical Debt
The 4 Types of Technical Debt
Technically speaking (pun intended), we can define Technical Debt as deficiencies in the code, technical documentation, development environments, 3rd-party tools and development practices, which makes the code hard for the Team to change.
A Strategy for Working With Ugly Code
I defined Ugly Code as Code that is UnProtected by Tests, Ill-Structured, and UnReadable. Ugly Code is Code that has lots of Technical Debt…
Read MoreClean Code, Ugly Code, Technical Debt and CleanUp Stories
One of the things most Agilists harp on is the need for Clean Code: Code that can be easily extended and maintained, and that Coders shouldn’t be afraid to work with. But, what does this really mean?
Read MoreWhen a Team Can’t Reach Their Sprint Goal
One of the most common issues that arises with a Scrum Team is that the content of a Sprint needs to change during the Sprint. This happens for a number of reasons, and this excerpt will touch on one reason this may occur: The team can’t do what it agreed to.
Read MoreTechnical Debt: A Horror Story
This is an excerpt from Dan Rawsthorne’s upcoming book “Project Management with Scrum”. Dan is a Certified Scrum Trainer for 3Back, a world-leader in Scrum development, and co-author of “Exploring Scrum: The Fundamentals”. This excerpt will give you a basic understanding of technical debt as well as a glimpse into an real-world example of technical debt overwhelming a team.
Read MoreAcceptance-Based Stories and Ideal Effort
This is an excerpt from the recently released second edition of Exploring Scrum: The Fundamentals by Dan Rawsthorne and Doug Shimp. The authors of “Exploring Scrum” are both Certified Scrum Trainers for 3Back, a world-leader in Scrum development. There is no accepted definition of what a StoryPoint represents, other than that it is a unitless, relative…
Read MoreTeam Velocity and Story Points in Scrum
Learn more about Scrum and Team Velocity by reading a short piece from Dan Rawsthorne and Doug Shimp’s newly released second edition of “Exploring Scrum: The Fundamentals”
Read MoreLayering Agility and Technical Debt Seminars at Directions 2012 Conference
We just completed a couple of talks at the Directions 2012 conference in Phoenix, AZ. Both of these topics are described in more depth in our book on Exploring Scrum: The Fundamentals.
Read More