It’s tough to become a great leader. How do you ask people to do hard things? How to really get to know what your team member want? How to foster a culture where people are not afraid of trying? How to get respect from your team members? How to make your team members feel like heroes, instead of turning yourself into a hero? Importantly, how to have difficult conversations? Here are some lessons from a new leader.
During your Agile transformation you have started to engage with finance and accounting teams to include Agile in their accounting practices. Now, how do we measure cost? Do we measure cost per person (FTE), or should we just have team costs? Are you faced with cost optimisation by moving people around? Now and then, are you faced with the question – which bucket (CapEx or OpEx) your stories fall under? Agile teams dread this question. Even more worrying is the cost question. And the dreaded time tracking. Well, here are 10 pitfalls of Agile capitalisation and a few tips to make things simpler.
Ever heard this before – the team isn’t delivering fast enough? Most teams are reduced to cutting corners on quality, work longer hours, or just try to work faster somehow. But what do we mean by speed? Where do we look to speed things up, the way the team work? Or do we go upstream also and see how does the work flow in? How do we influence both the quality and quantity of work, while helping teams move faster? Here are some ideas.
Are your team members focussed on detailed activities instead of the actual results the team has achieved? Do you use a long Sprint 0 before the real Sprints start? Do you have a Product Owner who doesn’t have a Sprint Goal in mind? Do you do Backlog Refinement only with the Product Owner and the Lead Developer? Here are 30 Scrum pitfalls you should avoid
Let’s say your product has been around for a while. Now you want to change the product. How do you go about doing this, without creating a lot of pain, confusion and risking loss of market position? But What do you change first? How do you locate and discover new possibilities, improve user experience and at the same time isolate change so you can measure the effectives of change? Very tough, indeed. Here are a few ideas you can try.
Do you always have “I know what I am doing” approach? You maybe in more trouble than you think, especially if you really want to become a very very good developer. How often do you try to prove yourself right? Another question. When does the development end, does it end when the coding ends? How often do you find yourself reading code, a lots of code? Here are 8 tips to become a a great developer.
It’s always helpful if you can you can move participants from a planned approach to an agile approach, by playing a fun game with them. You can demonstrate sprints and even introduce pair programming. You can help them see how their speed of response gets faster and at the same time the quality goes up as you are able to reduce rework. Here’s a game that helps you do exactly this.
AGILE
Leadership Lessons from a New Leader
It’s tough to become a great leader. How do you ask people to do hard things? How to really get to know what your team member want? How to foster a culture where people are not afraid of trying? How to get respect from your team members? How to make your team members feel like heroes, instead of turning yourself into a hero? Importantly, how to have difficult conversations? Here are some lessons from a new leader.
dzone.com
10 Pitfalls of Agile Capitalisation
During your Agile transformation you have started to engage with finance and accounting teams to include Agile in their accounting practices. Now, how do we measure cost? Do we measure cost per person (FTE), or should we just have team costs? Are you faced with cost optimisation by moving people around? Now and then, are you faced with the question – which bucket (CapEx or OpEx) your stories fall under? Agile teams dread this question. Even more worrying is the cost question. And the dreaded time tracking. Well, here are 10 pitfalls of Agile capitalisation and a few tips to make things simpler.
allaboutagile.com
How to Speed Up Effectively?
Ever heard this before – the team isn’t delivering fast enough? Most teams are reduced to cutting corners on quality, work longer hours, or just try to work faster somehow. But what do we mean by speed? Where do we look to speed things up, the way the team work? Or do we go upstream also and see how does the work flow in? How do we influence both the quality and quantity of work, while helping teams move faster? Here are some ideas.
dzone.com
Avoid These 30 Scrum Pitfalls
Are your team members focussed on detailed activities instead of the actual results the team has achieved? Do you use a long Sprint 0 before the real Sprints start? Do you have a Product Owner who doesn’t have a Sprint Goal in mind? Do you do Backlog Refinement only with the Product Owner and the Lead Developer? Here are 30 Scrum pitfalls you should avoid
blog.scrum.org
PRODUCT OWNER
Why Can’t We Change Our Product?
Let’s say your product has been around for a while. Now you want to change the product. How do you go about doing this, without creating a lot of pain, confusion and risking loss of market position? But What do you change first? How do you locate and discover new possibilities, improve user experience and at the same time isolate change so you can measure the effectives of change? Very tough, indeed. Here are a few ideas you can try.
blog.learningbyshipping.com
DEVELOPER
8 Tips to Become a Great Developer
Do you always have “I know what I am doing” approach? You maybe in more trouble than you think, especially if you really want to become a very very good developer. How often do you try to prove yourself right? Another question. When does the development end, does it end when the coding ends? How often do you find yourself reading code, a lots of code? Here are 8 tips to become a a great developer.
dzone.com
Agile Testing Game
It’s always helpful if you can you can move participants from a planned approach to an agile approach, by playing a fun game with them. You can demonstrate sprints and even introduce pair programming. You can help them see how their speed of response gets faster and at the same time the quality goes up as you are able to reduce rework. Here’s a game that helps you do exactly this.
tastycupcakes.org
Share this: