<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/atom.xsl" media="screen"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-US"><title type="html">Parlance</title><subtitle type="html" /><id>http://blogs.msdn.com/svemu/atom.xml</id><link rel="alternate" type="text/html" href="http://blogs.msdn.com/svemu/default.aspx" /><link rel="self" type="application/atom+xml" href="http://blogs.msdn.com/svemu/atom.xml" /><generator uri="http://communityserver.org" version="2.1.61025.2">Community Server</generator><updated>2008-03-21T12:00:47Z</updated><entry><title>Adopting SCRUM in Global Delivery</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/svemu/archive/2008/12/12/adopting-scrum-in-global-delivery.aspx" /><id>http://blogs.msdn.com/svemu/archive/2008/12/12/adopting-scrum-in-global-delivery.aspx</id><published>2008-12-12T10:10:11Z</published><updated>2008-12-12T10:10:11Z</updated><content type="html">&lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;p&gt;Recently (Oct 2008), I gave a presentation at a delivery management summit held by Microsoft at Cancun about Adopting SCRUM in a global delivery model.&lt;/p&gt;  &lt;p&gt;The adoption though not a run-away hit , has its own unique flavor and challenges more so when the customer is not even used a global delivery/onsite-offshore model the biggest one is that of the product owner not being in close proximity to the team , though with the usage of technologies some of these issues can be solved , there is also the other challenge of where the SCRUM Master needs to be and what’s the role of an offshore project manager and how he can contribute to the development life cycle.&lt;/p&gt;  &lt;p&gt;Not silver bullets – but from my experience of executing some of these projects, here’s a set of “Best Practices”&lt;/p&gt;  &lt;ul&gt;   &lt;li&gt;SCRUM Workshops for all the stake-holders during project initiation &lt;/li&gt;    &lt;li&gt;Break between sprints to review Specifications ( In case on unclear requirements) &lt;/li&gt;    &lt;li&gt;Treat the first few sprints as learning sprints , and let the team find their pace &lt;/li&gt;    &lt;li&gt;Decide on sprint duration during Sprint planning meeting &lt;/li&gt;    &lt;li&gt;Conduct feasibility analysis during deal structuring stage &lt;/li&gt;    &lt;li&gt;Conduct health check meetings after 3-4 sprints in long duration projects including all stakeholders even if you're doing regular retrospectives &lt;/li&gt;    &lt;li&gt;Documenting every decision made on the SharePoint Wiki Site, post the stand up meet &lt;/li&gt;    &lt;li&gt;Project sponsors and management buy-in and intervention , when needed &lt;/li&gt;    &lt;li&gt;Usage of BA to be proxy product owner &lt;/li&gt;    &lt;li&gt;Continuous coaching by experienced SCRUM Masters&lt;/li&gt; &lt;/ul&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9200772" width="1" height="1"&gt;</content><author><name>svemu</name><uri>http://blogs.msdn.com/members/svemu.aspx</uri></author></entry><entry><title>SCRUM in Infrastructure Projects</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/svemu/archive/2008/11/24/scrum-in-infrastructure-projects.aspx" /><id>http://blogs.msdn.com/svemu/archive/2008/11/24/scrum-in-infrastructure-projects.aspx</id><published>2008-11-24T12:50:52Z</published><updated>2008-11-24T12:50:52Z</updated><content type="html">&lt;p&gt;I have met quite a few project managers who have made the jump from one side to the other, I.e. moved from Infrastructure and the construction world to IT and vice versa , this was possible because all of them were pure Project Managers at heart with the PMI discipline etched in their DNA and this makes me wonder if a SCRUM Master of a practitioner of SCRUM Methodology can ever go to the other side ?&lt;/p&gt;  &lt;p&gt;Can we actually use agile principles on the other side ? What will Iterative development mean to them, If I am constructing a house how can I go Iterative ? Do I do it room by room , can I start living in a part of house while I get the other part of the house constructed ? Can I really see value / benefit in this ?&amp;#160; Though the Idea might sound outrageous I believe this can be done , the next little project that I do which is non IT, either learning photography or making pottery artifacts I will consciously try and go the agile way !&lt;/p&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9136547" width="1" height="1"&gt;</content><author><name>svemu</name><uri>http://blogs.msdn.com/members/svemu.aspx</uri></author></entry><entry><title>SCRUM and The Nokia Test</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/svemu/archive/2008/06/19/scrum-and-the-nokia-test.aspx" /><id>http://blogs.msdn.com/svemu/archive/2008/06/19/scrum-and-the-nokia-test.aspx</id><published>2008-06-19T08:52:59Z</published><updated>2008-06-19T08:52:59Z</updated><content type="html">&lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;p&gt;Was hearing Jeff Sutherland &lt;a href="http://www.infoq.com/presentations/AgileEnterpriseRealWorldExperience"&gt;talk&lt;/a&gt; about the Nokia test , a test developed by Nokia to test whether you&amp;#8217;re doing&amp;#160; Iterative development or not , and if yes if you&amp;#8217;re really doing SCRUM.&lt;/p&gt;  &lt;p&gt;Are you Iterative ?&lt;/p&gt;  &lt;ul&gt;   &lt;li&gt;Iterations must be timeboxed to less than 4 weeks&lt;/li&gt;    &lt;li&gt;Software features must be tested&amp;#160; and working at the end of each iteration &lt;/li&gt;    &lt;li&gt;The Iteration must start before specification is complete&lt;/li&gt; &lt;/ul&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;p&gt;The second point throws up a debate on what testing means , most of the companies that do partial SCRUM&amp;#160; try and do a separate test sprint and for them the above &amp;#8220;tested&amp;#8221;&amp;#160; - means unit tested , or at the most integration tested but not &amp;#8220;functional &amp;#8220; tested , I did see a lot of implementations diligently trying to go the SCRUM way , and not being able to make it , because this is where they falter.&lt;/p&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;p&gt;Are you implementing SCRUM ?&lt;/p&gt;  &lt;ul&gt;   &lt;li&gt;You know who the product owner is &lt;/li&gt;    &lt;li&gt;There is a product backlog prioritized by business value &lt;/li&gt;    &lt;li&gt;The product backlog has estimates created by the team &lt;/li&gt;    &lt;li&gt;The team generates burndown charts and knows their velocity &lt;/li&gt;    &lt;li&gt;There are no project managers (or anyone else) disrupting the work of the team &lt;/li&gt; &lt;/ul&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;p&gt;Another place&amp;#160; where most of the teams fail , even if you are doing the first part well , is at the product owner part , most of the times in services industry when we try SCRUM , we look at one of the key customer stakeholder as a product owner , and that stakeholder more often than not , does not understand what is expected out of him and that he too is an important Cog in the wheel , the customer needs to be told and trained on the methodology and needs to be completely on-board for SCRUM to be successful.&lt;/p&gt;  &lt;p&gt;Typically most of the SCRUM Masters are project managers who are taking on those roles and some of the old habits die hard , the fourth point above about the &amp;#8220;team&amp;#8221; generating burn charts&amp;#160; will not be true in these cases since the project manager / SCRUM Master has this urge of asking people the status and updating himself &amp;#8211; so the team / team members really do not know how they are all running together , usage of tools becomes very important here , in&amp;#160; the absence of tools , there should at least be enough diligence to make sure that each team member takes upon himself the task of going and updating the status so the burn chart gets generated.&lt;/p&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=8620374" width="1" height="1"&gt;</content><author><name>svemu</name><uri>http://blogs.msdn.com/members/svemu.aspx</uri></author></entry><entry><title>Fat SCRUM</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/svemu/archive/2008/04/12/fat-scrum.aspx" /><id>http://blogs.msdn.com/svemu/archive/2008/04/12/fat-scrum.aspx</id><published>2008-04-12T21:33:27Z</published><updated>2008-04-12T21:33:27Z</updated><content type="html">&lt;p&gt;was reading a very interesting &lt;a href="http://www.netobjectives.com/blogs/is-there-a-fat-agile"&gt;blog&lt;/a&gt;&amp;#160; about Fat agile and lean agile and I realized&amp;#160; that some more things can be added to that list and one most important thing is the what I call the &amp;#8220; CMMi vicious circle of life &amp;#8220;&lt;/p&gt;  &lt;p&gt;This happens when the management has half heartedly given a buy-in simply because they do not want to be left behind in the race of adopting the &amp;#8220;lean&amp;#8221; and agile methods and yet at the same time have process guys that come from the brick and mortar background and do insist on a master project plan ! the process / SQA face of the company also needs to be infused with fresh blood that can audit projects basing on their SCRUM effectiveness and not by the sheer amount of documentation that is needed &lt;/p&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=8385686" width="1" height="1"&gt;</content><author><name>svemu</name><uri>http://blogs.msdn.com/members/svemu.aspx</uri></author></entry><entry><title>Mind sets and Enterprises</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/svemu/archive/2008/03/27/mind-sets-and-enterprises.aspx" /><id>http://blogs.msdn.com/svemu/archive/2008/03/27/mind-sets-and-enterprises.aspx</id><published>2008-03-27T08:52:16Z</published><updated>2008-03-27T08:52:16Z</updated><content type="html">&lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;p&gt;For any enterprise to take on an new methodology or a framework that it can adapt , certain paradigm shifts need to be made in thinking or changing its Mind sets&lt;/p&gt;  &lt;p&gt;What comprises of mind sets ?&lt;/p&gt;  &lt;p&gt;I would say that organizations do not really start as infants , in fact they start as adolescent teenagers ( the painful kinds ! ).The first people who get in to start things , make rules, policies&amp;#160; come with their baggage and start doing things the way they are comfortable with and the way their previous organizations have taught them to . When new people come into the company they start imitating these pretty much like the teenager who imitates his rock /pop idol&amp;#8217;s hairdo.&lt;/p&gt;  &lt;p&gt;And if those mind sets are not the ones&amp;#160; that encourage &amp;#8220;self driven&amp;#8221; way of doing things , they need to be changed .&lt;/p&gt;  &lt;p&gt;HR, recruiting&amp;#160; needs to be aware of these trends in the industry&amp;#160; and should probably have measurable mechanisms that&amp;#160; look for a couple of things &lt;/p&gt;  &lt;p&gt;1.&amp;gt; How self driven is a resource ? &lt;/p&gt;  &lt;p&gt;2.&amp;gt; How adaptable to change is the resource being hired&amp;#160; ?&lt;/p&gt;  &lt;p&gt;Getting a change , shift in thinking&amp;#160; never works in Isolation ,it needs to be well thought out and needs to be collaboratively tackled .&lt;/p&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=8339060" width="1" height="1"&gt;</content><author><name>svemu</name><uri>http://blogs.msdn.com/members/svemu.aspx</uri></author></entry><entry><title>SCRUM and enterprise adoption</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/svemu/archive/2008/03/23/scrum-and-enterprise-adoption.aspx" /><id>http://blogs.msdn.com/svemu/archive/2008/03/23/scrum-and-enterprise-adoption.aspx</id><published>2008-03-23T11:53:06Z</published><updated>2008-03-23T11:53:06Z</updated><content type="html">&lt;p&gt;&lt;strong&gt;What kind of enterprises would be willing to take a risk that fundamentally changes the way they work ?How do we get conventional organizations that believe in strong hierarchies to adopt SCRUM ?&lt;/strong&gt;&lt;/p&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;p&gt;Traditionally organizations that believe in experimenting and wanting to adopt to new trends , and the companies that believe in making new products do jump at any opportunity that challenges the conventional ways ,&amp;#160; show a product company&amp;#160; that there is no major documentation , no &amp;#8220;CMMi&amp;#8221; level documentation that is needed and no heavy process and it would jump at the first opportunity to go the SCRUM way ,really we&amp;#8217;re not talking about enterprises of that sort.&lt;/p&gt;  &lt;p&gt;Imagine a company&amp;#160; &amp;#8220; A&amp;#8221; that has at least 12-14&amp;#160; different titles between Software engineer and&amp;#160; &amp;#8220; General manager &amp;#8220; , can you really get that org to use SCRUM ? the answer I am afraid is very disappointing ! the adoption fails at all levels and it has to be solved both ways bottom up and top down&lt;/p&gt;  &lt;p&gt;Lets take a cross section of this people at all levels and get them into a room and start talking about how SCRUM works and how we can leverage it&amp;#160; to create products faster , the first challenge that I get would be is when I talk about self organization , even a software engineer who is last in the food chain would say &amp;#8220; if I do all the planning ,what&amp;#8217;ll my lead do&amp;#160; ? &amp;#8220; this coming from a young lad who just passed out of college is very disheartening , yet there seems to be a sad reality that&amp;#8217;s in the face for us &amp;#8211; he is not saying that because he doesn't want to take responsibility he is saying that because these organizations traditionally do not reward aggression , passion and risk takers , these companies have middle managers and managers that sit in glass rooms and talk to these fresh engineers and tell them one constant thing , year after year and appraisal after appraisal &amp;#8220;you need to be more proactive &amp;#8220; and by that they mean that these guys take up the additional administrative responsibilities that the leads are supposed to be doing (E.g: collating the defect data etc for the status reports) , but when the guy actually starts taking a stab at being proactive&amp;#160; on the design front , it hits him back and his appraisal report this time around would have a statement like &amp;#8220; needs to perform well in the real of his roles and responsibilities&amp;#8221; ! the mid management and the technical leads start feeling threatened and then they nip that proactive-ness&amp;#160; in the bud and then the whole concept of self organization falls flat ! &lt;/p&gt;  &lt;p&gt;This happens more so in the Asian subcontinent, how does one tackle this , when I was doing this : I was&amp;#160; told by a middle manager &amp;#8220;&amp;#160; I don't think this works well in real life&amp;#160; this is good only on paper &amp;#8221; what is it that i can tell him ! ?&amp;#160; &lt;/p&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=8332097" width="1" height="1"&gt;</content><author><name>svemu</name><uri>http://blogs.msdn.com/members/svemu.aspx</uri></author></entry><entry><title>Hello World</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/svemu/archive/2008/03/21/hello-world.aspx" /><id>http://blogs.msdn.com/svemu/archive/2008/03/21/hello-world.aspx</id><published>2008-03-21T14:00:47Z</published><updated>2008-03-21T14:00:47Z</updated><content type="html">&lt;p&gt;Hello world &lt;/p&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=8328921" width="1" height="1"&gt;</content><author><name>svemu</name><uri>http://blogs.msdn.com/members/svemu.aspx</uri></author></entry></feed>