A wave begins when people begin to organize around innovative practices to solve a problem. As it grows in magnitude a distinct community of practice begins to emerge. The first wave of Agile was about setting up a small Agile team to produce better software. The second wave was about scaling, to integrate and coordinate work across Agile teams, while sustaining Agile teams in an enterprise setting. What’s the third wave about? Read on.
Are user stories and requirements synonymous? They do share some traits and you may find them in the same context, but that does not make them the same. User stories help us identity value from user perspective, and deliver that incrementally. User stories are about exploring options and seizing opportunities. If user stories are not requirements, then what are these? And how do we “get requirements”? Read on.
The company needs to operate in a faster, better and cheaper way. Well, more or less, all companies want to do this. Many chose Agile to enable faster, better and cheaper deliveries. They think that’s what Agile does. Is it the case? How do teams behave in a company where the reason to adopt Agile is faster, better and cheaper deliveries? Would these companies end up with empowered teams, where people are trusted to continuously improve, or would they end up with conforming teams?
No more endless debates. Let’s focus on building software by focusing on generating value rather than controlling cost, however it is accomplished. Right? Here’s an interesting perspective on why it’s time to bid farewell to #NoEstimates because we’ve have reached the point where the hashtag takes more away from than it gives.
Scrum masters are in high demand. That leads to waves of new professionals entering the market, probably believing that reading one or two Scrum books will be sufficient. How do you know the person you’re interviewing understands Agile, in theory and in practice? Keeping in mind there are no rules that apply to each and every scenario, here are 38 questions that can help you avoid imposter Scrum Masters.
What’s your leadership style, as the Product Owner? Do you know how to lead without authority? Do you use an affiliative style, putting people first and believe in strong relationships? Are you a democratic Product Owner and like to involve other people in your decision making? Do you use coaching techniques? Here are 7 different Product Owner leadership styles you can learn from.
How can we create our own opportunities to gain insight, knowledge, and skills that take us forward? How can we can have more control over our learning at work? And what’s the best way to learn? Best way to learn anything. Do we learn better if we learn on our own? Why high quality connections help us grow quicker? Have a look.
AGILE
3rd Agile Wave
A wave begins when people begin to organize around innovative practices to solve a problem. As it grows in magnitude a distinct community of practice begins to emerge. The first wave of Agile was about setting up a small Agile team to produce better software. The second wave was about scaling, to integrate and coordinate work across Agile teams, while sustaining Agile teams in an enterprise setting. What’s the third wave about? Read on.
www.solutionsiq.com
Difference Between User Stories and Requirements
Are user stories and requirements synonymous? They do share some traits and you may find them in the same context, but that does not make them the same. User stories help us identity value from user perspective, and deliver that incrementally. User stories are about exploring options and seizing opportunities. If user stories are not requirements, then what are these? And how do we “get requirements”? Read on.
blog.crisp.se
Empowered Teams Vs Conforming Teams
The company needs to operate in a faster, better and cheaper way. Well, more or less, all companies want to do this. Many chose Agile to enable faster, better and cheaper deliveries. They think that’s what Agile does. Is it the case? How do teams behave in a company where the reason to adopt Agile is faster, better and cheaper deliveries? Would these companies end up with empowered teams, where people are trusted to continuously improve, or would they end up with conforming teams?
scrumalliance.org
Putting NoEstimate Debate to Bed
No more endless debates. Let’s focus on building software by focusing on generating value rather than controlling cost, however it is accomplished. Right? Here’s an interesting perspective on why it’s time to bid farewell to #NoEstimates because we’ve have reached the point where the hashtag takes more away from than it gives.
blog.jbrains.ca
38 Questions to Avoid Imposter Scrum Masters
Scrum masters are in high demand. That leads to waves of new professionals entering the market, probably believing that reading one or two Scrum books will be sufficient. How do you know the person you’re interviewing understands Agile, in theory and in practice? Keeping in mind there are no rules that apply to each and every scenario, here are 38 questions that can help you avoid imposter Scrum Masters.
dzone.com
PRODUCT OWNER
7 Product Owner Leadership Styles
What’s your leadership style, as the Product Owner? Do you know how to lead without authority? Do you use an affiliative style, putting people first and believe in strong relationships? Are you a democratic Product Owner and like to involve other people in your decision making? Do you use coaching techniques? Here are 7 different Product Owner leadership styles you can learn from.
romanpichler.com
TEAMS
Why Learning Together Makes Learning Better
How can we create our own opportunities to gain insight, knowledge, and skills that take us forward? How can we can have more control over our learning at work? And what’s the best way to learn? Best way to learn anything. Do we learn better if we learn on our own? Why high quality connections help us grow quicker? Have a look.
hbr.org
Share this: