{"id":705,"date":"2010-09-21T15:30:50","date_gmt":"2010-09-21T14:30:50","guid":{"rendered":"http:\/\/blog.eweibel.net\/?p=705"},"modified":"2010-09-21T16:24:16","modified_gmt":"2010-09-21T15:24:16","slug":"tailoring-scrum","status":"publish","type":"post","link":"https:\/\/blog.eweibel.net\/?p=705","title":{"rendered":"Tailoring Scrum"},"content":{"rendered":"<p>During the last big project, duration more than a year, we used scrum. But it was a tailored scrum process. The reasons for the tailoring were:<\/p>\n<ul>\n<li>No scrum\/agile experience in the company <\/li>\n<li>Small team (4 developers) <\/li>\n<li>Knowledge of tailoring <a href=\"http:\/\/en.wikipedia.org\/wiki\/IBM_Rational_Unified_Process\" target=\"_blank\">RUP<\/a> or <a href=\"http:\/\/www.hermes.admin.ch\/\" target=\"_blank\">Hermes<\/a> <\/li>\n<li>First project with agile methods <\/li>\n<\/ul>\n<p>Normally I was the Scrum Master and mostly also the Product owner. The role of the Product owner should be fulfilled by the customer, but in our project, there were several customers with different opinions and interests. So it was our job to play a role like an advocate, in this scenario it means, that I have to be the Product owner for the developers. That wasn&#8217;t easy, because you have to understand what your customers want and explain that to them. But that&#8217;s daily business for a software engineer, isn&#8217;t it?   <br \/>As an illustration I describe a typical week:<\/p>\n<p><strong>Monday<\/strong> <a href=\"http:\/\/blog.eweibel.net\/wp-content\/uploads\/Test029.jpg\"><img loading=\"lazy\" decoding=\"async\" style=\"border-right-width: 0px; display: inline; border-top-width: 0px; border-bottom-width: 0px; margin-left: 0px; border-left-width: 0px; margin-right: 0px\" title=\"Test 029\" border=\"0\" alt=\"Test 029\" align=\"right\" src=\"http:\/\/blog.eweibel.net\/wp-content\/uploads\/Test029_thumb.jpg\" width=\"264\" height=\"351\" \/><\/a>     <br \/>The first thing what I did as Scrum Master is a review of the last week with the team. We looked at our whiteboard (our sprint-backlog) where we could see all tasks of the last week and which of them were done. I calculated the rate in percent how much of the planed tasks are done. Normally we had a rate between 70% and 90%. If it was lower than 70% I knew that we planned too much. If the rate was 100% I knew we planned too less.<\/p>\n<p>Here is the first tailoring: We used tasks rather than stories. This because we use in the company the term task and everybody knows what that is and which granularity it has. There was no need to introduce the concept of user stories.    <br \/>And there is another tailoring: As you can see on the picture, the layout on the whiteboard isn&#8217;t like a scrum board. We chose a quite simple layout: The tasks have only two states: Not-done or done. Important Tasks are additional marked with an exclamation mark.     <br \/>After the review meeting, I cleared all tasks on the board which are done. The tasks which weren\u2019t done I asked the team if we would do those tasks this week. If the answer is no, I cleared also those tasks and entered them in our project management tool to not loose them.     <br \/>Now the planning of the current week began: Every developer had access to our project management tool where he could see, what we had to do. And here is the next tailoring: In our company we have a project management tool, which we have to use. So I decided to use that tool as our product backlog. After the planning meeting you could see on the whiteboard all tasks which the team has committed to do this week. To some of the tasks on the whiteboard I added an exclamation mark to show the team the most important tasks for that week. The whole planning process was very democratic: Every developer could say what he thinks and I try to achieve a consensus.<\/p>\n<p><strong>Tuesday until Thursday<\/strong>     <br \/>Every morning we did a short meeting (like the scrum daily meeting): I checked with the developers every task on the whiteboard and asked the state of the task. During this process there could happen, that I added new tasks on the whiteboard, but we never delete tasks on the whiteboard (because of the review meeting next Monday).     <br \/>During the day I went to every developer and asked him if everything is OK or if I could do something for him. And this is another tailoring: In Scrum you have normally one daily meeting. Because our company had no experience in agile methods I decided to increase the communication between the Scrum master and the team members. If you are in a very agile experienced team there is much less need for that much communication, but communication is always a good thing.<\/p>\n<p><strong>Friday<\/strong>     <br \/>On Friday we delivered the software with most of the tasks, which we planned. The most important tasks were always delivered.<\/p>\n<p><strong>Conclusion<\/strong>     <br \/>Our sprint duration was one week and it was OK for us. The project was really tough and for that one week was perfectly. I used the project management tool to be transparent to the management and used the tailored scrum process to manage the creation of the software during the project.     <br \/>The team members were all quite young and interested in learning new things. I enjoyed it very much to work in that team. But because the team members were young I had a big responsibility to coach and lead them.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>During the last big project, duration more than a year, we used scrum. But it was a tailored scrum process. The reasons for the tailoring were: No scrum\/agile experience in the company Small team (4 developers) Knowledge of tailoring RUP or Hermes First project with agile methods Normally I was the Scrum Master and mostly also the Product owner. The role of the Product owner should be fulfilled by the customer, but in our project, there were several customers with&#8230;<\/p>\n<p class=\"read-more\"><a class=\"btn btn-default\" href=\"https:\/\/blog.eweibel.net\/?p=705\"> Read More<span class=\"screen-reader-text\">  Read More<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_exactmetrics_skip_tracking":false,"_exactmetrics_sitenote_active":false,"_exactmetrics_sitenote_note":"","_exactmetrics_sitenote_category":0,"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[17,14],"tags":[],"class_list":["post-705","post","type-post","status-publish","format-standard","hentry","category-agile","category-software-engineering"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/plOV9-bn","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":1056,"url":"https:\/\/blog.eweibel.net\/?p=1056","url_meta":{"origin":705,"position":0},"title":"Certified Professional Scrum Master I","author":"Patrick","date":"16. Jun 2011","format":false,"excerpt":"I did it again. First I did the scrum master course with the great teacher Ralph Jocham (@rjocham, effective agile). Then I passed the assessment after exercise the open assessment several times. I read also the Scrum guide twice. After that I took the assessment and passed it. So now\u2026","rel":"","context":"In &quot;Agile&quot;","block_context":{"text":"Agile","link":"https:\/\/blog.eweibel.net\/?cat=17"},"img":{"alt_text":"PSM Front Logo 2","src":"https:\/\/i0.wp.com\/blog.eweibel.net\/wp-content\/uploads\/PSMI_Logo_thumb.png?resize=350%2C200","width":350,"height":200},"classes":[]},{"id":1006,"url":"https:\/\/blog.eweibel.net\/?p=1006","url_meta":{"origin":705,"position":1},"title":"Certified Scrum Master","author":"Patrick","date":"11. Apr 2011","format":false,"excerpt":"Last week I participated the certified Scrum Master course in Bern. The event was organized by DasScrumTeam and the teacher was Andreas Schliep. After the course I passed also the online CSM Course evaluation with 97%. Now I am certified Scrum Master. Here some links which I found during some\u2026","rel":"","context":"In &quot;Agile&quot;","block_context":{"text":"Agile","link":"https:\/\/blog.eweibel.net\/?cat=17"},"img":{"alt_text":"110407-CJS-IMG41","src":"https:\/\/i0.wp.com\/blog.eweibel.net\/wp-content\/uploads\/110407CJSIMG41_thumb.jpg?resize=350%2C200","width":350,"height":200},"classes":[]},{"id":1353,"url":"https:\/\/blog.eweibel.net\/?p=1353","url_meta":{"origin":705,"position":2},"title":"NDC 2014","author":"Patrick","date":"16. Jun 2014","format":false,"excerpt":"I attended this year's NDC (Norwegian developer conference) in Oslo. It was a very interesting conference, but as a short summary, it saw something like a consolidation. JavaScript - as some people say in its fourth generation (Simple Scripts, AJAX, MVC-Framworks, SPA) - is finally accepted as a language like\u2026","rel":"","context":"In &quot;.NET&quot;","block_context":{"text":".NET","link":"https:\/\/blog.eweibel.net\/?cat=13"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/blog.eweibel.net\/wp-content\/uploads\/ndclogo2014.png?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]},{"id":1224,"url":"https:\/\/blog.eweibel.net\/?p=1224","url_meta":{"origin":705,"position":3},"title":"My personal wrap-up of the NDC 2012","author":"Patrick","date":"21. Jun 2012","format":false,"excerpt":"I was at the Norwegian Developer Conference (NDC) 2012 in Oslo. It is one of the best conferences I know in Europe. One reason is, that a lot of alpha-geeks are speaking there. There were during three days 8 parallels tracks, so you have to manage your program. My program\u2026","rel":"","context":"In &quot;First experiencies&quot;","block_context":{"text":"First experiencies","link":"https:\/\/blog.eweibel.net\/?cat=7"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1086,"url":"https:\/\/blog.eweibel.net\/?p=1086","url_meta":{"origin":705,"position":4},"title":"Grooming your code base","author":"Patrick","date":"1. Sep 2011","format":false,"excerpt":"When you're doing Test Driven Development (TDD), it's in the process: Red-Green-Refactor. Refactoring doesn't only mean to improve your new code, it is also important to make your existing code nicer. If you are a .NET Developer, then you should have the Visual Studio Add-on ReSharper. With this tool you\u2026","rel":"","context":"In &quot;.NET&quot;","block_context":{"text":".NET","link":"https:\/\/blog.eweibel.net\/?cat=13"},"img":{"alt_text":"Fotolia_32643902_S","src":"https:\/\/i0.wp.com\/blog.eweibel.net\/wp-content\/uploads\/Fotolia_32643902_S_thumb1.jpg?resize=350%2C200","width":350,"height":200},"classes":[]},{"id":1784,"url":"https:\/\/blog.eweibel.net\/?p=1784","url_meta":{"origin":705,"position":5},"title":"Knowledge Transfer in Times of Technology Change","author":"Patrick","date":"3. May 2025","format":false,"excerpt":"Let\u2019s face it: Technology changes in software development aren\u2019t rare events, they\u2019re practically the background noise of our industry. Especially in the evolving .NET world, where frameworks, tools, and deployment models are constantly shifting, staying on top means more than just learning new tools or technologies. It means preserving, sharing,\u2026","rel":"","context":"In &quot;Agile&quot;","block_context":{"text":"Agile","link":"https:\/\/blog.eweibel.net\/?cat=17"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/blog.eweibel.net\/wp-content\/uploads\/ChatGPT-Image-3.-Mai-2025-16_20_33_2.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/blog.eweibel.net\/wp-content\/uploads\/ChatGPT-Image-3.-Mai-2025-16_20_33_2.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/blog.eweibel.net\/wp-content\/uploads\/ChatGPT-Image-3.-Mai-2025-16_20_33_2.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/blog.eweibel.net\/wp-content\/uploads\/ChatGPT-Image-3.-Mai-2025-16_20_33_2.png?resize=700%2C400&ssl=1 2x"},"classes":[]}],"_links":{"self":[{"href":"https:\/\/blog.eweibel.net\/index.php?rest_route=\/wp\/v2\/posts\/705","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.eweibel.net\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.eweibel.net\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.eweibel.net\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.eweibel.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=705"}],"version-history":[{"count":12,"href":"https:\/\/blog.eweibel.net\/index.php?rest_route=\/wp\/v2\/posts\/705\/revisions"}],"predecessor-version":[{"id":784,"href":"https:\/\/blog.eweibel.net\/index.php?rest_route=\/wp\/v2\/posts\/705\/revisions\/784"}],"wp:attachment":[{"href":"https:\/\/blog.eweibel.net\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=705"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.eweibel.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=705"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.eweibel.net\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=705"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}