TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
I feel that scrum has many built-in contradictions. You should be able to respond to change, yet you must commit to your goals. Process is undervalued, yet the process must be followed to do scrum right. I could go on. As I mentioned, we were committed to Scrum from the get-go. We have had training. We also do team-building. We have our personalities evaluated. We have open work areas...
I don't think I am alone in my frustration. What I suspect is, Scrum has some optimal team size level.
>
> My intent is not to disrespect but to shed light on the possibilities.
> It's absolutely possible to make things work, but the trick is that
> the changes have to be embraced. I fully realize there are
> organizations that - for whatever reason - do not embrace change well
> and do not deal with issues appropriately. That certainly doesn't mean
> that we should take our eyes off the prize.
>
> I asked you about the session because you posted about it, and assumed
> you were the speaker (plugging your session). Wrong assumption on my
> part.
>
> On Wed, Sep 15, 2010 at 11:59 AM, Spectrum Writing
> <info -at- spectrumwritingllc -dot- com> wrote:
> > Bill,
> >
> > I don't know, just the topic itself was listed. I do know that from personal
> > experience in not one, but two separate organizations, that as a lone
> > writer, Scrum was indeed difficult. Yes, it can work without "hummingbird
> > behavior," but the effort to make it work darn near overwhelmed the ultimate
> > objective of getting documentation done. I make the analogy to the physical
> > sciences - some things simply aren't scalable in either direction.
> >
> > I am glad that you seemed to have gotten Scrum to work for you as a Lone
> > Writer, but don't discount the experiences and emotions of those of us who
> > have suffered it. We weren't the only ones on the teams and w/out all of the
> > team members understanding their roles and w/ the organizations just
> > throwing scrum into place w/out any formal research or training in it (in
> > both of the organizations that I was because it was the latest buzzword and
> > the CTOs in both places loved over using the phrase "we need to be on the
> > bleeding edge"), it was a nightmare.
> >
> > Different people on these lists have different experiences with the same
> > things and we need to respect that w/out judging them or coming down on them
> > like we "know it all."
>
> --
> Bill Swallow
>
> Twitter: @techcommdood
> Blog: http://techcommdood.com
> LinkedIn: http://www.linkedin.com/in/techcommdood
Create and publish documentation through multiple channels with Doc-To-Help.
Choose your authoring formats and get any output you may need. Try
Doc-To-Help, now with MS SharePoint integration, free for 30-days. http://www.doctohelp.com
LavaCon 2010 in San Diego Sept 29 - Oct 2 is now open for registration.
Use referral code TECHWR-L for $50 off conference tuition!
See program at: http://lavacon.org/
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-