AGILE, COACH, TEAMS
How do you balance responsibilities and commitment with accountability to create a truly meaningful and better work experience? Well, how does responsibility work? Can you assign responsibility to others without them accepting it? How to work with people so they feel responsible and committed? Here are some thoughts.
There’s no running away from this. If you want to move forward and get things done, you’ll need to deal with difficult people. More prepared you are, better the results. People are difficult in more than on way. Here we identify 10 different kinds of difficult people, so you can see what’s coming.
Fear makes us defer action. Instead we go back to wonderful world of creating a perfect plan, or perfect design. Fear of mistakes in our work, before we need that all important sign-off, drives us ever close to waterfall. If it’s really important, we must analyse it “properly”. Right? Here are some thoughts on why fear is waterfall.
You notice minimalism in design everywhere. From iOS to Android, from OS X to many web applications, it’s tough not to spot the trend. When did all start? What counts as minimal design anyway? What factors should you consider while adopting minimal design? Here it is.
Becoming a great Product Owner is challenging to say the least. What critical skills should you focus on if you want to become a great Product Owner? How do you align larger business goals and seemingly small backlog items? That’s a critical skill. How do you go about modifying the backlog in the light of business change and make sure you don’t throw away work done by the team? Read on to learn more about these and three other critical skills.
Information radiators are good at making things visual and easy to spot. How about using one to visualise and thus highlight your technical debt? This technique uses the metaphor of a pool – a pool full of technical debt. Then you go fishing, and you get to do some barbecue as well.
Just imagine. What sort of message the words “post mortem” or “end of project learning” convey, compared to “retrospective”. Which one carries positive energy and sends the right signal? How about “requirements”, “scope creep”, “responding to change” and “user stories”? Here’s an overview of words that ooze “waterfall” or “agile”. Which ones do you use?
Is learning to code and getting better at coding the same thing as learning karate? How does commitment, balance and quality over quantity apply to getting better at development? Mr Miyagi would have a thing or two to teach developers. Well, a lot more than you think.
How do you organise your team to optimise releases? Should the release management be operations led? Would it be better to have a separate team that takes care of release management side of things? Or does it make more sense that your delivery team takes of release management work? Here’s a look at all three approaches.