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 used to be a part of every team, now I am on the un-team, aka the Island of Misfit Toys. And that ain't Scrum.
I feel that doc can be a part of Scrum when done right, but what about those roles that touch every team but are not product specific like, as I mentioned, the buildmaster?
>
> > The problem is, I am not "on" those teams I support. All of us in support roles are on one team...test automation, build master, DBA, documentation, and quality systems.
> >
> > So we are not interchangeable and no, it is not Scrum. We tried a version on kanban, but the lesson there was it is impossible to use different methodologies on the same project (did we really need to try that experiment?)
>
> Ah, but do you see that you are still using two different methodologies?
>
> --
> 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-
