tag:blogger.com,1999:blog-13831777.post4085361571739596418..comments2024-03-27T09:37:53.071-04:00Comments on Coaching Agility: An Agile Case Study: Litle & Co.Damon Poolehttp://www.blogger.com/profile/16561311551267979837noreply@blogger.comBlogger10125tag:blogger.com,1999:blog-13831777.post-85238876432727207202019-02-05T01:22:58.143-05:002019-02-05T01:22:58.143-05:00Great post very good to read
Best power BI traini...Great post very good to read <br /><a href="https://www.slajobs.com/power-bi-training-in-chennai/" rel="nofollow">Best power BI training course in chennai</a>jefrinhttps://www.blogger.com/profile/12611160413527604608noreply@blogger.comtag:blogger.com,1999:blog-13831777.post-10723183934485985442013-05-13T05:22:06.359-04:002013-05-13T05:22:06.359-04:00Like the fact that all rule was developed by two p...Like the fact that all rule was developed by two people which provides both redundancy for knowledge of all rule and real-time rule review.<br />Axel Ballardhttp://hamishclemons.weebly.com/1/post/2013/04/hiring-an-offshore-software-company-is-not-only-very-economical-but-totally-risk-free-as-well.htmlnoreply@blogger.comtag:blogger.com,1999:blog-13831777.post-62513892666568786082011-07-05T06:54:49.486-04:002011-07-05T06:54:49.486-04:00Hi Damon,
Thanks for this fantastic case study. It...Hi Damon,<br />Thanks for this fantastic case study. It's really nice to see a clear and concise presentation of how Agile principles translate into real benefits.<br />I think the questions raised about PAT testing and design work done in parallel with iterations are just practical ways of dealing with a critical system delivery. The key point is that iterations are monthly and the business benefits from this fast turnaround. Great example of Agile working well.<br />Thanks again,<br />PetePete Karashttp://www.peterkaras.comnoreply@blogger.comtag:blogger.com,1999:blog-13831777.post-73637539753770368192009-11-04T09:41:41.203-05:002009-11-04T09:41:41.203-05:00Hi Nancy,
Thanks for the question. Unfortunately,...Hi Nancy,<br /><br />Thanks for the question. Unfortunately, I don't have that information.<br /><br />DamonDamon Poolehttps://www.blogger.com/profile/16561311551267979837noreply@blogger.comtag:blogger.com,1999:blog-13831777.post-46267709052176788962009-11-03T20:03:56.643-05:002009-11-03T20:03:56.643-05:00Hi Damon - Nice case study. I'd be interested ...Hi Damon - Nice case study. I'd be interested in knowing some statistics such as output in terms of function points per person-day, defects per function point, which can be stated as defects found prior to deployment and also after deployment. This type of data is helpful in comparing between companies. Thanks!Unknownhttps://www.blogger.com/profile/00718300192688314521noreply@blogger.comtag:blogger.com,1999:blog-13831777.post-88924827206316922642009-10-19T18:24:06.455-04:002009-10-19T18:24:06.455-04:00Hi, Thanks for the great post. What other case stu...Hi, Thanks for the great post. What other case studies are you looking at in your research?Unknownhttps://www.blogger.com/profile/12029212796497153938noreply@blogger.comtag:blogger.com,1999:blog-13831777.post-1127881734063403912008-06-01T16:27:00.000-04:002008-06-01T16:27:00.000-04:00Hi Maxim,Good questions! I'm working on an updated...Hi Maxim,<BR/><BR/>Good questions! I'm working on an updated version and will try to include the answers to your questions in it.Damon Poolehttps://www.blogger.com/profile/16561311551267979837noreply@blogger.comtag:blogger.com,1999:blog-13831777.post-29181775107692094952008-05-28T01:00:00.000-04:002008-05-28T01:00:00.000-04:00Thank you for sharing this process!Speaking about ...Thank you for sharing this process!<BR/><BR/>Speaking about overlapping iterations. What happens, when during the PAT a blocker is found and therefore "no go" decision has been made? Do they try to fix it right away and re-release or do their users have to wait another month for the next iteration?<BR/><BR/>And related question. How do they do hot fixes to the productive version? Do they skip PAT before deploying it or do they incorporate them into the current iteration (so again, everybody has to wait for up to one month for the fix)?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-13831777.post-49835907681970223512008-05-23T22:47:00.000-04:002008-05-23T22:47:00.000-04:00Hi Paul,Thanks for your comments and observations....Hi Paul,<BR/><BR/>Thanks for your comments and observations.<BR/><BR/>On re-reading the case study with your comments in mind I realize that I didn't do a very good job of conveying how they do overlapping iterations. It could probably use an illustration. The impression that they are doing short waterfalls is an artifact of my poor explanation.<BR/><BR/>I will double-check with Dave to make sure I've got the details correct, but basically the week of planning (not design) involves things like discussing what the theme of the iteration will be, producing the product backlog, and things like that. The planning overlaps with the last week of the previous 4 week development cycle.<BR/><BR/>Regular test development and execution as well as integration are happening continuously during the 4 week development cycle.<BR/><BR/>Once that is done, the software is "shipped" to the production team. The production team does the Production Acceptance Testing (PAT). The PAT is basically a dry-run of putting the software into production. While PAT is happening, engineering has already started the next iteration.<BR/><BR/>I hope this clears things up and I'll update the case study with more details when I can.Damon Poolehttps://www.blogger.com/profile/16561311551267979837noreply@blogger.comtag:blogger.com,1999:blog-13831777.post-85748552188368208012008-05-23T17:30:00.000-04:002008-05-23T17:30:00.000-04:00It sounds like they started with all the principle...It sounds like they started with all the principles of agile and have worked out an acceptable medium that allows for short waterfalls rather than XP.<BR/><BR/>Principally the end result doesn't appear to be very agile, while some practices are followed many others have been twisted back to the old waterfall ways (1 week of design, 4 weeks of dev followed by 2 weeks of testing can hardly be called agile!).<BR/><BR/>I certainly wouldn't call this a model example, infact I'd call it waterfall done better. But it does at least show that just using some of the practices can result in improvement in software quality.Paul Keeblehttps://www.blogger.com/profile/01672124418792339749noreply@blogger.com