How can we help business teams embrace some aspects of agility? How can we help them align business and technology goals and improve communication? How can they conduct Retrospective especially from business and customer perspective? What can they learn from Agile to accentuate value delivery? Here are some good ideas. http://agileconnection.com
We all strive to help our teams to be ever more happy. But how do we know they are happy? If you can’t measure something, how do you know you are getting better? How do we measure team happiness? Sounds interesting, right? Here are some quick ideas on do we know if our teams are happy or not. agilecomplexificationinverter.blogspot.com
Does #NoEstimates really mean “absolutely no estimates”? Is it fair to say that all means of predicting the future are “estimation” in some way. And thus makes them inherently bad? Or is it primarily about budgeting projects differently from conventional ways? Here’s an interesting perspective. http://ronjeffries.com
How do you deal with non-functional requirements (NFRs) which apply at the product or portfolio level? Would you deal with these differently compared to NFRs at a release or Product Backlog Item (PBI) level? Here are a few useful tips. These are described from a SaFe perspective, but regardless of the framework used, these provide a good way to organise NFRs.
Product Owner is a common Agile role, more of a Scrum role to be precise. However some leading companies, with history of lean practices, employ a role called the Product Champion. It’s used by 3M and Disney to name a few. What are the differences? Have a look. http://ronjeffries.com
Have you been part of a Retrospective where you didn’t have any facilitator? Can it actually work without a facilitator? Well, dialogue sheets can help. Dialogue sheet retrospectives are facilitator less. And what’s more? You can use the similar technique for Agile team kickoff, and Planning. Here are some very useful dialogue sheets.
Most technology companies try to solve most of the problems with technology. Sometimes this is exactly what solves the problem. But not always, as they can go way overboard in leveraging technology. Agile and Scrum tools do have their advantages, and do have their downside as well. Here’s an interesting perspective on how Agile and Scrum tools may affect Agility in an adverse way.
Complexity is one of the major cause of problems in software development and maintenance. It leads to unreliability, late delivery, lack of security and poor performance. So how do we tame complexity? What’s even more important to understand is that what causes the code to become too complex in the first place? Once we understand that, we can avoid those traps. Here are a 9 things to watch out for. https://dzone.com
AGILE
Agile Techniques for Business Teams
How can we help business teams embrace some aspects of agility? How can we help them align business and technology goals and improve communication? How can they conduct Retrospective especially from business and customer perspective? What can they learn from Agile to accentuate value delivery? Here are some good ideas.
http://agileconnection.com
How to Measure Team Happiness?
We all strive to help our teams to be ever more happy. But how do we know they are happy? If you can’t measure something, how do you know you are getting better? How do we measure team happiness? Sounds interesting, right? Here are some quick ideas on do we know if our teams are happy or not.
agilecomplexificationinverter.blogspot.com
Is It All a Matter of Definition Only?
Does #NoEstimates really mean “absolutely no estimates”? Is it fair to say that all means of predicting the future are “estimation” in some way. And thus makes them inherently bad? Or is it primarily about budgeting projects differently from conventional ways? Here’s an interesting perspective.
http://ronjeffries.com
How to Deal With Non Functional Requirements
How do you deal with non-functional requirements (NFRs) which apply at the product or portfolio level? Would you deal with these differently compared to NFRs at a release or Product Backlog Item (PBI) level? Here are a few useful tips. These are described from a SaFe perspective, but regardless of the framework used, these provide a good way to organise NFRs.
http://blogs.versionone.com
PRODUCT OWNER
Do We Need a Product Owner or a Product Champion?
Product Owner is a common Agile role, more of a Scrum role to be precise. However some leading companies, with history of lean practices, employ a role called the Product Champion. It’s used by 3M and Disney to name a few. What are the differences? Have a look.
http://ronjeffries.com
TEAM
How to Run a Retrospective Without a Facilitator?
Have you been part of a Retrospective where you didn’t have any facilitator? Can it actually work without a facilitator? Well, dialogue sheets can help. Dialogue sheet retrospectives are facilitator less. And what’s more? You can use the similar technique for Agile team kickoff, and Planning. Here are some very useful dialogue sheets.
http://www.softwarestrategy.co.uk
Do Tools Make Us Less Agile?
Most technology companies try to solve most of the problems with technology. Sometimes this is exactly what solves the problem. But not always, as they can go way overboard in leveraging technology. Agile and Scrum tools do have their advantages, and do have their downside as well. Here’s an interesting perspective on how Agile and Scrum tools may affect Agility in an adverse way.
http://www.agileadvice.com
DEVELOPER
How to Overcome Complexity to Become a Better Developer
Complexity is one of the major cause of problems in software development and maintenance. It leads to unreliability, late delivery, lack of security and poor performance. So how do we tame complexity? What’s even more important to understand is that what causes the code to become too complex in the first place? Once we understand that, we can avoid those traps. Here are a 9 things to watch out for.
https://dzone.com
Share this: