We recommend:
back to book listing
Amazon recommends:
back to book listing
2007/05/26
User Stories: a mindmap and a quick overview
Below is a simple mindmap for "Stories"
it in our project. In short we:
Write small, deliverable, user stories ( 3-5 days )
Store them in Jira and on sticky notes
Include in each story a brief summary that highlights what it does,
why its valuable, and several tests
Evolve them from simple reminders, to placeholders for our
understanding, and finally an agreement on when we are "done".
This gives us some advantages:
(1) We are able to be more flexible since the details can be fleshed
out when the time is right
(2) We are able to collaborate and focus on verbal communication
instead of passing on written documents
I'll elaborate a bit on of each of these points.
Writing small, deliverable stories
Finding the "right" size for your stories is somewhat tricky. Since
people have very differnet ways of specifing "size" you are likely to
have to experiment and go with what fits your team. For us, it seems
that we have had most success with stories that a single developer
would use 3-5 days on.
Storing in Jira and on sticky notes
The simplest storage method is just to write things on a sticky note
and place it on your wall. It's quick, easy, and visible. Using some
software to store them can also be quite useful. In an offshore
situation that kind of becomes necessary.
Even if you use some software place to store your stories, I have
found that it's good to keep writing those sticky notes and getting
them up on the wall. This way the stories are always visible to
everybody, and there is also just a "feel good" factor in "physically"
taking them down when you are done.
Include in each story a brief summary that highlights what it does,
why its valuable, and several tests
One of the more tricky things is finding out how much to put into a
story. Again, this depends on how your team feels about it.
Before we started using stories we have some small "specifications".
These where typically a few pages with some text and screenshots.
Switching to user stories can be a slight shock to the system. The
most common question I got was, "Where are the details?".
Well, we do actually have a lot of "details" in our stories. These are
represented by the tests and an a GUI prototype. User stories are not
about masking out details. In order to deliver the story you need to
flesh out these details ( as it becomes necessary ), and in most cases
write them down as tests. In my world, the difference between user
stories, and some kind of "specification" is not really that big. It's
how you get there that counts. It's the collaborative, lightweight
"process" of going from an idea to an understanding of when a story is
"done".
In my experience, one of the biggest challenges is to make sure we
actually do the things necessary to make stories work. If you don't
discuss them properly, sincerly write down the tests, and collaborate
during them whole process, then your stories become more of a problem
than a solution.
Evolve them from simple reminders, to placeholders for our
understanding, and finally an understanding of when we are "done"
The reason why stories work is that they are flexible and demand that
you collaborate. A story starts out just as a simple reminder of a
discussion with the client. It evolves as you discuss it with other
people in the team, and you flesh out some details. In the end it
guides you towards aswering that simple question, "when are we
done?".
Ragnar Birgisson, Mar 07, for Agile-Ukraine Google group,
see the discussion thread
it in our project. In short we:
Write small, deliverable, user stories ( 3-5 days )
Store them in Jira and on sticky notes
Include in each story a brief summary that highlights what it does,
why its valuable, and several tests
Evolve them from simple reminders, to placeholders for our
understanding, and finally an agreement on when we are "done".
This gives us some advantages:
(1) We are able to be more flexible since the details can be fleshed
out when the time is right
(2) We are able to collaborate and focus on verbal communication
instead of passing on written documents
I'll elaborate a bit on of each of these points.
Writing small, deliverable stories
Finding the "right" size for your stories is somewhat tricky. Since
people have very differnet ways of specifing "size" you are likely to
have to experiment and go with what fits your team. For us, it seems
that we have had most success with stories that a single developer
would use 3-5 days on.
Storing in Jira and on sticky notes
The simplest storage method is just to write things on a sticky note
and place it on your wall. It's quick, easy, and visible. Using some
software to store them can also be quite useful. In an offshore
situation that kind of becomes necessary.
Even if you use some software place to store your stories, I have
found that it's good to keep writing those sticky notes and getting
them up on the wall. This way the stories are always visible to
everybody, and there is also just a "feel good" factor in "physically"
taking them down when you are done.
Include in each story a brief summary that highlights what it does,
why its valuable, and several tests
One of the more tricky things is finding out how much to put into a
story. Again, this depends on how your team feels about it.
Before we started using stories we have some small "specifications".
These where typically a few pages with some text and screenshots.
Switching to user stories can be a slight shock to the system. The
most common question I got was, "Where are the details?".
Well, we do actually have a lot of "details" in our stories. These are
represented by the tests and an a GUI prototype. User stories are not
about masking out details. In order to deliver the story you need to
flesh out these details ( as it becomes necessary ), and in most cases
write them down as tests. In my world, the difference between user
stories, and some kind of "specification" is not really that big. It's
how you get there that counts. It's the collaborative, lightweight
"process" of going from an idea to an understanding of when a story is
"done".
In my experience, one of the biggest challenges is to make sure we
actually do the things necessary to make stories work. If you don't
discuss them properly, sincerly write down the tests, and collaborate
during them whole process, then your stories become more of a problem
than a solution.
Evolve them from simple reminders, to placeholders for our
understanding, and finally an understanding of when we are "done"
The reason why stories work is that they are flexible and demand that
you collaborate. A story starts out just as a simple reminder of a
discussion with the client. It evolves as you discuss it with other
people in the team, and you flesh out some details. In the end it
guides you towards aswering that simple question, "when are we
done?".
Ragnar Birgisson, Mar 07, for Agile-Ukraine Google group,
see the discussion thread
2007/05/24
War room или настенная живопись
Большая комната.
Неисчерпаемый запас sticky notes для каждой новой истории или бага.
Лист A2 прикрепленный скотчем на стену. Поделен на несколько секторов - каждый сектор определяет состояние готовности историй или багов, прикрепленных на него.
Во время утреннего митинга (или в любое другое время) стики переклеиваются в соответствии с обновленным состоянием, двигаясь от сектора "not started" до "accepted".
На стене практически у всех на виду постер с sprint burndown - обновляется маркером в соответствии с обновленными оценками по историям, которые ведутся в Jira.
На торце стены - "коллекция" закрытых историй и багов из предыдущих спринтов и релизов.
По среди комнаты два сдвинутых стола, ноутбук с внешним монитором, веб камерой, колонками и микрофоном - все что нужно для проведения утренних митингов с участием удаленных заказчиков.
Недалеко маркерная доска, поставленная на стул на колесах. На ней можно писать, не вставая из-за столов для совещаний.
Поотдать - flip chart с отрывающимися и переворачивающимися листками A2.
Куча маркеров.
Алексей Кривицкий для Agile Ukraine, May 07
Неисчерпаемый запас sticky notes для каждой новой истории или бага.
Лист A2 прикрепленный скотчем на стену. Поделен на несколько секторов - каждый сектор определяет состояние готовности историй или багов, прикрепленных на него.
Во время утреннего митинга (или в любое другое время) стики переклеиваются в соответствии с обновленным состоянием, двигаясь от сектора "not started" до "accepted".
На стене практически у всех на виду постер с sprint burndown - обновляется маркером в соответствии с обновленными оценками по историям, которые ведутся в Jira.
На торце стены - "коллекция" закрытых историй и багов из предыдущих спринтов и релизов.
По среди комнаты два сдвинутых стола, ноутбук с внешним монитором, веб камерой, колонками и микрофоном - все что нужно для проведения утренних митингов с участием удаленных заказчиков.
Недалеко маркерная доска, поставленная на стул на колесах. На ней можно писать, не вставая из-за столов для совещаний.
Поотдать - flip chart с отрывающимися и переворачивающимися листками A2.
Куча маркеров.
Алексей Кривицкий для Agile Ukraine, May 07
2007/05/23
AgileUkraine: новости и обновления
9 октября
The 3rd Agile Gathering.
Регистрация открыта
23-24 октября
Сертификации ScrumMaster снова в Киеве. .
Читайте и регистрируйтесь на scrum.com.ua.
6 сентября
Мы запустили проект Selected Agile Links.
Будьте в курсе последних обновлений и событий Agile мира.
Статьи, отчеты, презентации
Статьи, написанные членами группы Agile Ukraine:
На русском
Мы с радостью опубликуем ваши статьи. Пишите нам.
На русском
- FAQ по Agile
- Популярность Scrum
- Серия "Об Agile по-русски: Велик и могуч... термин «agile»"
- Серия "Об Agile по-русски: User Stories, часть 1"
- "War room или настенная живопись". Комната одной agile команды. Читать.
Мы с радостью опубликуем ваши статьи. Пишите нам.
События
Скоро
Подпишитесь на наш календарь для полученя обновлений
23-24 октября
Сертификации ScrumMaster снова в Киеве. .
Читайте и регистрируйтесь на scrum.com.ua.
9 октября
Планируется Третий Agile Gathering
Открылся Call for Papers. Высылайте, пожалуйста, предложения
Архив
21-22 июня 2007 ScrumMaster Certification классы в Киеве.
Читайте отчет.
19 июня 2007 Открытая Agile встреча
Детали.
31 марта 2007
Состоялась первая открытая встреча группы Agile Ukraine. Отчет и материалы здесь.
29 марта 2007
Компания Сиклум. Круглый стол, посвященный Scrum. Материалы фотосессии здесь.
Подпишитесь на наш календарь для полученя обновлений
23-24 октября
Сертификации ScrumMaster снова в Киеве. .
Читайте и регистрируйтесь на scrum.com.ua.
9 октября
Планируется Третий Agile Gathering
Открылся Call for Papers. Высылайте, пожалуйста, предложения
Архив
21-22 июня 2007 ScrumMaster Certification классы в Киеве.
Читайте отчет.
19 июня 2007 Открытая Agile встреча
Детали.
31 марта 2007
Состоялась первая открытая встреча группы Agile Ukraine. Отчет и материалы здесь.
29 марта 2007
Компания Сиклум. Круглый стол, посвященный Scrum. Материалы фотосессии здесь.
2007/05/22
Agile Ukraine news rus
First on our site?
know more about Agile Ukraine
ScrumMaster Certification class in Kiev
registration is being closed
visit the CSM section for more info
New site area: recommended books
find out recommended agile reading, share your favourites
visit the book section
Recent hot discussions, share your vision:
innovation games
sprint demos in distributed env
dysfunctions of team
Have a question? Proposal?
Contact us
know more about Agile Ukraine
ScrumMaster Certification class in Kiev
registration is being closed
visit the CSM section for more info
New site area: recommended books
find out recommended agile reading, share your favourites
visit the book section
Recent hot discussions, share your vision:
innovation games
sprint demos in distributed env
dysfunctions of team
Have a question? Proposal?
Contact us
Scrum Books
We recommend:
New book of 2007 by Ken Schwaber on Scrum at the Enterprise level
Previous Ken's books. Covers basics and practical aspects of Scrum:
back to book listing
Amazon recommends:
back to book listing
New book of 2007 by Ken Schwaber on Scrum at the Enterprise level
Previous Ken's books. Covers basics and practical aspects of Scrum:
back to book listing
Amazon recommends:
back to book listing
ScrumMaster Certifications in Ukraine
CSM classes
We conduct Certified ScrumMaster (CSM) classes inviting American and European Certified Scrum Trainers.
The last class was conducted 21-22 June 2007. Find the report.
The next is scheduled for October 2007.
Learn more about this and other certifications on ScrumAlliance official website.
Register for the next class?
Visit scrum.com.ua for class description, dates and pricing.
Other trainings: Scrum adoption, agile coaching
Apart of the official trainings from ScrumAlliance, we conduct coaching on Scrum and other agile topics with local trainers. Based on your need we build a program and assist you adopting agility in your current projects.
More info can be found our partner site scrum.com.ua.
Apply for other agile training programs?
Email us if interested and we discuss programs and rates.
We conduct Certified ScrumMaster (CSM) classes inviting American and European Certified Scrum Trainers.
The last class was conducted 21-22 June 2007. Find the report.
The next is scheduled for October 2007.
Learn more about this and other certifications on ScrumAlliance official website.
Register for the next class?
Visit scrum.com.ua for class description, dates and pricing.
Other trainings: Scrum adoption, agile coaching
Apart of the official trainings from ScrumAlliance, we conduct coaching on Scrum and other agile topics with local trainers. Based on your need we build a program and assist you adopting agility in your current projects.
More info can be found our partner site scrum.com.ua.
Apply for other agile training programs?
Email us if interested and we discuss programs and rates.
Subscribe to:
Posts (Atom)