Difference between revisions of "AppSuite:Sprint definition"

(7 days)
(3 days)
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
Since we are a bit different at Open-Xchange, we have not one but two "definitions of done": Our sprints are two weeks or ten work days long. The first seven are about geting the feature implemented, the last three about polishing it. Each part has its own definition of done.
+
<div class="title">Sprint definition</div>
 +
Sprints are two weeks (10 work days) long. The first seven days focus on feature development, the last three focus on quality. The first part needs a "definition of done".
  
== 7 days ==
+
==Definition of done==
* Documentation in OXpedia
+
* Tasks of user story are all done
* Tested once on a browser set to emulate a 480px device
+
* Tested once on a browser with very small window size to check responsiveness
* Tested with either an iOS or an Android device
+
* Tested once with either an iOS or an Android device
* Tasks in Pivotal Tracker are all checked
+
* Documentation in OXpedia (if necessary/required)
* Code has been merged into origin/develop
+
* Code has been merged into origin/develop (i
* i18n and l10n are taken care of
+
* i18n and l10n issues are checked (e.g. #debug-i18n=1)
** <code>#debug-i18n=1</code> does not complain
+
* Code is commented where necessary (what does it, what goes in, what comes out)
* Code is commented where necessary
+
 
** JSDoc-style comments at least on module APIs
+
If done, a user story is marked as "Delivered". Requestor then accepts or rejects the user story.
** Contents of <code>Baton</code> and option objects are described
 
  
 
== 3 days ==
 
== 3 days ==
 
* Tested with all permutations of iOS/Android and smartphone/tablet
 
* Tested with all permutations of iOS/Android and smartphone/tablet
 
* Tested with Firefox, Chrome, Safari and IE9
 
* Tested with Firefox, Chrome, Safari and IE9
* At least one smoke test is written
+
* At least one smoke test is written, L3 bugs get a test, too
** If it is a fix for an L3 bug, one test is written
 
 
* Checked for responsiveness criteria (e.g. busy(), notifications)
 
* Checked for responsiveness criteria (e.g. busy(), notifications)
* slow & fail parameters have been experimented with, ox.load() is used instead of require
+
* Slow & fail parameters have been experimented with, ox.load() is used instead of require
 
* Performance is tested
 
* Performance is tested
 
* Theming works (use the pink theme)
 
* Theming works (use the pink theme)
 
* All software change requests have been started (in case of API changes, new settings...)
 
* All software change requests have been started (in case of API changes, new settings...)
* A11Y checks done.
+
* Accessibility checks done
 +
 
  
 
[[Category:AppSuite]]
 
[[Category:AppSuite]]
 
[[Category:Development process]]
 
[[Category:Development process]]
 
[[Category:Ui]]
 
[[Category:Ui]]

Latest revision as of 19:15, 6 May 2013

Sprint definition

Sprints are two weeks (10 work days) long. The first seven days focus on feature development, the last three focus on quality. The first part needs a "definition of done".

Definition of done

  • Tasks of user story are all done
  • Tested once on a browser with very small window size to check responsiveness
  • Tested once with either an iOS or an Android device
  • Documentation in OXpedia (if necessary/required)
  • Code has been merged into origin/develop (i
  • i18n and l10n issues are checked (e.g. #debug-i18n=1)
  • Code is commented where necessary (what does it, what goes in, what comes out)

If done, a user story is marked as "Delivered". Requestor then accepts or rejects the user story.

3 days

  • Tested with all permutations of iOS/Android and smartphone/tablet
  • Tested with Firefox, Chrome, Safari and IE9
  • At least one smoke test is written, L3 bugs get a test, too
  • Checked for responsiveness criteria (e.g. busy(), notifications)
  • Slow & fail parameters have been experimented with, ox.load() is used instead of require
  • Performance is tested
  • Theming works (use the pink theme)
  • All software change requests have been started (in case of API changes, new settings...)
  • Accessibility checks done