|
|
| Line 1: |
Line 1: |
| − | ===Application:===
| |
| | | | |
| − | ''- How to use the tool in a project, how to read it and how to use it as a manager.''
| |
| − |
| |
| − |
| |
| − | ''- How to make a Risk Burn Down Chart.''
| |
| − |
| |
| − |
| |
| − | ''- When does (and doesn't) it make sense to apply the Risk Burn Down Chart (in which context).''
| |
| − |
| |
| − | In projects where tasks and workload is known up-front in makes sense to implement the RBD chart. When the tasks and workload is unknown, it will be very challenging to make the chart.
| |
| − |
| |
| − |
| |
| − | ''- In what type of projects is it most effective to use?''
| |
| − |
| |
| − | In agile projects such as SCRUM projects, the tool is an important part of the management. However, it can be applied to all types of projects. <ref name="Hofmann2021" /> One of the reasons why it is heavily used in agile projects is because of the nature of these type of projects, where the tasks to be completed are often known in more detail up-front and the tasks can be broken down into iterations or work packages - where smaller functions can be build and tested with a user and then new functions can be added to the previous ones. In agile projects, two types of RBD charts are used: an iteration RBD chart and a project RBD chart. The charts a very similar to each other, where the iteration chart is focused on the individual iteration progress and the project chart is focused on the overall progress of all iterations and work to be done. <ref name=Collins2010 >[Collins, M. J. (2010). Burndown Charts. Pro Project Management With Sharepoint 2010, 143–171.] https://doi.org/10.1007/978-1-4302-2830-1_9 </ref> In new product innovation projects, the tasks to be completed are often a lot more intangible, meaning that the specific tasks to be completed is not known up-front. Most companies have a development process, like [[The Stage-Gate Model]] <ref>[Pagoni, E. (2017), The Stage-Gate Model] http://wiki.doing-projects.org/index.php/The_Stage-Gate_Model </ref>, they are following, nevertheless it might still be challenging to know up-front what resources are needed in the specific project. However, most project managers are required to make estimates of how much time the different stages take and usually also propose dates for the different gates to get allocated resources from upper management. So, the RBD chart can also be applied to more intangible projects as a way of continuously tracking the process.
| |
| − |
| |
| − |
| |
| − | ''- Tips and tricks about RBDC''
| |
| − |
| |
| − | 1. If your project contains decisive milestones or gates, they can also be added on the vertical axis of your RBD chart (on the axis with remaining work packages). This is especially useful if you are working with a more intangible project, where it is challenging to provide precise workloads for each stage/iteration. <ref name="Hofmann2021" />
| |
| − |
| |
| − | 2. It is only useful if it is updated on a continuous basis, since it needs to reflect the current status, and displayed clearly and is accessible to the whole project team. <ref name="Hofmann2021" />
| |
| − |
| |
| − |
| |
| − | ===Limitations:===
| |
| − |
| |
| − | ''- Strengths and weaknesses of the tool.''
| |
| − |
| |
| − | Weakness:
| |
| − |
| |
| − |
| |
| − | ''- How it relates to the standards of project management.''
| |
| − |
| |
| − |
| |
| − | ''- Other similar tool that can be used instead of or in addition to the RBD Chart''
| |
| − |
| |
| − |
| |
| − | ==References:==
| |
| − |
| |
| − | <references/>
| |
| − |
| |
| − |
| |
| − | ==Annotated bibliography:==
| |
| − |
| |
| − | ''Lai, S. T., Susanto, H., & Leu, F. Y. (2022). Project Management Mechanism Based on Burndown Chart to Reduce the Risk of Software Project Failure. Lecture Notes in Networks and Systems, 346, 197–205. https://doi.org/10.1007/978-3-030-90072-4_21'' - Article about the use of RBD Charts in software development and how it is effective at identifying problems in relation to risk.
| |
| − |
| |
| − | ''Chaudhuri, D. J., & Chaudhuri, A. (2011). AGILE burndown chart deviation - predictive analysis to improve iteration planning. Proceedings of the 2011 International Conference on Software Engineering Research and Practice (Serp 2011), 443–449.'' - Article about the usefulness of the RBD chart and how it can be used in AGILE environments.
| |
| − |
| |
| − | ''Collins, M. J. (2010). Burndown Charts. Pro Project Management With Sharepoint 2010, 143–171. https://doi.org/10.1007/978-1-4302-2830-1_9'' - Book chapter on the basics of RBD charts and how to make one.
| |
| − |
| |
| − | ''Woodward, C. J., Cain, A., Pace, S., Jones, A., & Kupper, J. F. (2013). Helping students track learning progress using burn down charts. Proceedings of 2013 Ieee International Conference on Teaching, Assessment and Learning for Engineering, Tale 2013, 104–109. https://doi.org/10.1109/TALE.2013.6654409'' - Article on how useful the RBD Chart is in a university setting in programming units.
| |
| − |
| |
| − | ''Miranda, E., & Bourque, P. (2010). Agile monitoring using the line of balance. Journal of Systems and Software, 83(7), 1205–1215. https://doi.org/10.1016/j.jss.2010.01.043'' - Article talks about the usefulness of RBD chart in SCRUM/Agile projects, but also questions the tool and talks about some of the limitations.
| |
| − |
| |
| − | ''Hofmann, M. (2021). Tools for the Optimisation of Workflows. A Holistic Approach To Process Optimisation, 61–120. https://doi.org/10.1007/978-3-658-34097-1_4'' - Book with some basics about RBD charts and some benefits/strengths about the tool.
| |
| − |
| |
| − | ''Sutton, S. M. (2018). Informed projection: Using what you know to make simple estimates of work better. Acm International Conference Proceeding Series, 76–85. https://doi.org/10.1145/3202710.3203147'' - Article might propose better alternative tools to the RBD chart tool.
| |
