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.
On Tue, Apr 1, 2014 at 9:49 AM, McLauchlan, Kevin <
Kevin -dot- McLauchlan -at- safenet-inc -dot- com> wrote:
> So do you normally find it valuable to do any writing - as opposed to
> planning and research - in the early sprints leading to a release? Or does
> it reliably make more sense for you to hold off until the Jell-o begins to
> set a bit, before trying to nail it to the wall?
>
I'm always writing, even if it's just a list of things that I think I need
to write about (or research, or check at the end of the Sprint, or
questions to ask....You get the idea.).
> For bonus points, is anyone being successfully Agile, where the Product
> Manager does NOT attend a significant number of scrums (any...)?
>
I've worked on teams where the Product Manager is at every meeting, and
teams where the Product Manager only showed up for Sprint demos, and both
seemed to work OK.
For further bonus points, is anyone being successfully Agile where your
> Scrum Masters are just the engineering team leaders and managers, and NOT
> people whose primary duty is leading/driving sprints and scrums? In other
> words, is a purpose-built Scrum Master necessary for Agile success, or can
> it be just anybody with the discipline and clout to keep meetings on track
> and moving briskly, and maybe they read (part of) a book about Agile?
>
At four different jobs now, I don't think I've ever worked somewhere were
we had someone whose sole role was just to be a Scrum Master. Our scrum
masters have always been engineering managers, or one of the team leads or
a developer.
--
Julie Stickler http://heratech.wordpress.com/
Blogging about Agile and technical writing
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Doc-To-Help 2014 v1 now available. SharePoint 2013 support, NetHelp enhancements, and more. Read all about it.