Category: Dev Tools


Scrum and tech debt

A Scrum Alliance article has this to say about tech debt and how to manage it in the Scrum workflow

Servicing the technical debt
The first step in servicing the debt is to identify any such issues and register them — making the debt visible for the team. These could be made part of the product backlog or even be part of a separate technical debt backlog for purposes of tracking. The team can then evaluate and prioritize, taking into account the effort required and the “pain” caused by the technical debt and its frequency. The product owner would need to make a conscious decision whether the “economics” justifies the cost of the technical debt. It has to be kept in mind that not all technical debt need be repaid; e.g., one can live with issues relating to a product nearing its end of its life. However, it is important during this time that technical debt is not accumulated, since that would only cripple the system

From David Hawks, CEO of Agile Velocity, who sums it up like this

In the sprint I believe all work should be made visible. I probably wouldn’t put points on it since it isn’t part of the release plan. Also I encourage folks to track a separate tech debt backlog to make that backlog of work visible and prioritized

In other words, the Product Backlog should still only be populated with user stories, and user stories should always be testable and estimable, but you also want a Tech Debt Backlog populated with tech debt stories that aren’t necessarily testable or estimable. This separate Tech Debt Backlog makes it clear to the testers that this isn’t something they need to test, and it’s a useful way of capturing work that might normally be a spike time box or just skunkworked outside the workflow.

See more

We’ll ask for estimates and make them deadlines

We'll ask for estimates and then treat them as deadlines - We'll ask for estimates and then treat them as deadlines  Dr Evil and minions

How to check if nuget package files failed to be added to your checkin (Visual Studio 2013)

package_management

TFS Hates Nuget

In Source Control Explorer, go to the packages folder, right-click and Compare server to local to see all the package files that didn’t get checked in.  Ctrl-Click all the files it found locally but not on server and right-click Add, then check in again.

Google Translate for Managementspeak-to-English

From Google:

Our engineers have worked tirelessly for the past two years to fight this epidemic that has plagued efficiency in the business world. Today, we are launching a new alpha feature in Google Apps for Business, Jargon-Bot. Jargon-Bot will automatically detect business jargon or business speak and provide you with real-time translation in plain English. Yes, simple, plain English. Jargon-Bot has been integrated across the entire suite of Google Apps so that next time you are on an IM chat with your manager, it will help you recognize and say no to unrealistic expectations. When you receive an e-mail from your supplier, Jargon-Bot won’t let you get ripped off by demystifying the fine print. And even when you’re on a Google+ Hangout with your accounting team, jargon-bot will be by your side, so you don’t break your e-reader when you have to help “close the books.”

We can only wish…

Refactoring

© 2017 Robert Corvus