Note on pushing to beta

[Tim Sutcliffe]

Hi guys,

A release went up yesterday to beta that has some big bugs in it.  We can talk as a group. but just a reminder that, as much as i don't wan't this job, I'm acting as QA / release manager at the moment, so we shouldn't be pushing from staging to beta without

1. Letting me know

2. Waiting for me to give the thumbs up

We have real users actually using our site now, so what's live on beta must always be awesome.

Cheers,

t

[Alex Chaffee]

On Fri, Nov 30, 2012 at 12:27 PM, Tim Sutcliffe <t...@groupiter.com> wrote:

We have real users actually using our site now, so what's live on beta must always be awesome.

+1

Theo and I are currently fixing the myriad bugs visible on staging and beta; we're doing a staging deploy soon.

--
Alex Chaffee - al...@stinky.com
http://alexchaffee.com

http://codelikethis.com
http://twitter.com/alexch

[Tim Sutcliffe]

Just a follow on, I had a look at pivotal, and there was a lot of tickets (from everyone, myself included) for stories that:

 - Have been started, that have not been marked as started

 - That have been pushed to beta, but have not been delivered

 - That have been pushed to beta, but have not been acepted

Have a look at this from pivotal (tl;dr below)

Story Workflow

At the beginning of a typical day, a developer will pick an unstarted story in the current iteration and click its start button (thereby becoming its owner unless it already has one).

When work on the story is complete, the developer will click the finish button. The "deliver" button will appear; when the product is ready for acceptance testing/evaluation, a team member will click the "deliver" button. This will indicate to the story requester (visually in Tracker and via email) that they can now provide feedback on the story by accepting or rejecting it.

If the story requester (or someone else representing the customer) accepts the story, the story will turn green and move to the top of the current iteration. At the end of the iteration, accepted stories move to the done panel.

If the story is rejected, it will move to the end of the list of stories that are currently in progress. It's state will be set to "rejected", and a "restart" button will appear. This indicates to the owner of the story that more work is needed. When a story is rejected, Tracker prompts the rejector for a reason, which subsequently appears as a comment in the story. The owner of the story is notified by email.

Story Workflow (TL;DR)

0.  Don't start any work unless it has a ticket, that has been 

  - Move into the current sprint by the PM   

  - estimated

  - discussed with the team, from a technical perspective

1.  When you start work, click 'Start'.  This will prevent two people working on the same ticket.

2.  When you're done, click finnish.  It's ready for QA.  I get an accept / reject.

3.  When I have QA'd, I click accept / reject

4.  When everything in the sprint is green, I / we push

(I hope i have that right, feedback / comments welcome)

So, I'm not at all upset, and I'm part of the problem.  

But we really are getting close to have something awesome.  So far, we have invited about 100 users, and just 1 team is really using the product (and they are really using it, it's insane.  Tried to share on groupiter, not working).  Getting those first users is  HARD and i only have a small and finite number of people I can lean on to give it a spin. So it must feel like it works. It must be awesome. So, up until now we've been a bit hacky re deployment, but this is getting real folks.  

Cheers,

T

On Fri, Nov 30, 2012 at 12:27 PM, Tim Sutcliffe <t...@groupiter.com> wrote:

[Tim Sutcliffe]

Great, thank you.  I'll do some QA tomorrow.

t

--