Skip to content

Category: Scrum

  • warning: Creating default object from empty value in /home/artemmarchenko/ on line 33.
  • strict warning: Non-static method view::load() should not be called statically in /home/artemmarchenko/ on line 823.
  • strict warning: Declaration of views_plugin_display::options_validate() should be compatible with views_plugin::options_validate(&$form, &$form_state) in /home/artemmarchenko/ on line 1684.
  • strict warning: Declaration of views_plugin_display_page::options_submit() should be compatible with views_plugin_display::options_submit(&$form, &$form_state) in /home/artemmarchenko/ on line 457.
  • strict warning: Declaration of views_plugin_display_block::options_submit() should be compatible with views_plugin_display::options_submit(&$form, &$form_state) in /home/artemmarchenko/ on line 184.
  • strict warning: Declaration of views_handler_field_broken::ui_name() should be compatible with views_handler::ui_name($short = false) in /home/artemmarchenko/ on line 243.
  • strict warning: Declaration of views_handler_sort_broken::ui_name() should be compatible with views_handler::ui_name($short = false) in /home/artemmarchenko/ on line 82.
  • strict warning: Declaration of views_handler_filter::options_validate() should be compatible with views_handler::options_validate($form, &$form_state) in /home/artemmarchenko/ on line 584.
  • strict warning: Declaration of views_handler_filter::options_submit() should be compatible with views_handler::options_submit($form, &$form_state) in /home/artemmarchenko/ on line 584.
  • strict warning: Declaration of views_handler_filter_broken::ui_name() should be compatible with views_handler::ui_name($short = false) in /home/artemmarchenko/ on line 608.
  • strict warning: Declaration of views_plugin_row::options_validate() should be compatible with views_plugin::options_validate(&$form, &$form_state) in /home/artemmarchenko/ on line 61.
  • strict warning: Declaration of views_plugin_row::options_submit() should be compatible with views_plugin::options_submit(&$form, &$form_state) in /home/artemmarchenko/ on line 61.

Scrum process overview: schedule

May 13, 2007 by Artem

Scrum is the adaptive and flexible software development methodology. The possibility to adjust it according to the team preferences and organizational culture make Scrum implementations look differently across the organization. Some teams like packing the estimation session into a separate day, some like doing a little bit of estimation during every sprint planning; some teams have 5 minutes long sprint reviews, some have to make their reviews day long in order to let all the stakeholders express their opinions.

Earth travel

March 13, 2007 by Artem Marchenko

Some "products" from the Scrum Master course by Bas Vodde.

Today we were building a poster for a Martian travel agency. Since the course is held in Helsinki, no surprise we decided to offer some tours over Finland.

That's what out first 8 minute sprint day ended with. Not really shippable, but if we had to release it next minute, we could probably deliver it.

Agile Software Development one pager

March 5, 2007 by Artem

Agile software development is a set of core values. Iterative, incremental software development methods (ASDM) are based on these values. If I had to boil the overview down to the three most important items, these would be the following:

1. Iterative planning and releasing
ASDM recognize that it is rarely if ever possible to accurately plan software in advance. Customer priorities change, competitors force to release something early and even the best requirements obtained by pure thinking and analysis cannot be as good as the ones refined after seeing a running program.

Q & A sprints

January 31, 2007 by Artem

Some teams using Scrum and XP tend to have special Q&A iterations every several iterations and/or before the release. While it might be ok, during the transition to the agile processes, as a rule of thumb having Q&A sprints is a good indication of the problems with the definition of "done". The main point of iterative development is to have a "potentially shippable" product at the end of iteration. Planning for Q&A sprints essentially means that at the end of the iteration, team does not plan to have a potentially shippable product.

Scrum backlog templates and examples

November 6, 2006 by Artem Marchenko

Bas Vodde collected and published examples and templates of the Scrum product and Sprint backlogs. Most of them are in MS Excel format. Some (XLS) include a lot of comments, some (XLS) are very colourful. Check them out, Excel can really cover most of the needs of the archived backlog tracking.

Cached templates
Here are the cached copies of templates that I reviewed on this website.

See Also

Meet you at XP2006!

May 18, 2006 by Artem Marchenko

The 7th International conference on eXtreme Programming and Agile Processes in Software Engineering is going to take place on June 17-22, 2006, Oulu, Finland. According to the program, despite its name the conference is going to be focused more on the Agile Processes, than exactly on XP.

Among the speakers there are Kent Beck, the father of eXtreme Programming; Mike Cohn, the founder of Mountain Goat Software - strong Scrum supporter; Michael Feathers, author of Working Effectively with Legacy Code and a lot of other Agile Alliance founding members and board members.

Backing up the unreliable people

March 25, 2006 by Artem

Scrum Master role in the Scrum development method in the first place "was designed to change the power relationship and interaction dynamics from the traditional Team Lead or Project Manager". Scrum Master organizes the daily meetings, removes the impediments, reminds the Sprint goal, often maintains the Sprint backlog and does other secretary-like work.

Scrum takes over XP

March 22, 2006 by Artem

Extreme programming and Scrum are probably the most known agile software development methods over there. I myself find Scrum being more attractive and putting fewer requirements on the people communication skills. Have you ever wondered which method is more popular, which one is more talked about and what is the trend? I decided to ask the ubiquitous source of information - the web. I searched for "agile AND scrum" and "agile AND (xp OR extreme programming OR extremeprogramming"). "agile" is included to cut out the rugby's scrum. The search engine syntaxes are a bit different; you can see the concrete queries, by following the result links.

Multitasking in the workspace

October 30, 2005 by Artem

On Joel's Multitasking in the Workplace

Multitasking in the Workplace:
Joel Spolsky, a known writer on software development related topics is a long standing advocate of private offices for every developer, perfect working conditions and managers whose main role is to “move furniture out of the way, so people can concentrate on their work”. Lately he found the support in the published in the NY Times research report claiming that in the cubicle space people loose hell a lot of time on interruptions. I believe that there is a proven way to unite the advantages of the open-space communication and private office focus.

Best of