<?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/'><id>tag:blogger.com,1999:blog-5250963007270448594.post8681906274604215360..comments</id><updated>2011-01-23T09:18:57.941-08:00</updated><category term='Agile Tool'/><category term='ALM Tools'/><category term='Time Management'/><category term='Requirements Management'/><category term='Test Management'/><category term='google marketing brand equity Nike'/><category term='Project Team Productivity'/><category term='Agile ALM Lean Kanban Waterfall SCRUM CMMI'/><category term='Traceability'/><category term='Process Maturity'/><category term='Agile ALM'/><category term='Measurement in Software Projects'/><category term='Agile Project Management'/><category term='Application Lifecycle Management'/><category term='Capacity Planning'/><category term='Release Scoping'/><category term='Lean/ Kanban'/><category term='PPM'/><category term='Defect Management'/><category term='Agile Metrics'/><category term='Quality'/><category term='Scrumban'/><category term='ALM Agile Waterfall Software Process Lean'/><category term='Lean Software Development'/><category term='Software Estimation'/><category term='SaaS'/><category term='LSSC11'/><category term='ALM'/><category term='Scaled Agile ALM'/><category term='Kanban'/><category term='Scrum Tools'/><category term='Scrum'/><category term='Change Management'/><category term='Release Management'/><category term='Lean SSC'/><category term='Kanban for Distributed Teams'/><category term='Effort Tracking'/><category term='Project Portfolio Management'/><category term='Kanban Tool'/><category term='Scaled Agile ALM Tool'/><title type='text'>Comments on The Digité Fountainhead: When is a project too small or too short for ALM?</title><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://blog.digite.com/feeds/8681906274604215360/comments/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5250963007270448594/8681906274604215360/comments/default'/><link rel='alternate' type='text/html' href='http://blog.digite.com/2011/01/when-is-project-too-small-or-too-short.html'/><author><name>Digité, Inc.</name><uri>http://www.blogger.com/profile/06102985784968070126</uri><email>noreply@blogger.com</email><gd:image xmlns:gd='http://schemas.google.com/g/2005' 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>4</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-5250963007270448594.post-5859430714073449214</id><published>2011-01-23T09:18:57.941-08:00</published><updated>2011-01-23T09:18:57.941-08:00</updated><title type='text'>To the extent that one is looking at purely a tool...</title><content type='html'>To the extent that one is looking at purely a tool usage perspective, the use of ANY tool may be considered essential vs. an overhead depending on a number of factors - culture, size of project, grographical spread of the team, etc.  If you consider the current situation of many collocated teams doing Scrum or Kanban projects, they are very happy with simply the physical Story/ Kanban board and  have zero interest in any electronic tool.  However, from the &amp;quot;application&amp;#39;s&amp;quot; perspective, whatever work they do would still be a part of that application&amp;#39;s lifecycle management.  The point I was making is that an &amp;quot;ALM&amp;quot; discussion is not and should not just be an &amp;quot;ALM tool&amp;quot; discussion.</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5250963007270448594/8681906274604215360/comments/default/5859430714073449214'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5250963007270448594/8681906274604215360/comments/default/5859430714073449214'/><link rel='alternate' type='text/html' href='http://blog.digite.com/2011/01/when-is-project-too-small-or-too-short.html?showComment=1295803137941#c5859430714073449214' title=''/><author><name>Mahesh Singh</name><uri>http://www.blogger.com/profile/02319792158123798925</uri><email>noreply@blogger.com</email><gd:image xmlns:gd='http://schemas.google.com/g/2005' rel='http://schemas.google.com/g/2005#thumbnail' width='25' height='32' src='http://1.bp.blogspot.com/_KIQQm_uuW0Q/SdW2QdMEYgI/AAAAAAAABAg/UsD0QLUnBXw/S220/IMG_2939-A1.jpg'/></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://blog.digite.com/2011/01/when-is-project-too-small-or-too-short.html' ref='tag:blogger.com,1999:blog-5250963007270448594.post-8681906274604215360' source='http://www.blogger.com/feeds/5250963007270448594/posts/default/8681906274604215360' type='text/html'/><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='blogger.itemClass' value='pid-1346162903'/></entry><entry><id>tag:blogger.com,1999:blog-5250963007270448594.post-453197700796622209</id><published>2011-01-23T07:05:31.613-08:00</published><updated>2011-01-23T07:05:31.613-08:00</updated><title type='text'>Sudi, yes.  You are correct.  I would even state i...</title><content type='html'>Sudi, yes.  You are correct.  I would even state it more bluntly and expand it a bit. An ALM solution that is put in place for all to use will make everyone better by consolidation of knowledge and efforts. Thus, avoiding gaps and overlaps. Whether they are good, or not so good, they will be better as a team by adherance to the process. Even a poorly thought out process that is followed is better than a good process that is not followed. The organizations who are individual centric do not get the most out of their teams if that means a concession to the ALM process. Look at the Yankees... Great individual contributors, but they do not play well as a team and therefore fall short of their goals. You can have great talent, but if they do not work as a shared knowledge unit - following an ALM process, they will not reach their ultimate team potential.</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5250963007270448594/8681906274604215360/comments/default/453197700796622209'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5250963007270448594/8681906274604215360/comments/default/453197700796622209'/><link rel='alternate' type='text/html' href='http://blog.digite.com/2011/01/when-is-project-too-small-or-too-short.html?showComment=1295795131613#c453197700796622209' title=''/><author><name>M. Amend</name><uri>http://www.blogger.com/profile/14286010565397868957</uri><email>noreply@blogger.com</email><gd:image xmlns:gd='http://schemas.google.com/g/2005' rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://blog.digite.com/2011/01/when-is-project-too-small-or-too-short.html' ref='tag:blogger.com,1999:blog-5250963007270448594.post-8681906274604215360' source='http://www.blogger.com/feeds/5250963007270448594/posts/default/8681906274604215360' type='text/html'/><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='blogger.itemClass' value='pid-1238545614'/></entry><entry><id>tag:blogger.com,1999:blog-5250963007270448594.post-4049421784908834846</id><published>2011-01-22T20:32:31.168-08:00</published><updated>2011-01-22T20:32:31.168-08:00</updated><title type='text'>I think there is another aspect of organization cu...</title><content type='html'>I think there is another aspect of organization culture. Some organizations are inherently process centric, metric centric (not just for the show of it). Some organizations tend to be  individual centric where they depend on maverick leaders, individual heroism. ALM tools will add immense value to former category of organizations. To the other group, it will keep questioning the value of such a tool but still do continue to use it. They find it politically incorrect to say that they are not process and data centric.</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5250963007270448594/8681906274604215360/comments/default/4049421784908834846'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5250963007270448594/8681906274604215360/comments/default/4049421784908834846'/><link rel='alternate' type='text/html' href='http://blog.digite.com/2011/01/when-is-project-too-small-or-too-short.html?showComment=1295757151168#c4049421784908834846' title=''/><author><name>Sudi</name><uri>http://www.blogger.com/profile/10540044000319418170</uri><email>noreply@blogger.com</email><gd:image xmlns:gd='http://schemas.google.com/g/2005' rel='http://schemas.google.com/g/2005#thumbnail' width='27' height='32' src='http://4.bp.blogspot.com/_jn2QrmYYC3c/SpnuYkEiaAI/AAAAAAAADOA/pQMfqgJ39l0/S220/Self+01.JPG'/></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://blog.digite.com/2011/01/when-is-project-too-small-or-too-short.html' ref='tag:blogger.com,1999:blog-5250963007270448594.post-8681906274604215360' source='http://www.blogger.com/feeds/5250963007270448594/posts/default/8681906274604215360' type='text/html'/><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='blogger.itemClass' value='pid-167329677'/></entry><entry><id>tag:blogger.com,1999:blog-5250963007270448594.post-7962849327550210299</id><published>2011-01-21T19:31:32.895-08:00</published><updated>2011-01-21T19:31:32.895-08:00</updated><title type='text'>I might add that the exception swallows the rule. ...</title><content type='html'>I might add that the exception swallows the rule. If you make exceptions to the ALM process management by exclusion, then you do not follow an ALM process. Every change, small or large, can have extreme consequences if not documented properly for later consideration. &lt;br /&gt;&lt;br /&gt;Well done on the three points!</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5250963007270448594/8681906274604215360/comments/default/7962849327550210299'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5250963007270448594/8681906274604215360/comments/default/7962849327550210299'/><link rel='alternate' type='text/html' href='http://blog.digite.com/2011/01/when-is-project-too-small-or-too-short.html?showComment=1295667092895#c7962849327550210299' title=''/><author><name>M. Amend</name><uri>http://www.blogger.com/profile/14286010565397868957</uri><email>noreply@blogger.com</email><gd:image xmlns:gd='http://schemas.google.com/g/2005' rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://blog.digite.com/2011/01/when-is-project-too-small-or-too-short.html' ref='tag:blogger.com,1999:blog-5250963007270448594.post-8681906274604215360' source='http://www.blogger.com/feeds/5250963007270448594/posts/default/8681906274604215360' type='text/html'/><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='blogger.itemClass' value='pid-1238545614'/></entry></feed>
