Do you have a scrum team consisting of individual players? Does your team know why it exists in the first place? Do the team members know eachother's personal preferences for doing the things they do? Are they aware of what they find important as a team? A Team Poster crafted by the team itself will improve collaboration and contributes to a performance increase.
One of the cool things that Europeans added to Judo is the belt system. Japanese are patient by nature, they either do or don't. In fact they distinguish only the black belt, you either have it or are progressing towards it.
We need a bit more guidance to know we are on the right way, hence we have the different belts (which actually originate from the game of pool.) So what are five distinct levels of Product Ownership that we can observe and what must change before we move on to the next level?
Robot Framework is a great automated testing tool that uses a keyword-driven approach. When you want to run Robot Framework tests within the context of a running system-under-test you can load Robot Framework's RemoteServer as a java agent. This is not something that comes out of the box so we will explain how to do it here.
Methods based on Agile and the Kanban Method both stimulate collaboration to achieve focus and flow. In practice this is often challenged by teams with specialists who have a tendency to maximize the utilization of the specialists.
So, is a team with a focus to finish work more effective than a team with focus on efficiently using expertise? Read more
Do you remember the legendary PID? the Project Initiation Document. The famous big binder that we used to create in the beginning of a project to satisfy governance and then bury in a drawer so we could get started. Then agile came and we broke things down. We learned story maps, customer journeys, vision statements, business model canvases. For me it works for the big picture, but when it comes to feature development or epics, it's not perfect.
Product Samurai use elegant weapons for a clear and effective battle. So what is our weapon of choice? I have not yet seen te ultimate tool. But I'm close and I need your help to complete it.
As Product Managers people look up to us to carry the vision, to make sure all the noses are aligned, the troops are rallied and that sort of stuff. But what is it that influences behavior? And what makes your team do what they do? The answer has more to do with you than with others.
During the 5th edition of Scrum Day Europe, Laurens and I facilitated a workshop on how to “Add Visual Flavor to Your Organization Transformation with Videoscribe.”
The theme of the conference, “The Next Iteration,” was all about the future of Scrum. We wanted to tie our workshop into the theme of the conference, so we had a creative brainstorming session and identified four key elements that we think are important in the future of Scrum.
Scaling: Do Scrum well first, before scaling Scrum. You should only scale when needed and if the organization is ready.
Done: A “done” increment means actually done, all the way into production. We hope that future Scrum teams will be able to put things into production themselves. We still see a lot of teams with dependencies on other teams for delivering increments to production.
Product Owner: We’re still searching for great Product Owners who understand the product and the market. These Product Owners work well with teams and are empowered, mandated and have a product vision.
Scrum everywhere: We already see Scrum in construction, health care, schools, marketing and many other places. In the future, we see Scrum used everywhere.
Since Laurens is such a great drawer, he sketched out the four elements, and we made a VideoScribe of them. You can find our video here: https://www.youtube.com/watch?v=XKYjWS4H26I
During our presentation at Scrum Day Europe, we demonstrated each of the seven steps required to produce this video. To bring Videoscribe to life, we asked the attendees to suggest a fifth element for the video on the future of Scrum. They came up with “Happiness.” We then went through the steps to make a video, asking for different volunteers to record a voice over and draw pictures for the message. Here are the results: https://www.youtube.com/watch?v=uWlSaC3K9Kg
The attendees were impressed and amazed to see that they could produce a very smart looking Videoscribe themselves. Overall, the workshop feedback was very positive. We also received some tips for improving it, such as showing examples of how real companies have used this method. But because Videoscribes are usually made for internal use only, we could not show these at the conference. For our next session, we probably make an example Videoscribe for a non-existing company which is shareable with the audience.
One of our attendees was so inspired by our session that we are invited to facilitate a workshop for her management team!
"Well eh ok, I guess so" mumbled the student in the training exercise where he was practicing how to say no to feature gluttony. I decided to give the class an additional exercise to awaken their inner diplomat.
“Diplomacy is the art of telling people to go to hell in such a way that they ask for directions.” - W.S. Churchill
All sweet and well, but how do we say NO?
When scaling Agile/Scrum, we invariably run into the alignment vs. autonomy problem. In short, you cannot have autonomous, self-directing teams if they have no clue what direction they should go. Or, even shorter, alignment breeds autonomy.
But how do we create alignment? And what tools can we use to quickly evaluate whether or not what we want to do is part of the mission? Niel Nickolaisen, chief technology officer at OC Tanner, created the purpose alignment model. I use it with innovation labs in large enterprises to determine what aspects of innovation to keep, and what to leave to others.
I'm getting a lot of questions about my previous blog post. Fortunately also about the content, but mostly about how I created the video. So in this episode we will look at the MVP (Minimal Viable Product) version of a video scribe and the lessons learned. This way you can make a better video scribe based on my learnings.