A big hairy task list for planning a doc sprint

We’ve recently held a doc sprint. I thought it may be enlightening, or at least fun, to see the complete list of tasks on our planning page. So here it is, as at one week after the sprint. 🙂

Actually, this list of tasks is not 100% complete. I’ve removed some minutiae to make it a little more palatable. And if you’re looking for a summary that’s easier to read, try this post instead: How to plan a doc sprint.

The list

Done	Task
2 May	Initial contact with Confluence PMs
5 June	Initial contact with Confluence team lead
14 June	Initial contact with Dev Rel team
14 June	Finalise date
14 June	Decide about getting any San Franciscans here in Sydney for the sprint.
23 June	Decide locations for physical sprint and update all relevant pages
19 June	Add dates to tech writers’ calendars
19 June	Add to Sydney Events calendar on Google Calendars.
	Add to Amsterdam Events calendar somewhere
Not required	Add to SF Events calendar somewhere???
21 June	T-shirts
23 June	Update Doc Sprint space on CAC
23 June	Look at points from previous sprint’s retrospective
28 June	Start defining the tutorial wish list.
25 June	Announce the sprint internally
9 July	Issue general invitation to external stakeholders/authors and describe scope
30 July	Ask Joe Clark if he would prepare “best practice” guidelines about what the sprinters should include in their tutorials
23 July	Post invitation on Experts site
20 July	Engage Ambassadors
23 July	List the external participants we want to invite specifically
27 July	Issue targeted invitations to external community authors
26 July	Check the Snippet plugin
7 August	List the Atlassians we want to invite specifically, and invite them personally
8 August	Book room(s) in Sydney for sprint co-location
	Book room(s) in SF for sprint co-location
19 July	Book room(s) in Amsterdam for sprint co-location
1 August	Focus on the teaching and social side of doc sprint
	Finalise authorisation of T-shirts
9 August	Send email message to all participants (external and internal) about preparing for doc sprint
16 August	Set up a tech writer roster
7 August all done	Add the event to all Atlassian attendees’ calendars
7 August all done	Finalise tutorial wish list
9 August	Organise allocation of specific tutorials/tasks to each sprinter
17 August	Compile and publish page containing schedule
	Compile and publish page containing information about online facilities
	Set up chat room
	Set up email distribution list.
	Update the plugin tutorial template
	Organise Bitbucket for the tutorials
Not required	Organise Bamboo for the tutorials on Bibucket
8 August	Organise a meeting of tech writers to check everything is ready
	Think up some fun stuff to do
8 August	Organise DAC edit access for external sprinters
8 August	Add CAC page telling sprinters how to prepare
9 August	Publicise Twitter tag
16 August	Add placeholder for new tutorials on DAC
16 August	Discuss catering for Sydney
21 August	Discuss catering for SF
17 August	Discuss catering for Amsterdam
16 August	Update the guidelines and put them in the DOCSPRINT space on CAC.
19 August	Post a final reminder on EAC
21 August	Do final coordination of Amsterdam with Sherali
9 August – decided not to do this	Post a final reminder on Atlassian blog
16 August	Schedule webinars
21 August	Schedule a practice webinar
	Organise network capabilities in the rooms in Sydney
	Organise network capabilities in the room in SF
	Organise network capabilities in the room in Amsterdam
	Organise cameras in Sydney
	Organise cameras in SF
17 August	Organise cameras in Amsterdam
	Coordinate fun stuff during the sprint
21 August	Fun stuff: golden ticket
24 August	Plan and document the structure of the retrospective and show and tell
	Buy Sydney chocolates.
	Buy SF chocolates.
17 August	Buy Amsterdam chocolates.
19 August	Let reception and experience teams know about the sprint
	After the sprint: Order and distribute T-shirts
	After the sprint: Judge haiku competition and send out prizes
	After the sprint: Write up and collate the results of the retrospective
In progress	After the sprint: Liaise with late sprinters
	After the sprint: Judge golden ticket competition and send out prizes
	After the sprint: Revoke the temporary access rights where necessary
25 August	After the sprint: Update hall of fame
27 August	After the sprint: Send wrapup email to sprinters
In progress	After the sprint: Assess status of Sydney tutorials and chase up the reviewing and publication tasks
In progress	After the sprint: Assess status of Remote tutorials and chase up the reviewing and publication tasks
In progress	After the sprint: Assess status of San Francisco tutorials and chase up the reviewing and publication tasks
In progress	After the sprint: Post an internal write-up of the results
In progress	After the sprint: Post an external write-up of the results
In progress	After the sprint: Review and publish tutorials