<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-8156024921836845136</id><updated>2011-11-28T03:34:38.500+04:00</updated><category term='All about SCRUM'/><category term='off-topic'/><title type='text'>Certified Scrum Master Notes</title><subtitle type='html'>Not only about SCRUM...</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://litoshenko.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8156024921836845136/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://litoshenko.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>Sieben</name><uri>http://www.blogger.com/profile/12480584035731206926</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>10</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-8156024921836845136.post-1827868752201117323</id><published>2008-04-07T21:02:00.004+04:00</published><updated>2008-04-07T21:16:11.566+04:00</updated><title type='text'>Scrum and Motivation</title><content type='html'>It is very important in SCRUM to have motivated team. As far as we know SCRUM rule is "inspect and adopt". &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_0"&gt;No one&lt;/span&gt; is telling developers what to do. &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_1"&gt;They&lt;/span&gt; have sprint goal, they have list of functionality which should work after Sprint - they are doing whatever they thing is helpful to meet this goal. BUT, it works only if your developers really motivated to meet this goal. I am not talking not about lazy developers, no. But for some type of developers this goal is not so clear. I mean - they are doing theirs job, they are developing, they are finding new features in Java or somewhere else, so they are developing and developing, but they are not concentrated in meeting Project Goal. They are concentrated in development.&lt;br /&gt;&lt;br /&gt;And they are good &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_2"&gt;developers&lt;/span&gt;. they know a lot of &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_3"&gt;technical&lt;/span&gt; things, etc. BUT it is not &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_4"&gt;enough&lt;/span&gt; in SCRUM. Each team member should be concentrated in meeting Sprint goal, on adding new &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_5"&gt;value&lt;/span&gt; to the Project. They should develop not for development, bu to add new value to the Project, which helps theirs team to meet &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_6"&gt;Sprint&lt;/span&gt; Goal, to make Customer happy and to make Customer Business &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_7"&gt;successful&lt;/span&gt;.&lt;br /&gt;&lt;br /&gt;SO, good Project Manager should manage her/his team so it will be motivated to make this Project successful and to meet Sprint Goal, but not just develop day by day.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8156024921836845136-1827868752201117323?l=litoshenko.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://litoshenko.blogspot.com/feeds/1827868752201117323/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8156024921836845136&amp;postID=1827868752201117323' title='44 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8156024921836845136/posts/default/1827868752201117323'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8156024921836845136/posts/default/1827868752201117323'/><link rel='alternate' type='text/html' href='http://litoshenko.blogspot.com/2008/04/scrum-and-motivation.html' title='Scrum and Motivation'/><author><name>Sieben</name><uri>http://www.blogger.com/profile/12480584035731206926</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>44</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8156024921836845136.post-7215718362049896185</id><published>2008-03-27T15:18:00.003+03:00</published><updated>2008-03-27T15:25:06.174+03:00</updated><title type='text'>"apprehension - the way to the truth"</title><content type='html'>"apprehension - the way to the truth" - I am not sure who has told that.&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;Doubt everything untill you will get the truth.&lt;/strong&gt;&lt;br /&gt;&lt;br /&gt;Why is Stand-Up so important? Why should I log working time? Why should I log working time? - if you do not have answers on all these questions, probably you are wasting your time doing it??? - BTW, the answer "Because SCRUM books are telling us that we should do it" - is wrong :) You should answer on the question - why Jeff Sutherland is suggesting you doing that? Which benefits will you get?&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8156024921836845136-7215718362049896185?l=litoshenko.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://litoshenko.blogspot.com/feeds/7215718362049896185/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8156024921836845136&amp;postID=7215718362049896185' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8156024921836845136/posts/default/7215718362049896185'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8156024921836845136/posts/default/7215718362049896185'/><link rel='alternate' type='text/html' href='http://litoshenko.blogspot.com/2008/03/apprehension-way-to-truth.html' title='&quot;apprehension - the way to the truth&quot;'/><author><name>Sieben</name><uri>http://www.blogger.com/profile/12480584035731206926</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8156024921836845136.post-4272392847414966602</id><published>2008-03-26T11:56:00.002+03:00</published><updated>2008-03-26T12:05:43.318+03:00</updated><title type='text'>Ping your team</title><content type='html'>Sometimes it is very reasonable to PING your team and get PONG.&lt;br /&gt;&lt;br /&gt;The thing is - it is quite helpful sometime ask your team to answer on some questions concerning current Project to make sure that team do understand everything same way. Another way it will be very hard for team members to reach goals of the Sprint.&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;For example&lt;/strong&gt; - in one of my Projects we are working on Usability of the system. What is usability? is it measurable? is it using of Ajax?&lt;br /&gt;&lt;br /&gt;I have asked team members to write to me e-mail - what do you mean, whan you are talking about Usability? - i have got 9 answers, they were really about something similar - but some people include in Usability - security, some of them - design. So  - there were no same understanding concerning what are we going to have at the and of the Sprint.&lt;br /&gt;&lt;br /&gt;When Sprint Goal is to improve usability - what exactly should be done? How would we understand that we have completed Sprint? How could we measure it?&lt;br /&gt;&lt;br /&gt;As PM it is quite helpful to make sure that your team is talking on the same language, i am not talking about english or russian, i am talking about terms, which you are using in your Project.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8156024921836845136-4272392847414966602?l=litoshenko.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://litoshenko.blogspot.com/feeds/4272392847414966602/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8156024921836845136&amp;postID=4272392847414966602' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8156024921836845136/posts/default/4272392847414966602'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8156024921836845136/posts/default/4272392847414966602'/><link rel='alternate' type='text/html' href='http://litoshenko.blogspot.com/2008/03/ping-your-team.html' title='Ping your team'/><author><name>Sieben</name><uri>http://www.blogger.com/profile/12480584035731206926</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8156024921836845136.post-3551648165064448364</id><published>2008-03-26T10:45:00.002+03:00</published><updated>2008-03-26T11:02:13.904+03:00</updated><title type='text'>If you just started working based on SCRUM - Stand-Up for PM</title><content type='html'>Here are some points which could be useful for PM who just started using SCRUM and who is going to drive Stand-Up  -&lt;br /&gt;&lt;br /&gt;&lt;ol&gt;&lt;li&gt;To not tal everything for all - give your team ability to speak, do not try to answer on all questions yourself, try to listen what your team is talking&lt;/li&gt;&lt;li&gt;You should be 200% sure in all your words&lt;/li&gt;&lt;li&gt;You should be 200% sincere in all your words - team will feel, if you are not sincere&lt;/li&gt;&lt;li&gt;Do not impose your processes. There is only one way to work based on processes - your team should accept it. Team should belive that it will really help them to meet Project Goal and to work better.&lt;/li&gt;&lt;li&gt;Do not forget - INSPECT AND ADAPT&lt;/li&gt;&lt;li&gt;Stand-up for stand-up is wasting of time. You and your team should understand why they are spending 1 minutes of their time standing and speaking. It is quite helpful to define goal of the Stand-up in the Morning, what are you going to reach during Stand-Up. Try to meet this Goal during Stand-Up and after it - answer your self - have you done it?&lt;/li&gt;&lt;li&gt;If you have some rules (no chairs, no cell phones, no computers) for stand-up - they should work for everyone and every stand-up. No exceptions (cell phone - only for something really urgent)&lt;/li&gt;&lt;/ol&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8156024921836845136-3551648165064448364?l=litoshenko.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://litoshenko.blogspot.com/feeds/3551648165064448364/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8156024921836845136&amp;postID=3551648165064448364' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8156024921836845136/posts/default/3551648165064448364'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8156024921836845136/posts/default/3551648165064448364'/><link rel='alternate' type='text/html' href='http://litoshenko.blogspot.com/2008/03/if-you-just-started-working-based-on.html' title='If you just started working based on SCRUM - Stand-Up for PM'/><author><name>Sieben</name><uri>http://www.blogger.com/profile/12480584035731206926</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8156024921836845136.post-8039547187336771887</id><published>2008-03-25T15:52:00.002+03:00</published><updated>2008-03-25T16:11:44.013+03:00</updated><title type='text'>Stand-Up Scenario (just my vision)</title><content type='html'>&lt;em&gt;Here is one of the visions, how could it looks like. StandUp could be different, depends on the team, etc. This is only one of possible formats.&lt;/em&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;StandUp is +- 15 min meeting, which is going at the beginning of the business day (could be at the end, but 99% - at the beginning :)).&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;&lt;span style="font-size:180%;"&gt;Participants&lt;/span&gt;&lt;br /&gt;&lt;/strong&gt;Required Participants - Development Team&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;&lt;span style="font-size:180%;"&gt;Invariants&lt;/span&gt;&lt;/strong&gt;&lt;br /&gt;&lt;strong&gt;&lt;span style="font-size:180%;"&gt;&lt;/span&gt;&lt;br /&gt;&lt;/strong&gt;-No Cell Phones&lt;br /&gt;-No Computers&lt;br /&gt;-No chairs&lt;br /&gt;-Only one talk same time, other listen&lt;br /&gt;-Only Required Participants are able to talk on the Meeting. All other can only listen.&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;&lt;span style="font-size:180%;"&gt;Rules&lt;/span&gt;&lt;br /&gt;&lt;/strong&gt;&lt;br /&gt;&lt;p&gt;Each member of the Development Team (or one from pair) should answer on several questions - &lt;/p&gt;&lt;ol&gt;&lt;li&gt;What have I done since last StandUp? &lt;/li&gt;&lt;li&gt;For which tasks we are out of Estimation? &lt;/li&gt;&lt;li&gt;What could be tested by the Test Team? - This one is new question and should give for Test team clearer vision on completed tasks. &lt;/li&gt;&lt;li&gt;Which blocks do I have? - Only small items should be solved during meeting. All other should be written down and discussed right after meeting. &lt;/li&gt;&lt;li&gt;What I am planning to do till the next StandUp?&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;There are several additional things which should be done by the team during the StandUp - &lt;/p&gt;&lt;ol&gt;&lt;li&gt;During answering on the question 1 team member should check that all closed tasks are marked on the Lists on the Wall and if not - update it &lt;/li&gt;&lt;li&gt;During answering on the question 5 team member should check that new tasks are marked on the Lists on the Wall and if not - update it &lt;/li&gt;&lt;/ol&gt;&lt;p&gt;&lt;br /&gt;&lt;span style="font-size:130%;"&gt; &lt;/span&gt;&lt;strong&gt;&lt;span style="font-size:180%;"&gt;Scenario&lt;/span&gt;&lt;br /&gt;&lt;/strong&gt;&lt;br /&gt;&lt;strong&gt;Entrance –&lt;br /&gt;&lt;/strong&gt; Responsible – PM&lt;br /&gt; Speech – &lt;em&gt;&lt;span style="font-family:courier new;"&gt;Till the initially planned end date of the Sprint we have “…” days (planned date is “…”). We are out/over the Scope for “…” days, including development – “…” days, testing – “…” days.  For now, based on our current Progress, end date of the Sprint is “…”. To be on track development team should make “…” hours per day, testing – “…” hours. Today are absent - “…” (if any)&lt;br /&gt;&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Quality &lt;/strong&gt;–&lt;br /&gt; Responsible – Test Lead&lt;br /&gt; Speech – &lt;span style="font-family:courier new;"&gt;&lt;em&gt;For now we have “…” open Bugs. “…” of them requires immediate fixing, here they are on Emergency List.&lt;br /&gt;&lt;/em&gt;&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Development Status&lt;/strong&gt; –&lt;br /&gt; Responsible – each developer or representative of the pair&lt;br /&gt; Speech – &lt;/p&gt;&lt;ol&gt;&lt;li&gt;&lt;span style="font-family:courier new;"&gt;&lt;em&gt;We have done these tasks &lt;/em&gt;&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style="font-family:courier new;"&gt;&lt;em&gt;We are out of estimation for “…” hours because of “…” (if we are)&lt;/em&gt;&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style="font-family:courier new;"&gt;&lt;em&gt;“…” items are ready for testing&lt;/em&gt;&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style="font-family:courier new;"&gt;&lt;em&gt;We have problems with “…”&lt;/em&gt;&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style="font-family:courier new;"&gt;&lt;em&gt;Today we are going to make “…” and take bug “…” from the emergency list&lt;/em&gt;&lt;/span&gt;&lt;br /&gt;&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;&lt;strong&gt;Testing Status&lt;/strong&gt;&lt;br /&gt; Responsible – each tester or representative of the pair&lt;br /&gt; Speech – &lt;/p&gt;&lt;ol&gt;&lt;li&gt;&lt;em&gt;&lt;span style="font-family:courier new;"&gt;We have tested these functionality&lt;/span&gt;&lt;/em&gt;&lt;/li&gt;&lt;li&gt;&lt;em&gt;&lt;span style="font-family:courier new;"&gt;We have found several Bugs concerning “…”&lt;/span&gt;&lt;/em&gt;&lt;/li&gt;&lt;li&gt;&lt;em&gt;&lt;span style="font-family:courier new;"&gt;We have such problems during testing – “…”&lt;/span&gt;&lt;/em&gt;&lt;/li&gt;&lt;li&gt;&lt;em&gt;&lt;span style="font-family:courier new;"&gt;Today we are going to test – “…”&lt;/span&gt;&lt;/em&gt;&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;&lt;strong&gt;Exit&lt;br /&gt;&lt;/strong&gt; Responsible – PM&lt;br /&gt; Speech – &lt;/p&gt;&lt;ol&gt;&lt;li&gt;&lt;em&gt;&lt;span style="font-family:courier new;"&gt;Does anyone have anything to discuss concerning the Project – process questions, ideas, etc.? – check Idea wall&lt;/span&gt;&lt;/em&gt;&lt;/li&gt;&lt;li&gt;&lt;em&gt;&lt;span style="font-family:courier new;"&gt;Summary – at the end of the day we are planning to have “…” developed and fixed and “…” tested. Thank you and good luck!!!&lt;/span&gt;&lt;/em&gt;&lt;/li&gt;&lt;/ol&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8156024921836845136-8039547187336771887?l=litoshenko.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://litoshenko.blogspot.com/feeds/8039547187336771887/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8156024921836845136&amp;postID=8039547187336771887' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8156024921836845136/posts/default/8039547187336771887'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8156024921836845136/posts/default/8039547187336771887'/><link rel='alternate' type='text/html' href='http://litoshenko.blogspot.com/2008/03/stand-up-scenario-just-my-vision.html' title='Stand-Up Scenario (just my vision)'/><author><name>Sieben</name><uri>http://www.blogger.com/profile/12480584035731206926</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8156024921836845136.post-953749811646673685</id><published>2008-03-25T15:42:00.002+03:00</published><updated>2008-03-25T15:51:56.897+03:00</updated><title type='text'>Stand-up is not a report to PM</title><content type='html'>It is very critical to make your team understand that Stand-Up is not report concerning work done to PM. PM is not the main nperson on this meeting at all. Team is main person.&lt;br /&gt;Stand-up should not be formal meeting each morning. Igf team does not understand the neccesity of it - it will not have any value.&lt;br /&gt;&lt;br /&gt;Stand-Up is meeting of the Team but not for PM. On this meeting team should update each team member concerning where is the Project now, are we going to meet goal of the Sprint in planned date, or we are out of estimation, which Problems do we have and how to solve them, which emergency bugs do we have.&lt;br /&gt;&lt;br /&gt;Developer should not come to work only to develop. Developer should come to work to make Project better, to help team to meet Sprint goal, but not to write 5 UT and fix 3 bugs - it is not the goal, it could be means to meet goal.&lt;br /&gt;&lt;br /&gt;Development for development is not the goal.&lt;br /&gt;&lt;br /&gt;Development to make Project better, to drive Project to the main GOAL - is good Goal, and is good reason to go to work. If you do not have similar goal - probably you are wasting your time sitting in the Office? Probably it is time to change situation?&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8156024921836845136-953749811646673685?l=litoshenko.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://litoshenko.blogspot.com/feeds/953749811646673685/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8156024921836845136&amp;postID=953749811646673685' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8156024921836845136/posts/default/953749811646673685'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8156024921836845136/posts/default/953749811646673685'/><link rel='alternate' type='text/html' href='http://litoshenko.blogspot.com/2008/03/stand-up-is-not-report-to-pm.html' title='Stand-up is not a report to PM'/><author><name>Sieben</name><uri>http://www.blogger.com/profile/12480584035731206926</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8156024921836845136.post-2995047691335005268</id><published>2008-03-25T12:52:00.002+03:00</published><updated>2008-03-25T13:06:51.274+03:00</updated><title type='text'>Solve Problems trought Risks</title><content type='html'>I have just read "Deadline" book. I don't know why, but only now I have opened it and find out that it is good time.&lt;br /&gt;&lt;br /&gt;Solve Problems trought Risks - if you do not want to be face to face with Problems in the Project, try to predict them, use Risk management Process.&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;Step 1. Each monday try to get information which Risks do you have for now in the Project&lt;/strong&gt; -&lt;br /&gt;Sample -&lt;br /&gt;1. Developer A dont like Tester B, it could cause bad productivity in the Team.&lt;br /&gt;2. Qality of automation tests could be low because we do not have expertise in it.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;Step 2. Try to measure impact&lt;/strong&gt;&lt;br /&gt;1. If developer A will avoid bugs from Tester B we could have at the end of the Sprint 72 bugs in the Application&lt;br /&gt;2. If quality of the AT will be LOW we will spend additional 30 hours in fixing of bugs from Customer.&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;Step 3. Write mitigation strategy&lt;/strong&gt;&lt;br /&gt;Sample -&lt;br /&gt;1. Find out real problem between A and B and solve it.&lt;br /&gt;2. Find in company Automation Tests GURU and share this contact with your Test Team. Find good trainings concerning AT&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;Step 4. At the end of the week try to analyse what have you done concerning these risks, how it helps you this week, etc.&lt;/strong&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;All these steps could be done not only once a week, but every day, or any day, when you think it is reasonable.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8156024921836845136-2995047691335005268?l=litoshenko.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://litoshenko.blogspot.com/feeds/2995047691335005268/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8156024921836845136&amp;postID=2995047691335005268' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8156024921836845136/posts/default/2995047691335005268'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8156024921836845136/posts/default/2995047691335005268'/><link rel='alternate' type='text/html' href='http://litoshenko.blogspot.com/2008/03/solve-problems-trought-risks.html' title='Solve Problems trought Risks'/><author><name>Sieben</name><uri>http://www.blogger.com/profile/12480584035731206926</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8156024921836845136.post-2008263774244022625</id><published>2007-06-13T23:40:00.001+04:00</published><updated>2007-06-13T23:55:32.682+04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='All about SCRUM'/><title type='text'>SCRUM + Motivation</title><content type='html'>One of the main ideas of SCRUM is Self-Organized Team. Sounds really great! You don't need any Team Lead, who will manage tasks for developers and testers - team estimate, commit, implement. But, if you are trying to setup SCRUM in your company you should understand - SCRUM without Motivation is not working at all.&lt;br /&gt;&lt;br /&gt;If your team is not motivated you will get nothing at the end of the Sprint. Even if they will work very hard whole month. What is the reason - team is not motivated, and is not interested in success of the Project, they are not going to meet a goal of the Sprint, they are just working. So, first of all - check if everything is O in your team with motivation. Team should be really concentrated to meet the Goal.&lt;br /&gt;&lt;br /&gt;Let's imagine that you are not managing tasks for team members anymore, and every person is able to start working on any task she/he likes. If your team is not concentrated - each developer and tester will try to take more interesting and probably easy tasks. What will you get in one week - a lot of closed, small, and not related to each other tasks. In terms of system - nothing. What will you send to your testers - nothing, what will you deliver to your customers for review - also nothing.&lt;br /&gt;&lt;br /&gt;If team is motivated, they will check every time - which tasks is most important for today, "what should I do to help team to meet the goal of the Sprint".&lt;br /&gt;&lt;br /&gt;Scrum is working only for very good motivated teams.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8156024921836845136-2008263774244022625?l=litoshenko.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://litoshenko.blogspot.com/feeds/2008263774244022625/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8156024921836845136&amp;postID=2008263774244022625' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8156024921836845136/posts/default/2008263774244022625'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8156024921836845136/posts/default/2008263774244022625'/><link rel='alternate' type='text/html' href='http://litoshenko.blogspot.com/2007/06/scrum-motivation.html' title='SCRUM + Motivation'/><author><name>Sieben</name><uri>http://www.blogger.com/profile/12480584035731206926</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8156024921836845136.post-4516962594764318774</id><published>2007-05-30T01:12:00.000+04:00</published><updated>2007-06-03T15:47:43.472+04:00</updated><title type='text'>ScrumAlliance.org</title><content type='html'>Great!!!&lt;br /&gt;&lt;br /&gt;I was registered on scrumalliance.org. Find my Profile - &lt;a href="http://www.scrumalliance.org/profiles/2092-vladimir-litoshenko"&gt;http://www.scrumalliance.org/profiles/2092-vladimir-litoshenko&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Visit &lt;a href="http://www.scrumalliance.org"&gt;www.scrumalliance.org&lt;/a&gt; for more information about SCRUM and certification.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8156024921836845136-4516962594764318774?l=litoshenko.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://litoshenko.blogspot.com/feeds/4516962594764318774/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8156024921836845136&amp;postID=4516962594764318774' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8156024921836845136/posts/default/4516962594764318774'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8156024921836845136/posts/default/4516962594764318774'/><link rel='alternate' type='text/html' href='http://litoshenko.blogspot.com/2007/05/scrumallianceorg.html' title='ScrumAlliance.org'/><author><name>Sieben</name><uri>http://www.blogger.com/profile/12480584035731206926</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8156024921836845136.post-6501296905071248673</id><published>2007-03-13T23:20:00.000+03:00</published><updated>2007-06-13T13:25:18.215+04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='off-topic'/><title type='text'>Marketing job</title><content type='html'>I was in St.Pete Russia in Metro. There were two guys who were selling some stuff in the train and on each station they were going to another car. One of these guys was selling maps and pensils. Good and usefull maps and not bad pensils. So there were potential buyers in the train, but when he was describing his article of trade noone will be able to hear him and everything what he was talking about was boring and not interesting at all. There were no smile on his face. So, he hasn't sold anything.&lt;br /&gt;Second guy was selling real stuff - something like balloons with a sound. He was talking loud enough so everyone will be able to hear him. He has shown how this balloon works - he has inflated one of them and let them off - balloon was flighing with a funny sound throw whole car. Everyone seen that, and he has sold 5 or 10 such balloons in 2 minutes.&lt;br /&gt;&lt;br /&gt;So - good marketing and presentation are working really well&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8156024921836845136-6501296905071248673?l=litoshenko.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://litoshenko.blogspot.com/feeds/6501296905071248673/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8156024921836845136&amp;postID=6501296905071248673' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8156024921836845136/posts/default/6501296905071248673'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8156024921836845136/posts/default/6501296905071248673'/><link rel='alternate' type='text/html' href='http://litoshenko.blogspot.com/2007/03/marketing-job.html' title='Marketing job'/><author><name>Sieben</name><uri>http://www.blogger.com/profile/12480584035731206926</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry></feed>
