Meeting #234
Updated by André Neto over 9 years ago
h1. Sprint planning
*Date of the meeting:* 29/09/2015
*Sprint objective:* Sixth release of MARTe aimed at finishing the introspection base infrastructure and implementing streams support
*Backlog items:* #169, #188, #235, #236, #237, #238, #239, #240
h1. Sprint review
The following issues and concerns were discussed by the team during the sprint:
* Non-tested functions of #240 to be reported in the Q&A audit report;
* cl does not have an option to set the version of C++. It was decided to implement it for gcc (see #236);
* Check for (and clean) test code compilation warnings;
* Investigate the possibility of having a Windows based jenkins instance. report.
h1. Sprint retrospective
* Things that the team should start doing
* Always start each commit line with the code of the related user-story (preceded by #);
* Minimise the number of WIPs and start to use stash;
* Things that the team should stop doing
* Implement many features under the same branch/user-story. In case of major work, break the user-story in smaller stories when possible.
* Things that the team should continue doing
h1. Technical debt
Non-completed user-stories: #188, #236
h1. Backlog review (restimation, reprioritization, weighting)
The sprint was not completely successful given that the introspection infrastructure is still not defined. More effort than expected was consumed in the re-factoring of the stream code base.
*Date of the meeting:* 29/09/2015
*Sprint objective:* Sixth release of MARTe aimed at finishing the introspection base infrastructure and implementing streams support
*Backlog items:* #169, #188, #235, #236, #237, #238, #239, #240
h1. Sprint review
The following issues and concerns were discussed by the team during the sprint:
* Non-tested functions of #240 to be reported in the Q&A audit report;
* cl does not have an option to set the version of C++. It was decided to implement it for gcc (see #236);
* Check for (and clean) test code compilation warnings;
* Investigate the possibility of having a Windows based jenkins instance. report.
h1. Sprint retrospective
* Things that the team should start doing
* Always start each commit line with the code of the related user-story (preceded by #);
* Minimise the number of WIPs and start to use stash;
* Things that the team should stop doing
* Implement many features under the same branch/user-story. In case of major work, break the user-story in smaller stories when possible.
* Things that the team should continue doing
h1. Technical debt
Non-completed user-stories: #188, #236
h1. Backlog review (restimation, reprioritization, weighting)
The sprint was not completely successful given that the introspection infrastructure is still not defined. More effort than expected was consumed in the re-factoring of the stream code base.