Changes between Version 329 and Version 330 of ScrumBurndownPlugin
- Timestamp:
- Aug 25, 2015, 5:25:07 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ScrumBurndownPlugin
v329 v330 1 1 [[PageOutline(2-5,Contents,pullout)]] 2 2 3 = Scrum Burndown in Trac =3 = Scrum Burndown in Trac 4 4 5 == Description == 6 A plugin to enable burndown chart capabilities, a common part of Scrum and other agile development methodologies. 5 == Description 6 7 This is a plugin to enable burndown chart capabilities, a common part of Scrum and other agile development methodologies. 7 8 8 9 This plugin is integrated with the TimingAndEstimationPlugin. 9 10 10 == Using the plugin == 11 At the beginning of a sprint, after the tickets have been inputted and estimated in Trac an admin user should click the 'Start Milestone' plugin. This inputs a datetime integer into the milestone table to indicate when the milestone was started. The daily burndown_job.py script will only record hours_remaining entries for milestones that have started, but have not been completed. It should be fairly obvious, then, that an admin user should click the 'Milestone Complete' button at the end of the milestone to prevent the burndown_job from continuing to collect data. 11 At the beginning of a sprint, after the tickets have been input and estimated in Trac an admin user should click the 'Start Milestone' plugin. This inputs a datetime integer into the milestone table to indicate when the milestone was started. The daily burndown_job.py script will only record hours_remaining entries for milestones that have started, but have not been completed. It should be fairly obvious, then, that an admin user should click the 'Milestone Complete' button at the end of the milestone to prevent the burndown_job from continuing to collect data. 12 12 13 13 You can view different burndown charts, selectable by milestone and component by choosing from the dropdowns and clicking the 'Show Burndown Chart' button. 14 14 15 In order for this to work, it is imperative that developers keep the 'Estimated Hours' and 'Total Hours' fields accurate and up-to-date on the tickets they are working.The 'Total Hours' field itself should never be manually edited, but rather, it can be changed by inputting positive and negative values into the 'Hours to Add' field.15 For this to work, it is imperative that developers keep the 'Estimated Hours' and 'Total Hours' fields accurate and up-to-date on the tickets they are working. The 'Total Hours' field itself should never be manually edited, but rather, it can be changed by inputting positive and negative values into the 'Hours to Add' field. 16 16 17 17 [[Image(burndown.jpg,50%)]] 18 18 19 == Questions == 20 1. Is there an easy way to move the start date of a sprint into the past? (For example when some tickets of a milestone already have been closed when starting a sprint, immediately after installing this plugin.) [[BR]] 21 ''This can be done in the administration panel (only in Trac 0.11.x)'' 19 This plugin relies on the TimingAndEstimationPlugin. 22 20 23 2. Is there any way to automatically grant BURNDOWN_VIEW to any/all users? It's slightly annoying to have to explicitly set that permission on every user (which in our case is about 40 people). 24 ''Answering my own question, figured it out on my own. Any authenticated user pulls it's default permissions from the 'anonymous' group. This is all explained in the TRAC documentation: http://trac.edgewall.org/wiki/TracPermissions , if you add BURNDOWN_VIEW to the anonymous usergroup, everyone can view it. If you add it to the authenticated usergroup, any authenticated user will be able to view it.'' 21 See also: 22 * BurndownPlugin is a similar plugin using Fusion Charts Free edition. 23 * AgiloForScrumPlugin is a similar plugin. 24 * EstimationToolsPlugin is a similar plugin. It uses Google's Charts API, and doesn't depend on TimingAndEstimationPlugin. 25 25 26 == Bugs/Feature Requests == 26 == Bugs/Feature Requests 27 27 28 Existing bugs and feature requests for ScrumBurndownPlugin are 28 [query:?status=new&status=assigned&status=reopened&group=&component=ScrumBurndownPlugin&order=priority 29 [query:?status=new&status=assigned&status=reopened&group=&component=ScrumBurndownPlugin&order=priority here]. 29 30 30 31 If you have any issues, create a 31 32 [/newticket?component=ScrumBurndownPlugin new ticket]. 32 33 33 == Download == 34 [[TicketQuery(component=ScrumBurndownPlugin&group=type,format=progress)]] 35 36 == Source 37 34 38 You can check out the source [/svn/scrumburndownplugin using Subversion] or [source:scrumburndownplugin browse the source] with Trac. 35 39 36 == Related Plugins == 37 * This plugin relies on the TimingAndEstimationPlugin 38 * BurndownPlugin is a similar plugin using Fusion Charts Free edition 39 * AgiloForScrumPlugin is a similar plugin. 40 * EstimationToolsPlugin is a similar plugin. It uses Google's chart API, and doesn't depend on TimingAndEstimationPlugin 40 == Installation 41 41 42 == Recent Changes == 42 General instructions on installing Trac plugins can be found on the [TracPlugins#InstallingaTracplugin TracPlugins] page. 43 44 == Questions and Answers 45 46 1. Is there an easy way to move the start date of a sprint into the past? (For example when some tickets of a milestone already have been closed when starting a sprint, immediately after installing this plugin.) [[BR]] 47 48 ''This can be done in the administration panel, available in Trac 0.11 and higher.'' 49 50 2. Is there any way to automatically grant BURNDOWN_VIEW to any/all users? It's slightly annoying to have to explicitly set that permission on every user (which in our case is about 40 people). 51 52 ''Any authenticated user pulls its default permissions from the 'anonymous' group, see http://trac.edgewall.org/wiki/TracPermissions. If you add `BURNDOWN_VIEW` to the anonymous usergroup, everyone can view it. If you add it to the authenticated usergroup, any authenticated user will be able to view it.'' 53 54 == Recent Changes 43 55 44 56 [[ChangeLog(scrumburndownplugin, 3)]] 45 57 46 == Author/Contributors ==58 == Author/Contributors 47 59 48 60 '''Author:''' [wiki:sambloomquist] [[BR]] 49 '''Maintainer:''' ''none (needsadoption)''[[BR]]61 '''Maintainer:''' [[Maintainer]] [[BR]] 50 62 '''Contributors:''' [[BR]]
