Feature Toggling can help a team deliver new functionality rapidly but safely. This allows teams to modify system behaviour without changing code. What are major types of feature toggles? How long the feature toggle should live? How dynamic the toggling decision must be? How do we constrain the number of toggles in our system? Read on.
We know the value of the feedback loops. That’s why we work in shorter iterations, do Retrospectives, automate tests, and release often. Direct feedback from team members helps bring to light things that make the team members better. But how do we provide direct feedback to each other? That’s scary. Difficult. Here are a few techniques you can use.
Accidental agility is when the agile processes are native to what you have in place at a certain organisation. These work out well. These work without everyone fully understanding exactly why do these work. But you like the success. Then you try those at another place, and those doesn’t work, at all. Rather it fails, miserably. What can we do to learn from success and make sure we understand why it may not work at other places?
When do we do user acceptance testing in Agile? A common pattern is to do user acceptance testing once all the code has been developed and integrated. Or worse, only do that user acceptance testing in production, just before release. How would you eliminate these patterns? When to do the user acceptance testing? Who should do the user acceptance testing in the first place? Have a look.
Accidental agility is when the agile processes are native to what you have in place and they work without everyone fully understanding exactly why. You like it and believe it works. But then you try that at another place, and it doesn’t work. Rather it fails, miserably. What can we do to learn from success and make sure we understand why it may not work at other places?
How do you become a great Product Owner? Do you have a product vision, that you’ve truly embraced? How do you communicate? Do you know your business model? What do you really focus on? How good are you at saying no? Read on to explore 18 characteristics to become a great Product Owner.
I am a Business Analyst but I am expected to be a proxy for the Product Owner, but I have neither the perspective nor the buy-in from the business to do this. What do I do? Some developers on the team think, why do we need the business analyst, we can just talk to the business and ask what they want? Experienced business analysts who have the skills to analyse processes and value chains think, I am expected just to produce requirements instantly, I don’t have the time to do my job in Agile? So how does the role of the business analyst work then? Here a interesting perspective? (video)
Many organisations have embraced devops concepts, and it’s changed the way business is done. How do you get really good at that? How do end the culture of fear? How do you find and retain knowledge and talent? What should you really focus on? Read on.
How do we break that bad habit? We all have one, or many. Some are potentially career limiting. Others affect personal life. Whether it’s weak interpersonal skills, a tendency to procrastinate, or good-but-not-great technical prowess, one of the biggest impediments to our progress is how do we rid ourselves of that bad habit? Here’s a trick you can use.
AGILE
How to Get Feature Toggles Right?
Feature Toggling can help a team deliver new functionality rapidly but safely. This allows teams to modify system behaviour without changing code. What are major types of feature toggles? How long the feature toggle should live? How dynamic the toggling decision must be? How do we constrain the number of toggles in our system? Read on.
martinfowler.com
How to Enable Team Feedback? To Each Other.
We know the value of the feedback loops. That’s why we work in shorter iterations, do Retrospectives, automate tests, and release often. Direct feedback from team members helps bring to light things that make the team members better. But how do we provide direct feedback to each other? That’s scary. Difficult. Here are a few techniques you can use.
agileconnection.com
What to Learn From Accidental Agility?
Accidental agility is when the agile processes are native to what you have in place at a certain organisation. These work out well. These work without everyone fully understanding exactly why do these work. But you like the success. Then you try those at another place, and those doesn’t work, at all. Rather it fails, miserably. What can we do to learn from success and make sure we understand why it may not work at other places?
leadingagile.com
4 User Acceptance Testing Anti Patterns to Avoid
When do we do user acceptance testing in Agile? A common pattern is to do user acceptance testing once all the code has been developed and integrated. Or worse, only do that user acceptance testing in production, just before release. How would you eliminate these patterns? When to do the user acceptance testing? Who should do the user acceptance testing in the first place? Have a look.
tcagley.wordpress.com
What to Learn From Accidental Agility?
Accidental agility is when the agile processes are native to what you have in place and they work without everyone fully understanding exactly why. You like it and believe it works. But then you try that at another place, and it doesn’t work. Rather it fails, miserably. What can we do to learn from success and make sure we understand why it may not work at other places?
leadingagile.com
18 Characteristics of a Great Product Owner
How do you become a great Product Owner? Do you have a product vision, that you’ve truly embraced? How do you communicate? Do you know your business model? What do you really focus on? How good are you at saying no? Read on to explore 18 characteristics to become a great Product Owner.
blog.scrum.org
A Business Analyst in Agile? How Does That Work?
I am a Business Analyst but I am expected to be a proxy for the Product Owner, but I have neither the perspective nor the buy-in from the business to do this. What do I do? Some developers on the team think, why do we need the business analyst, we can just talk to the business and ask what they want? Experienced business analysts who have the skills to analyse processes and value chains think, I am expected just to produce requirements instantly, I don’t have the time to do my job in Agile? So how does the role of the business analyst work then? Here a interesting perspective? (video)
scrumexpert.com
3 Ways to Improve Devops Culture
Many organisations have embraced devops concepts, and it’s changed the way business is done. How do you get really good at that? How do end the culture of fear? How do you find and retain knowledge and talent? What should you really focus on? Read on.
devops.com
How to Trick Yourself to Break a Bad Habit?
How do we break that bad habit? We all have one, or many. Some are potentially career limiting. Others affect personal life. Whether it’s weak interpersonal skills, a tendency to procrastinate, or good-but-not-great technical prowess, one of the biggest impediments to our progress is how do we rid ourselves of that bad habit? Here’s a trick you can use.
hbr.org
Share this: