tag:blogger.com,1999:blog-13831777.post4704810852643643608..comments2024-03-27T09:37:53.071-04:00Comments on Coaching Agility: Unconsciously AgileDamon Poolehttp://www.blogger.com/profile/16561311551267979837noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-13831777.post-71492742488084560272017-08-11T02:54:12.058-04:002017-08-11T02:54:12.058-04:00Without conscious intent and the synchronizing sig...Without conscious intent and the synchronizing signal of short iterations it is hard to notice the difference between being on the path and off the path unless you stay on the path for a while.Nicely put indeed Damon!!Apart from studying Agile methodology and implementing it on a software development project, it is quite interesting to understand the degree to which you are Agile.Why don't you have a look at our piece of work.Click on: https://www.scrumstudy.com/blog/how-agile-are-you-2/Ethan Moorenoreply@blogger.comtag:blogger.com,1999:blog-13831777.post-19385249472745789912007-12-22T01:26:00.000-05:002007-12-22T01:26:00.000-05:00Isaac,You don't have to release often to be Agile....Isaac,<BR/><BR/>You don't have to release often to be Agile. There are benefits to releasing often, but they are not the only benefits nor are they the lions share of the benefits. See my post on the definition of Agile which talks about the complete list of benefits and where they come from.<BR/><BR/>If the product designers produce their designs as a result of interacting with customers, they yes they could be considered a customer proxy.<BR/><BR/>All of the Agile practices except for short timeboxed iterations can be introduced without major disruption and many have been or are in the process of being introduced in many places without any reference to Agile. Refactoring, Continuous <BR/>Integration, and Test Driven Development are becoming very popular independently of Agile.<BR/><BR/>In the end, I believe your best tool is education. Start finding people that are like minded or open minded and suggest that they at least read a book or two. I think "The Toyota Way" or "Lean Software Development" are both excellent starting points which lay the groundwork without hitting one over the head with the message.Damon Poolehttps://www.blogger.com/profile/16561311551267979837noreply@blogger.comtag:blogger.com,1999:blog-13831777.post-28445529477996580552007-12-17T18:59:00.000-05:002007-12-17T18:59:00.000-05:00Hi,Great post. Let me go even a step further. I am...Hi,<BR/><BR/>Great post. Let me go even a step further. I am a true believer that agile practices are the way to go. But, I work for a company that develops commercial products and we are in yearly release cycles.<BR/><BR/>For a long time, I've been trying to push agile practices, and people react negatively to that because they make the wrong assumptions. They say, we do not release often, things are different in our world. We do not have direct contact with customers, etc. <BR/><BR/>People often do not see that we release 2-3 builds a week to QA, can you be more agile than that? Furthermore, Product Designers complain we have not implemented exactly what the spec said. Aren't they in some way our customers? Aren't they the ones that decide if a feature is written correctly or not?<BR/><BR/>Working at this pace and avoiding agile practices is a nightmare, so my battle now is how can I introduce agile practices without telling people that they are agile.Isaac Rodriguezhttps://www.blogger.com/profile/04341790584083395302noreply@blogger.comtag:blogger.com,1999:blog-13831777.post-78361563632788633962007-12-07T15:48:00.000-05:002007-12-07T15:48:00.000-05:00You bring up a good point Artem. Certainly an iter...You bring up a good point Artem. Certainly an iteration and a patch/maintenance release are not guaranteed to be exactly the same. While Agile helps when there is not a clear understanding of what exactly is required, it is perfectly ok if you do happen to know what is required. My point is that folks may have more experience that overlaps with Agile than they realize.Damon Poolehttps://www.blogger.com/profile/16561311551267979837noreply@blogger.comtag:blogger.com,1999:blog-13831777.post-54277457347929830832007-12-07T15:32:00.000-05:002007-12-07T15:32:00.000-05:00There is a bit of a difference between patches / m...There is a bit of a difference between patches / maintenance releases and "normal" agile development. Typically when patch is needed there is quite clear understanding of what exactly is required.<BR/><BR/>Even though prioritizing might still be useful, the requirements are quite well detailed up-front.Anonymousnoreply@blogger.com