Skip to content

Category: XP

  • warning: Creating default object from empty value in /home/artemmarchenko/agilesoftwaredevelopment.com/modules/taxonomy/taxonomy.pages.inc on line 33.
  • warning: Invalid argument supplied for foreach() in /home/artemmarchenko/agilesoftwaredevelopment.com/modules/cck/content.module on line 1270.
  • warning: Invalid argument supplied for foreach() in /home/artemmarchenko/agilesoftwaredevelopment.com/modules/cck/content.module on line 1270.
  • warning: Invalid argument supplied for foreach() in /home/artemmarchenko/agilesoftwaredevelopment.com/modules/cck/content.module on line 1270.
  • warning: Invalid argument supplied for foreach() in /home/artemmarchenko/agilesoftwaredevelopment.com/modules/cck/content.module on line 1270.
  • warning: Invalid argument supplied for foreach() in /home/artemmarchenko/agilesoftwaredevelopment.com/modules/cck/content.module on line 1270.
  • warning: Invalid argument supplied for foreach() in /home/artemmarchenko/agilesoftwaredevelopment.com/modules/cck/content.module on line 1270.
  • strict warning: Non-static method view::load() should not be called statically in /home/artemmarchenko/agilesoftwaredevelopment.com/modules/views/views.module 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/agilesoftwaredevelopment.com/modules/views/plugins/views_plugin_display.inc 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/agilesoftwaredevelopment.com/modules/views/plugins/views_plugin_display_page.inc 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/agilesoftwaredevelopment.com/modules/views/plugins/views_plugin_display_block.inc 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/agilesoftwaredevelopment.com/modules/views/handlers/views_handler_field.inc 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/agilesoftwaredevelopment.com/modules/views/handlers/views_handler_sort.inc 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/agilesoftwaredevelopment.com/modules/views/handlers/views_handler_filter.inc 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/agilesoftwaredevelopment.com/modules/views/handlers/views_handler_filter.inc 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/agilesoftwaredevelopment.com/modules/views/handlers/views_handler_filter.inc 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/agilesoftwaredevelopment.com/modules/views/plugins/views_plugin_row.inc 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/agilesoftwaredevelopment.com/modules/views/plugins/views_plugin_row.inc on line 61.

Unpublished
n/a

Unpublished
n/a

Unpublished
n/a

Scrum and XP from the Trenches: Russian Edition

December 6, 2008 by Artem Marchenko

English summary below.

Scrum и XP: заметки с передовой" – это книга подробно рассказывающая о том, как одна конкретная компания использует Scrum и XP в своей работе. Хенрик Книберг, шведский консультант по Agile и Java, делится опытом применения Agile в своей компании, описывает подход к планированию, тестированию, координации нескольких команд в рамках одного проекта и многое другое.

В течение последних четырёх месяцев группа украинских энтузиастов организованная Алексеем Солнцевым переводила и перевела книгу на русский язык. Ваша покорный слуга принимал минимальное участвие в редактуре, однако тоже был удостоен упоминания в предисловии к русской версии. Скачать книгу можно здесь (ссылка на pdf).

Unpublished
n/a

Unpublished
n/a

Unpublished
n/a

XP Practice: Pair programming

April 18, 2008 by Artem Marchenko

Pair programming is one of the most known Extreme Programming practices. In essence it means creating the code in pairs trying to get multiple perspectives on the code created. One of the participants, called driver, types the code and thinks about the low level details. Another one, called navigator, thinks about what the typed code is for. The participants periodically switch roles. The definition of "low level" depends on the skills of the concrete pair and their experience in the subject area. For example, when using test-driven development the driver might be focused on the writing the production code, while the navigator could be thinking about how the next unit test should look like in order to change the system architecture in the desired direction.

XP Practice: Incremental Design

March 28, 2008 by Artem Marchenko

In traditional software development the design phase happens in the beginning of the project, takes quite a long no-coding or little-coding time. At the end of the phase, the design is considered being more-or less frozen. It might sound logical to plan ahead in a detail, however, in the case of software only the final source code is the real design - any diagrams or descriptions can at best be the higher level design abstractions. Therefore attempts to fix the design well in advance often lead to the wrong assumption and sub-optimal solutions.

XP Practice: Test-First Programming

February 18, 2008 by Artem Marchenko

Test-First Programming (TFP) and its sometimes more known related practice Test-Driven Development(TDD)  are not very usual for the traditional software development cycle. Test-driven development simply means creating tests before writing the code they are supposed to test. A canonical test-driven cycle is as follows:

  1. Write a test for the functionality you are going to implement
  2. Write as little code as possible to make the test compile. Make sure that at this step the test fails
  3. Write minimal or almost minimal code needed to make the test pass
  4. Once the test passes, refactor the code to make it better, prettier or simpler. The test and other existing tests will guard against accidental functionality breaks during the refactoring process

Best of AgileSoftwareDevelopment.com