Many teams depend on their Scrum Master to solve problems. Scrum Masters become addicted to the helplessness of their teams. Once this pattern gets set, it’s very difficult to break. Consequently, the teams don’t get empowered. It’s toxic. Here are 4 tips to help you avoid this trap.
Have you noticed people always like their ideas better than your ideas? This is what asking powerful questions can achieve. It liberates the coach from providing all the answers. It helps the person being coached explore multiple options. Here are five reasons to help you understand why asking questions is so powerful and liberating at the same time.
It doesn’t matter what your job title says. How many times you see a Scrum Master doing the job of a project manager? How can you tell when you start to (or are made to) work as a project manager instead of a Scrum Master? Here are 7 questions that can help you identify what is it that you are doing exactly.
How to scale? Is SAFe (Scaled Agile Framework) really safe? Or LeSS (Large Scale Scrum) really more? Nokia is not the aspiring example it used to be, but SAFe and LeSS both grew out of Nokia, one way or the other. How did these evolve? What’s the difference? Here it is.
Personas help us understand the user. They help us understand who the users are – their demographics among other insights. Personas help product owners and teams focus on the delivering value to their target users. Here are 7 techniques to help you generate personas.
How about UML? Some like it – others don’t. How about communicating design in one sketch drawn on a white-board? These are two extremes. Most of us do something in between. Here are some ideas on how to communicate technical design and architecture models while keeping it Agile and lean. (PDF)
Making your code replace (most of) documentation is controversial to say the least. It has its critics. But have you really seen it in action? Have your really tried making code speak for itself as documentation? Martin Fowler presents some ideas how to make it so.
Taiichi Ohno defined seven wastes in his landmark book, The Toyota Production System. How do these apply to software development? What sort of waste tends to creep up in our software? Here are seven wastes we must avoid in software development.
Local cultures matter more than ever despite our society and industry becoming heavily globalised. Local cultural attributes can hinder or at times derail agility if we are not careful. Watch out for these 5 anti-patterns to avoid big speed bumps on your path to agility.
What are most of the testers afraid of? Bugs in the released code that could’ve been avoided? Losing their jobs to outsourcing? Here are top three things software testers are most afraid of.
AGILE, SCRUM
Why Depending on Your Scrum Master Can be Toxic?
Many teams depend on their Scrum Master to solve problems. Scrum Masters become addicted to the helplessness of their teams. Once this pattern gets set, it’s very difficult to break. Consequently, the teams don’t get empowered. It’s toxic. Here are 4 tips to help you avoid this trap.
www.scrumalliance.org
COACH
Why Asking Questions is so Powerful and Liberating?
Have you noticed people always like their ideas better than your ideas? This is what asking powerful questions can achieve. It liberates the coach from providing all the answers. It helps the person being coached explore multiple options. Here are five reasons to help you understand why asking questions is so powerful and liberating at the same time.
lmsgoncalves.com
AGILE, SCRUM
7 Differences Between a Scrum Master and a Project Manager
It doesn’t matter what your job title says. How many times you see a Scrum Master doing the job of a project manager? How can you tell when you start to (or are made to) work as a project manager instead of a Scrum Master? Here are 7 questions that can help you identify what is it that you are doing exactly.
blog.scrum.org
SCALING, AGILE
SAFe or LeSS? Which One and Why?
How to scale? Is SAFe (Scaled Agile Framework) really safe? Or LeSS (Large Scale Scrum) really more? Nokia is not the aspiring example it used to be, but SAFe and LeSS both grew out of Nokia, one way or the other. How did these evolve? What’s the difference? Here it is.
gosei.fi
PRODUCT OWNER, USER STORIES
How to Generate Personas?
Personas help us understand the user. They help us understand who the users are – their demographics among other insights. Personas help product owners and teams focus on the delivering value to their target users. Here are 7 techniques to help you generate personas.
tcagley.wordpress.com
DEVELOPER
How to Communicate Design and Architecture?
How about UML? Some like it – others don’t. How about communicating design in one sketch drawn on a white-board? These are two extremes. Most of us do something in between. Here are some ideas on how to communicate technical design and architecture models while keeping it Agile and lean. (PDF)
software-architect.co.uk
Code as Documentation
Making your code replace (most of) documentation is controversial to say the least. It has its critics. But have you really seen it in action? Have your really tried making code speak for itself as documentation? Martin Fowler presents some ideas how to make it so.
martinfowler.com
AGILE, LEAN
Avoid These 7 Wastes of Software Development
Taiichi Ohno defined seven wastes in his landmark book, The Toyota Production System. How do these apply to software development? What sort of waste tends to creep up in our software? Here are seven wastes we must avoid in software development.
www.scruminc.com
TEAMS
How Local Culture Can Derail Agility?
Local cultures matter more than ever despite our society and industry becoming heavily globalised. Local cultural attributes can hinder or at times derail agility if we are not careful. Watch out for these 5 anti-patterns to avoid big speed bumps on your path to agility.
www.scrumalliance.org
TESTING
Worst Fears of a Software Tester
What are most of the testers afraid of? Bugs in the released code that could’ve been avoided? Losing their jobs to outsourcing? Here are top three things software testers are most afraid of.
utest.com
Share this: