Scrumphony - Scrum, Kanban and other useful stuff

Ready For Sprint?

scrumphony — Mon, 16 Jan 2012 07:25:07 +0000

http://www.flickr.com/photos/robert_voors/767796301/

Have you ever been sitting in a sprint planning and heard the following sentences:

“Can we split this user story and at least start with the GUI?”
“I’m not sure if the hardware will be available on time to integrate this story but we could use an emulator instead.”
“There are no wire frames yet, but we could start with the back-end.”
“The acceptance criteria are still quite vague, but I think I know what the customer needs.”
etc.

Does some of these sentences sound familiar? I observed these conversations several times in the past. All of these quotes are based on the same problem: The user story is simply not ready for the next sprint. Still, some teams pull these user stories into there next sprint to implement at least a part of it, to make the PO happy. Stop it! It doesn’t make sense at all. None of these user stories will be done at the end of the sprint, because important parts are missing. These teams have to be reminded that every user story has to be implemented, tested, integrated, documented and shall deliver value to the end user. If you already know at the start of a new sprint, that you won’t be able to finalize a user story: ditch it!

But what can you do to avoid these discussions? There is a simple solution: Introduce the “Definition of Ready” (DoR)! The DoR defines, when a user story is ready for a sprint. If it doesn’t comply with this definition it will be ignored in the next sprint planning. As the “Definition of Done”, the DoR is defined by the team itself and therefore varies from team to team. If you’re e.g. developing a web application, hardware may be not that important for your team, but if you’re developing software for e.g. a medical device it is could be important. Sit together with your team and your PO and define what the DoR has to contain in your current situation. Agree, only to pull those stories into your sprint, that are ready for sprint.

Most agile teams I know implement a DoD, but the DoR is still only rarely used. I hope this will change in the future. Don’t waste your time implementing half-baked user stories. You can use your time better than that.

What are your experiences? Leave a comment!

Food For Thought #13: Less distraction, more ideas

scrumphony — Wed, 04 Jan 2012 20:20:55 +0000

http://www.flickr.com/photos/30228426@N03/2832163100/

Do you know these moments, were you’re between two tasks and don’t have the energy to start with the next one? I know these moments a lot. It’s same when you’re working on a task and you’re stuck. This is the time when a lot of people search for distraction. At least that’s what I did in the past. You open your web browser and start surfing the web, reading your Twitter timeline, checking for mails on your 11 different email accounts or check who is online on Skype. Nowadays it’s easy to get distracted. There are hundreds of ways to waste your costly life time. The main problem is, when you get used to this behavior, your productivity decreases over time. In the end your not able to concentrate on a single task and even get distracted by simple things DURING a task (like e.g. an incoming email or DM on Twitter). You don’t have the energy to start any task (maybe smaller ones). Don’t tolerate this behavior, stop it! Now! Did you hear me? Stop it!

The next time you’re having a break between two tasks, lean back and do….. nothing. Yes, exactly. Just do nothing. Don’t try to fill these breaks with some distracting activities. Try to withstand the impulse to open the browser or anything else to fill this gap. Just sit there (or stand) and wait. After a while the magic will happen: New ideas will come up into your mind. Your mind needs these breaks to get back into creativity mode. This isn’t wasted time, instead it’s one of the most valuable things you can do with it. In my experience the best ideas are created during these mind breaks.

Try it out and tell me your observations and experiences in the comments. I’m already looking forward to read them.

6 Things You Might Try in 2012

scrumphony — Thu, 29 Dec 2011 23:20:06 +0000

http://www.flickr.com/photos/katieharbath/4764671272/

2011 draws to a close and it is time to set your goals for 2012. If you’re not sure what challenges to put on your plan for 2012, the following list could be a starting point.

1 retro 2011

Before jumping into 2012 it might be a good idea to do a retrospective for the past year. Sit together with your family, draw a timeline and collect all the good things that happened to you in 2011. But do me a favor and forget about the bad things to keep 2011 in good memory.

2 question your org structure

When was the last time you questioned the organizational structure of your company? Does it still fit with the way you’re working? Does it support you in your daily business? No? Then it is definitely time to openly question this structure. I saw a lot of companies trying to introduce agile frameworks like Scrum but without changing the current org structure. It never worked. Let’s try to avoid it! Invite for a kick off meeting to get the discussions rolling and start the change process. It is worth it.

3 ask why

Why did your company introduce Scrum? Why do they think that agile frameworks will help. Why is this process in place. Why do we need to fill out this excel spreadsheet? Why does it take so long to get new hardware? Why is Bob behaving like an idiot? Why are you doing your job? Why is this task so important.

Why questions are the most powerful questions. They are a great trigger to ignite change in your workplace or even in your private life. Why questions will help you in your quest for a life of continuously improvements.

4 offer uncalled help

When was the last time you actively offered help? Don’t wait to be asked. When you see somebody struggling, offer them your help. This shouldn’t be limited to your work life, but also to your private life. Unfortunately, the number of people who are offering uncalled help is decreasing year after year. It starts with so simple things, like opening the door for someone who is balancing a cup of coffee in one and a laptop in the other hand. Try it out, it will brighten up your day.

5 work on your listening skill

Have a look at this great TED talk by Julian Treasure. He talks about 5 ways to listen better. Definitely worth the time!

6 genba walk

If you’re a manager or team lead, this one is for you. Instead of sitting in your office and waiting till everyone comes to you, leave your office and visit your employees. Genba is a Japanese term meaning “the real place”. Go to the places in your company, where the real value is created. The idea of a genba walk is that problems are visible and the best improvement ideas will come from going to the genba. It is also a great opportunity to improve your communication with your team.

What else to you have on your agenda for the year 2012? Leave a comment! Thanks.

An agile cloze

scrumphony — Fri, 09 Dec 2011 13:23:00 +0000

http://www.flickr.com/photos/monkeyminddesign/4553428118/

I was just inspired by an german christmas cloze. It even inspired me so much, that I decided to write an agile cloze and let you fill the missing pieces So, here you are.

The best way _____________________.

Scrum is ______________ but XP _________________ with or without Kanban.

I currently read ______________ and think _____________.

___________ is the best thing that happened to our company because ____________.

Would you believe _______________.

_____________________ awesome.

If ______________ the world would be a better place.

Happy __________________.

You can either leave a comment or create a blog post based on the above cloze. I’m looking forward to your “fill-in”