There should be NO 8-week sprint 0! - The first sprint really is no
different to all the other sprints. It should follow the same rules as of
the other sprints as well. If anything it should be SHORTER (shorter sprint
is good to form teams, team goals and rules, finding impediments, and doing
that
Thanks all for the input, and Adrian and Liz for the links.
I have been reading through some (not yet all) of the agile threads on this
list, and a number of people seem to be saying 'yes we do start just one
sprint ahead of development, but it is usually very painful'...especially if
there is no
Hiya,
Folks interested in this topic might like to read Lane Halley's
recent journal post at http://tinyurl.com/5t6m4y. She makes some
really coherent points there, IMHO!
Also, I thought that Alan Cooper's keynote presented at the Agile
2008 conference was pretty ground-breaking. And it may well
hey jessica
i work for an organization that recently moved from RUP to Agile, it
can be a really exciting transition.
before you decide on where you fall on this fence i would soak up all
you can about the ideal agile team and then look at your organization
itself and identify/forecast pain poin
Webster
Director of Technology and User Experience
Adobe Consulting
m: +44 7917 428 947
Registered Office: 151 St Vincent Street, Glasgow G2 5NJ. Company No. SC101089
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Robert Hoekman J
On 4 Nov 2008, at 20:58, Elizabeth Whitworth wrote:
[snip]
It would be great to hear the experiences of others on this list in
resolving design and agile methods.
[snip]
The biggest change I've noticed in my own behaviour was a move away
from producing "documentation" in the form of hi-fi wi
On 4 Nov 2008, at 21:24, Robert Hoekman Jr wrote:
My experience is very similar to Elizabeth's, except we spent about 8
weeks on "sprint 0" when we built the groundwork for our core
product.
Much has been said on this list about Agile and UX already, so I
won't get
into it. I just wanted t
Good point, Robert...
Full disclosure: The '8 week sprint' was the beginning of the
project, my second 8 weeks with the company, and my development
team's first 8 weeks. That is, they brought the agile methodology
in and I did my best to keep up with them as much as humanly possible
the entire t
>
> My experience is very similar to Elizabeth's, except we spent about 8
> weeks on "sprint 0" when we built the groundwork for our core
> product.
Much has been said on this list about Agile and UX already, so I won't get
into it. I just wanted to say one thing:
You two are incredibly lucky. I
My experience is very similar to Elizabeth's, except we spent about 8
weeks on "sprint 0" when we built the groundwork for our core
product.
I came at my current company from a waterfall-driven environment,
I'm the only designer, and found the same hurdles in the beginning.
I spent 2-3 weeks prio
I'm a user experience specialist that came into a company already using
agile practices. When I first got there I tried to jump straight into the
sprints with interaction designs. This resulted in a lot of confusion,
unnecessary changes, and a less than ideal user interface.
We took a step back on
On 10 Jan 2008, at 14:38, Michael Tuminello wrote:
> For me, I can't say that it does very much. That's part of the
> reason I'm headed down to interaction 08 - for the agile/uxd workshop.
[snip]
On the subject of conferences...
The Agile 2008 Conference (Toronto, Aug 4-8) this
year has a U
12 matches
Mail list logo
