Dependencies limit our ability to act swiftly. Dependencies limit agility. And we find ourselves surrounded by dependencies. What do we do? We only have two real choices. We can either break dependencies. Or we can manage them. How do we go about doing it? And which ones do we manage and which ones do we strive to break? Here’s an interesting take on this.
What’s hurting? Unrealistic plans, lack of commitment, priorities that don’t get done, late delivery, change, dependencies, and ever increasing amount of risk? Maybe all of these, or maybe some of these. How do you go about fixing these? You may end up fixing your delivery, but what if you still end up building the wrong thing? How do we handle both of these issues? Read on.
How do Scrum Masters provide value to the Product Owners? How do they coach the Product Owners? Well, they help them understand the time boxes. They help them understand the benefits of a healthy Product Backlog, and show them how does a healthy Product Backlog can help Product Owners what they want. And a few other very important things. Have a look.
On surface, the daily Scrum is a fairly simple event. But a lot of teams struggle to take the full advantage of the opportunity it presents. Do you know what’s the purpose and outcome of your Daily stand up? Here are 15 tips you can use to improve your daily Scrum.
What are the typical risks that agile teams face that may jeopardise the sprint or worse the agile process as a whole? How do you reduce ambiguity in requirements, and ensure that you deliver highest possible value? And deliver that as a quality piece of work? Here are top 5 risks, and how Agile teams can mitigate these.
What should be your Sprint length? Are your sprints too long, or too short? How do you know? Should you change Sprint length? All good questions. Here are a few answers.
Legacy code is full of mysteries. What about that weird if statement that seems to do nothing anymore (it was introduced as a workaround for a creepy bug that has now been fixed). All the history that’s often lost over time is what causes issues. Eventually we end up in a mess. What can we learn from forensic psychology that can make our job easier? Here’s an interesting perspective.
How do we build sustainable confidence in the long term health of products in the DevOps pipeline? What if we monitor results test analysis and aggregate results over multiple tests and release cycles? How do we go about doing that? What steps do we take? Read on.
AGILE
How to Get Rid of Evil Dependencies
Dependencies limit our ability to act swiftly. Dependencies limit agility. And we find ourselves surrounded by dependencies. What do we do? We only have two real choices. We can either break dependencies. Or we can manage them. How do we go about doing it? And which ones do we manage and which ones do we strive to break? Here’s an interesting take on this.
leadingagile.com
Fix These 7 Things That are Eating Your Budget
What’s hurting? Unrealistic plans, lack of commitment, priorities that don’t get done, late delivery, change, dependencies, and ever increasing amount of risk? Maybe all of these, or maybe some of these. How do you go about fixing these? You may end up fixing your delivery, but what if you still end up building the wrong thing? How do we handle both of these issues? Read on.
rallydev.com/blog
How Scrum Masters Serve the Product Owner?
How do Scrum Masters provide value to the Product Owners? How do they coach the Product Owners? Well, they help them understand the time boxes. They help them understand the benefits of a healthy Product Backlog, and show them how does a healthy Product Backlog can help Product Owners what they want. And a few other very important things. Have a look.
scrumalliance.org
15 Tips to Improve Your Daily Stand Up
On surface, the daily Scrum is a fairly simple event. But a lot of teams struggle to take the full advantage of the opportunity it presents. Do you know what’s the purpose and outcome of your Daily stand up? Here are 15 tips you can use to improve your daily Scrum.
blog.scrum.org
TEAM
How Agile Teams Reduce Risk?
What are the typical risks that agile teams face that may jeopardise the sprint or worse the agile process as a whole? How do you reduce ambiguity in requirements, and ensure that you deliver highest possible value? And deliver that as a quality piece of work? Here are top 5 risks, and how Agile teams can mitigate these.
agileconnection.com
What’s a Good Sprint Length?
What should be your Sprint length? Are your sprints too long, or too short? How do you know? Should you change Sprint length? All good questions. Here are a few answers.
blog.3back.com
DEVELOPER
What’s Common Between Code and Crime Scene?
Legacy code is full of mysteries. What about that weird if statement that seems to do nothing anymore (it was introduced as a workaround for a creepy bug that has now been fixed). All the history that’s often lost over time is what causes issues. Eventually we end up in a mess. What can we learn from forensic psychology that can make our job easier? Here’s an interesting perspective.
dzone.com/articles
DEVOPS
Why do Continuous Test Monitoring?
How do we build sustainable confidence in the long term health of products in the DevOps pipeline? What if we monitor results test analysis and aggregate results over multiple tests and release cycles? How do we go about doing that? What steps do we take? Read on.
devops.com
Share this: