I promised this post a week ago. Failure bow. Forecast over promises. I've already covered many issues that affect software quality - see: https://www.linkedin.com/posts/marklevison_yesterday-we-looked-at-how-poor-understanding-activity-7293324567647858688-Y8l9 and https://www.linkedin.com/posts/ma - ThreadSky

mlevison.bsky.social • 9 days ago

I promised this post a week ago. Failure bow. Forecast over promises.

I've already covered many issues that affect software quality - see: https://www.linkedin.com/posts/marklevison_yesterday-we-looked-at-how-poor-understanding-activity-7293324567647858688-Y8l9 and https://www.linkedin.com/posts/ma

Comments

mlevison.bsky.social•9 days ago

Some clever wag will respond that most of this boils down to the fact we've ignored the XP Technical Practices for too long. Both true and unhelpful at the same time.

The biggest sin by far? Building on Technical Debt without making any effort to remediate it.

2 of 7 #EffectiveScrum

mlevison.bsky.social•9 days ago

An excellent paper from the team at CodeScene really brings this home: https://codescene.com/hubfs/web_docs/Business-impact-of-code-quality.pdf When the code is already messy and we continue to try to do new feature work or fix a bug, we're 15 times more likely to have defects than if we were workin

mlevison.bsky.social•9 days ago

….When the existing code is messy and we fix a bug, we have a high risk of creating a new bug. Whack-a-mole?

What other technical factors are there?
- Lack of automated test cases a code bases with few tests, all changes are high risk.

4 of 7 #EffectiveScrum

mlevison.bsky.social•9 days ago

Ignoring Test Case Failure - With some troublesome tests, they fail, and the failure isn't easily understood. This should, of course, be a warning that the system is unreliable or at least that the test case covers too much. Instead, many teams tag it as ignored and move on.

5 of 7 #EffectiveScrum

mlevison.bsky.social•9 days ago

Long-lived code branches and their partner in crime Pull Requests. The longer the branch lives, the harder it is to merge into main. The delays of both branches discourage refactoring. Missed opportunities for refactoring increase our technical debt.

6 of 7 #EffectiveScrum

mlevison.bsky.social•9 days ago

could spend an entire workshop day covering this mess. Without delving into solutions, what other technical factors affect quality?

Next time, we will work on the Team and Collaboration. (I'm not promising tomorrow)

Sign up for newsletter: https://agilepainrelief.com/newsletter

7 of 7 #Effective

Comments

Posting Rules

Reply