>> We unit and web test, and also as Bobby says do a week long manual regression test.
We used to do something like that, but we also only released quarterly. We're down to monthly releases now, and removed the "regression sprint", if there really is such as thing. I think it's actually helped quality to remove the "regression sprint", because you can't just check something in and assume or hope the regression sprint will find it. Communication between engineers and testers has increased because of this, as has are willingness to pay attention to quality from day 1 on each sprint. On Thu, Dec 23, 2010 at 10:19 AM, Adron Hall <[email protected]> wrote: > Two comments regarding documentation & installation. > > First Comment: > If the install requires documentation it probably needs some changes to the > design of the architecture, severely needs these changes. There are lots of > products out there that are just vastly more complex to install than need > be. One of the products that comes to mind is Webtrends. The installer is > 500 or so MB, plus requires a big manual (nasty word doc, 50-100 pages or > so) and all sorts of hackery. In my opinion, and most customers' opinion, > that is totally unacceptable. It really goes to show why when Webtrends > started offering the OnDemand (SaaS) choice they easily migrated 96% of the > customers to that solution. > > Second Comment: > Word documents are horrible for documentation. Absolutely build a wiki. > Make it public. Modernize it and make it SEO friendly. Word documents are > like the enemy of human progress at this point. At least for things that > should not need printed out, like installation instructions for software. > :) > > Anyway, just wanted to throw those two comments in as strongly urged ideas > for improvement & product quality ideas. > > Cheers! Adron > > > On Thu, Dec 23, 2010 at 8:41 AM, Anne Wax <[email protected]> wrote: > >> I appreciate all the comments and discussion. >> >> Yes, quality goes in all along the way. We unit and web test, and also as >> Bobby says do a week long manual regression test. >> >> But..in the end, don't you see/learn new things at the end of the cycle, >> that you may want to incorporate into the next cycle (or a future cycle). >> Or once the whole feature is before your eyes, you realize that later things >> you did really should be refactored back into the whole? Or tools should be >> enhanced? >> >> For me, this conversation is underscoring the importance of doing the >> refactoring as we go, which we do as much as possible, while, as Justin says >> meeting our customer deliverables/deadlines. >> >> Also for us, the product includes technical documentation such as >> installation guides for new features. Our discussions are leading us to the >> conclusion that we need to build customer facing documentation such as >> installation guides as part of the initial build vs at the end of a >> release. They tend to uncover issues, especially because our customers have >> varied environments (dual/single web server, server farms, different >> versions of IIS etc, varied security policies/implementations). I have a >> feeling we are headed in that direction very soon. >> >> Anne >> >> >> >> On Thu, Dec 23, 2010 at 7:08 AM, Bobby Johnson >> <[email protected]>wrote: >> >>> Always, I think the main take away with agile is there are no set in >>> stone rules; instead measure and adjust. >>> >>> >>> On Thu, Dec 23, 2010 at 6:55 AM, Justin Bozonier >>> <[email protected]>wrote: >>> >>>> "I would also suggest that the definition of quality in your project >>>> needs to be set up front with clear goals." >>>> >>>> I love that and completely agree (with the caveat that when things >>>> change.. Well.. Things will change). >>>> >>>> <codemonkey expression="big smile" /> >>>> >>>> On Dec 23, 2010, at 6:35 AM, Bobby Johnson <[email protected]> >>>> wrote: >>>> >>>> I would also suggest that the definition of quality in your project >>>> needs to be set up front with clear goals. >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Seattle area Alt.Net" group. >>>> To post to this group, send email to [email protected]. >>>> To unsubscribe from this group, send email to >>>> [email protected]<altnetseattle%[email protected]> >>>> . >>>> For more options, visit this group at >>>> http://groups.google.com/group/altnetseattle?hl=en. >>>> >>> >>> >>> >>> -- >>> "The explanation requiring the fewest assumptions is most likely to be >>> correct." >>> >>> - Occam’s Razor >>> http://en.wikipedia.org/wiki/Occam's_Razor >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Seattle area Alt.Net" group. >>> To post to this group, send email to [email protected]. >>> To unsubscribe from this group, send email to >>> [email protected]<altnetseattle%[email protected]> >>> . >>> For more options, visit this group at >>> http://groups.google.com/group/altnetseattle?hl=en. >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Seattle area Alt.Net" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]<altnetseattle%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/altnetseattle?hl=en. >> > > > > -- > *Adron B Hall* > > *Tech*: http://compositecode.com > *Transit*: http://transitsleuth.com > *Twitter*: http://www.twitter.com/adronbh > > -- > You received this message because you are subscribed to the Google Groups > "Seattle area Alt.Net" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<altnetseattle%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/altnetseattle?hl=en. > -- You received this message because you are subscribed to the Google Groups "Seattle area Alt.Net" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/altnetseattle?hl=en.
