In This Issue
- We Need Agility, Not Just Agile
Read Alex Adamopoulos’ Blog Post - Is Agility Making You Less Innovative?
Read Luke Hohmann’s Blog Post - Empirical Process Control: Why Scrum Works
Read Barry Hawkins' Blog Post - The Cause of Poor Software Quality
Read Alan Shalloway’s Blog Post - Success = Results - Expectations
Read Matt Badgley's Blog Post
We Need Agility, Not Just Agile
Have you ever asked yourself why you believe agile is right for your organization? Alex Adamopoulos suggests that many companies are actually seeking agility in the business lifecycle. While this can be achieved through agile practices, it’s important to understand what you are trying to solve first and then leverage the right practices to help your organization get there.
Read Alex Adamopoulos’ Blog Post.
Is Agility Making You Less Innovative?
Innovation is messy and risky. So it’s not hard to see why agile teams might go down the slippery slope to less innovation. But Luke Hohmann suggests the use of roadmaps as an antidote to the lack of innovation that can creep into some agile teams.
Read Luke Hohmann’s Blog Post.
Empirical Process Control: Why Scrum Works
Empirical process control sounds like a mouthful. But all it requires is three basic elements: transparency, inspection and adaptation. In his blog, Barry Hawkins explains how scrum was specifically designed to enable those three basic elements for successful software development.
Read Barry Hawkins' Blog Post.
The Cause of Poor Software Quality
Do you ever work on too many things at once? Do you work on things in the wrong order? Do you not fully understand how to write code incrementally? If you (or a team member) answered “Yes” to any of these questions, then you’ll want to read Alan Shalloway’s three-part blog series on how to improve software quality.
Read Alan Shalloway’s Blog Post.
Success = Results - Expectations
Does success hinge on knowing everything up front? If you’re stuck in a waterfall environment, you might think so. In his two-part blog series, Matt Badgley explains how software delivery teams (and their customers) can find success throughout a project by applying four basic agile concepts – none of which is complete, up front requirements.
Read Matt Badgley's Blog Post.
