Project

General

Profile

Edit History

V30 - Sprint #5 » History » Version 4

Johannes Bornhold, 21.01.2015 15:52

1 1 Johannes Bornhold 
h1. In preparation
2 





    3
    
    
    
* Bugfixing of high priority issues





    4
    
    
    
** High priority issues from regression run





    5
    
    
    
** High priority issues from customer feedback





    6
    
    
    
* Technical reviews of further overhauled sections in our tech docs





    7
    
    
    
* Keep on fixing styling issues and polishing the frontend





    8
    
    
    
** Styling topic "Forms"





    9
    
    
    
   Note: Won't fit into sprint 4 probably





    10
    
    
    
** Changeset





    11
    
    
    
** Comments





    12
    4
    Johannes Bornhold
    
* Parallel test runs in Jenkins





    13
    
    
    
  Avoids overhead and frees time lost due to stuck builds. First steps for further improvements to free even more time.





    14
    1
    Johannes Bornhold
    





    15
    
    
    





    16
    
    
    
h2. Statistics





    17
    
    
    





    18
    
    
    
We'll take the last three sprints to get a good indication of how many things we should put into this Sprint.





    19
    
    
    





    20
    
    
    





    21
    
    
    
h2. Issue handling





    22
    
    
    





    23
    
    
    
We classify new issues according to the question of how much it would prevent our users from using our product. Everything which would be a serious impediment from that perspective will be in priority "High" and will be sneaked in into our running Sprint. This is an attempt to find a good trade off between staying focused and keeping productivity high and reacting to severe issues on a timely manner.





    24
    
    
    





    25
    
    
    
Please notify Johannes in case you think that you found an issue which would qualify as priority "High".





    26
    
    
    





    27
    
    
    





    28
    
    
    
h2. Review changes





    29
    
    
    





    30
    
    
    
* We are involving Martina and Greg more into our workflow, starting with our daily standup meeting and planning. This way they know what we are up to and have a chance to prepare their own schedule better.





    31
    
    
    
* We (mainly Johannes) is making the check_screens script available so that this can be used by every team member to quickly verify if frontend changes have unintended collateral damage in other places. This is expected to pay off within a few days already, since it avoids extra loops when checking PRs.





    32
    
    
    
* We (mainly Greg) kick off test automation. This is a prevention of letting Greg become more and more a bottleneck.





    33
    
    
    





    34
    
    
    





    35
    
    
    
h2. Links





    36
    
    
    





    37
    2
    Johannes Bornhold
    
"Issues overview":https://bugs.rhodecode.com/projects/rhodecode-3-0/issues?utf8=%E2%9C%93&set_filter=1&f[]=fixed_version_id&op[fixed_version_id]=%3D&v[fixed_version_id][]=31&f[]=&c[]=tracker&c[]=status&c[]=priority&c[]=subject&c[]=assigned_to&c[]=updated_on&group_by=priority