罗伯·马赫
社交媒体
最新博客抢
看到所有的博客
这是你可能知道每日的站起来。这是最虐待,折磨和虐待在Scrum会议。或即使是Scrum。如果没有别的,这通常是组织采用Scrum的一部分和保持。如果他们做什么他们这样做。和男孩做什么他们做!这个会议太好了15分钟,让我们把它45 !有一些常见的反模式,这个会议期间我遇到过所以我认为我会和你分享。看看你认识他们从你的每日例会。水务局的折磨。 Plain and Simple. I am going to keep you standing up for 45 minutes whilst everyone tells me what exactly they did yesterday and what they plan to do tomorrow. Have a problem with the binary search function? Lets discuss it whilst we all stand here listening. Hey the 10 of us have nothing better to do. The 8 Teams of 1 Person We are not a team. We work on our own. We talk once a day at this ‘mandated’ meeting. Then we each go our separate ways until tomorrow. We work on one task / story each. So we give our update. Then we have to listen to 7 others give theirs. But we don’t care. It does not affect us in any way other than having to stand through this boring meeting. The Wall Talker He approaches the board. He stops. He looks around and starts talking. Quietly. No-one can hear him because he is talking to a wall. Everyone strains to hear, and then gives up. The Over Sharer I know that I didn’t finish much yesterday but let me explain why. Well I had an unscheduled meeting from 10 until 11. I then got a call from my mother in law who said that she had a sore knee. I had to leave work early to drive her to the hospital and then take her home….. The Goldfish Memory I can’t remember what I did yesterday. The Photographic Memory Arrives with pages of notes to read from to justify quite how busy they really are. The Shaver (aka The Hidden Impediment) That task that was 6 hours yesterday. Today it has 5 hours left. Tomorrow it will be 4 hours. Even though you worked on it all day. You need help. You know it and we know it. Please ask your team, one of them would love to help you. Now for the really controversial part. Who said that you have to stand up? Really? Why don't you check that again... Want to sit down at your Daily Scrum, do it. If any of these meetings sound like yours then maybe it’s time for a change. We stood up because the meetings were short. If the meeting isn’t short why are you standing up? Photo licensed via Creative Commons https://www.flickr.com/photos/dpstyles/4835354126
2014年12月17日
我坐在一家咖啡馆享受在新加坡一个当之无愧的饮料和晚餐后教学第一天的Scrum.org Scrum产品负责人专业课程。我们有学生从印度尼西亚、新加坡和柬埔寨的课程。我们第一天大部分时间都在追逐价值在产品开发的想法。哪里驻留在我们的产品待办事项列表的值。我们如何识别,优先考虑并最大化。识别价值是很难的。这是我们的价值,我们的客户价值或两者?是利润生成,满足获得或节省成本?这是一些产品的许多挑战今天的所有权。我们要求我们的很多产品负责人。 We ask that they be entrepreneurs, experimenters, and like product explorers. We ask that they provide a clear compelling vision to our teams and are able to accurately represent many conflicting stakeholders. This is hard. Are we asking too much? Can you really bring a start up mind set to a bank or an insurance company? Can a validated learning approach really exist in corporate IT? Are they able to actually interpret and respond to Scrum’s feedback loops? Many companies ‘assign’ product owners from the ‘business’ (don’t you love that word.) If you talk about anyone outside of IT as ‘the business’ then I worry for you. If you see them as the business, what do they see you as? Probably a monopoly provider of questionable service. What do you think would happen if ‘the business’ could choose a different service provider? Would they still choose you? If they didn’t could you attract new clients? I thought not. You care about the success of the organisation. So do they. You are on the same team. You are not ‘trusted partners of the business’, you are the business. An assigned Product Owner who already has a full time job will not work – yes I did say that. Let’s turn this round. Are you a full time developer / tester / ba / other – great. Let’s pretend we have an exciting new project and it’s so important that it gets funded. We show how important it is by having you be the Product Owner. As well as your day job of course. What could possibly go wrong? These are often multi-million dollar programs / projects. I don’t want to devalue your day job, but really? We ask a lot of our Product Owners. Maybe too much. But don’t make it impossible.
2014年11月4日,
我是一个Scrum教练与Scrum.org。我与许多组织合作,帮助他们变得更加敏捷。我看到很多坏Scrum。超过我的公平份额。有时我看到那么多坏Scrum,这个问题让我我这样做的原因。这篇文章是我试图提醒自己为什么。糟糕的Scrum是什么?让我们开始它不是什么。Scrum不遵循规则。有一个行业充满了Scrum变成一个宗教的人。 I kid you not. They even have names for themselves. They call themselves 'white robes'. They obsess over every change to the Scrum guide and translate the 'founders' intent for you. They will speak of your dysfunctions (sins), they will point out your deviations from the one true path and they will shame you. Scrum is not my religion. Don't make it yours. Be skeptical. There are no higher beings when it comes to Scrum. I am not a high priest and I don't need a high priest. Scrum is not about mechanics. They are merely there to serve a purpose. The mechanics are a means not an end. The mechanics do not define the result. Can I follow all the rules and mechanics and have bad Scrum - you bet. Scrum is freedom. Freedom from the tyranny of trying to meet someone else's commitments (made for you.). It is freedom from being told to be 'accountable', meet your 'commitments' and other 'motivational' words. It is freedom from being measured against someone else promises. It is freedom from feeling like a cog in an endless machine. It is freedom to question, to discover, to disagree, to decide how to work, how to improve and how to make your own promises. What is bad Scrum? If you are not feeling any of these freedoms and you are 'doing' Scrum then you already know the answer. Bad Scrum is mechanical. It's a belief in magic. If we stand up for 15mins every day, attend lots of meetings, call someone a Scrum Master then things should be better right? A Scrum Master just books the meetings and makes sure everyone turns up right? Right? If we decide the features that should be in a release and we decide what date that release will ship we can just tell our self-organizing team and they should be able to deliver it, right? Welcome to bad Scrum. If we decide that the Project Managers should be Scrum Masters but our new teams are self-organizing and therefore accountable for the outcomes, welcome to bad Scrum. If you are being asked to 'drive success' for the team then you are not part of the solution. Lots of companies decide that Scrum has too many holes. It doesn't dictate documentation, dependencies, scaling etc. We need to define that. So they reach out to a prescriptive model (SAFe - I am looking at you) or 'customize' it to add what is missing. Welcome to bad Scrum. The gaps ARE the power. The gaps are where we can decide what works best for us. The gaps are the opportunities. Revel in the gaps. Glory in the gaps. The gaps are what makes this what it is. The gaps are where teams can actually define their own future. The gaps leave room for a self-organizing team to exist. Scrum doesn't need to be customized - just fill in the gaps with what makes your team special. There is genius in empiricism. Predicting the future is hard. Adjusting to evidence is easy if we are given the chance, and people are willing to hear the truth. A team that is allowed to self-organize don't need anyone to 'drive' them. Good Scrum is not about measuring adherence to practices or mechanics. Be skeptical. If your consultant arrives and defines success by measuring practices, think about what you are advocating. You have created a proxy for success. That proxy involves post-it notes and standing up. Really? Good Scrum is exciting. Good Scrum teams have purpose. They have fun. They are not defined by the length of their planning meeting. Good Scrum teams do not need someone to 'empower' them. I have my own power thanks and I don't need yours. Good Scrum teams crave feedback. They crave it from their process, their products, their stakeholders, and each other. Feedback is power. Feedback drives improvement. The Scrum framework gives us a way to gather feedback. Our response to this feedback defines us. These teams need someone to care. Someone to care about more than just the next feature, or project deadline. Scrum Master this is you. You are there to create the environment for this type of team to exist and thrive. You are there to gather this feedback, and help your organization act on it. Do nothing and expect no improvement. Scrum is merely the vehicle that will surface these opportunities for greatness. They will be challenging, they will appear unsolvable. They are not. Look at each day and ask yourself - 'are we better than yesterday?' Your job has nothing to do with booking meetings. If you care - I hope we meet. What type of Scrum do you have? Image courtesy of https://www.flickr.com/photos/matthewalmonroth/14486687503 - licensed via Creative Commons
2014年9月30日
罗伯的认证
专业的Scrum Master我
专业的Scrum产品负责人
专业的Scrum产品所有者三世
我专业的Scrum开发人员
按比例缩小的专业Scrum