tag:blogger.com,1999:blog-50415025604939686292011-11-28T02:15:18.695+01:00- Inspect and adapt. The essence of being agile. Condence knowledge from the past and adapt accordingly to maximize your chances for success.dotPernoreply@blogger.comBlogger31100tag:blogger.com,1999:blog-5041502560493968629.post-41981471844841914212008-07-10T08:03:00.006+02:002008-07-10T14:17:14.766+02:00Only a few weeks into our current project we were all able to see it....<br /><br />..with the the solutionstrategy we initially picked, we were not able to deliver the project on the specified duedate.<br /><br />How could we see that?....The power of SCRUM:) and burndown charts!!<br /><br />Burndown charts is an excellent way of making your progress (or lack of same) visible to EVERYONE. In my team we use 3 different burndowncharts:<br /><ul><li>A burndown chart showing the remaining tasks in the current sprint</li><li>A burndown chart showing the remaining storypoints planned in the sprint</li><li>A burndown chart showing the remaining storypoints of all the planned backlog items from projectstart till projectend.</li></ul>It was actually the last burndownchart, which made it VERY visible, that we needed to change something to get the job done.<br /><br />So burndown charts are great:)<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/5041502560493968629-4198147184484191421?l=inspectandadapt.blogspot.com' alt='' /></div>dotPernoreply@blogger.com0tag:blogger.com,1999:blog-5041502560493968629.post-75749369506712074962008-07-09T15:34:00.002+02:002008-07-09T15:48:06.349+02:00<span style="font-size:100%;">We now for the first time have a dedicated ScrumMaster - as in not a developer which has ScrumMaster duties, but really a person for whom the most important function is to maximize the performance of the scrumteam (me).<br /><br />In the early days in our Scrum-adoption-process we have been placing this important role round-robyn-style on a teammember. This is a very bad idea. The teammember will always have a bigger focus on his current teamtasks, than on the big picture (the process as a whole). And in stressful situations up to a deadline, it is very easy to totally neglect this role. Believe me - been there done that!.<br /><br />So have the team point out a person who can dedicate his time to being a Scrummaster. <br /><br /></span><span style="font-size:100%;"><br /></span><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/5041502560493968629-7574936950671207496?l=inspectandadapt.blogspot.com' alt='' /></div>dotPernoreply@blogger.com0tag:blogger.com,1999:blog-5041502560493968629.post-90261671507438304632008-07-09T15:12:00.012+02:002008-07-10T14:16:01.911+02:00<span style="font-size:100%;">In my organization we have been trying to implement Scrum several times in the last couple of years. We are now in the middle of our 4th or 5th attempt and now it finally seems to work...:)<br /><br />I can see now that one of the key mistakes we made in our earlier attempts, was to create our own processmodel by bending the </span><span style="font-size:100%;">rules and roles of Scrum.<br /><br /></span><span style="font-size:100%;">If you want to adopt Scrum as your agile project management foundation it is crucial (especially in the beginning) to stick to the recipe.</span><span style="font-size:100%;"><br /></span><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/5041502560493968629-9026167150743830463?l=inspectandadapt.blogspot.com' alt='' /></div>dotPernoreply@blogger.com0