Suggestions in order to keep your Backlog clear, updated and attractive for the EC: * Create a general Node.Maintenance WorkItem for your daily/routine maintenance activities. * Create a general Users.Support WorkItem for your daily/routine users support activities. (Close the WorkItems above at the end of each sprint and Clone them at the start of the next) * Create as many WorkItems as all the activities your are planning to do on your node. * Keep updated the Status of each WorkItem (“in progress", “open”… “closed”). * Set the Status on “impeded” if you cannot advance on a planned WorkItem for external reason (e.g. you are waiting for the new monitoring documentation) and leave a comment. * Set the Priority of a WorkItem on “minor” if you have planned some not-mandatory activities (they could affect statistics whether not closed within the planned sprint). And then, last but not least… * Create (and close) as many WorkItems as all the main activities you have performed during 2016! Such as Migration to Kilo, VMs migrations, Node Maintenance, Node federation and so on… (Manuel will help us to set the correct Sprint number according to the date of the activity). I know that it could be very boring (and quite hard in some cases) but it could be very useful to underline progresses and efforts spent on your node. Especially for the EC which has access to those data. Alfonso Alfonso Pietropaolo Research and Development Laboratory Engineering Ingegneria Informatica S.p.A. <https://imail.eng.it/ecp/Customize/www.eng.it> Via Riccardo Morandi, 32 00148 Roma - Italy Tel. 0683074834 Skype: alfopietro -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-lab-federation-nodes/attachments/20160705/bdbd2228/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy