Month: April 2013
Agile is a project management method commonly used in software development. Scrum is a framework within the Agile project management methodology. The Agile with Scrum approach to project management is often seen in software development, but could be an interesting way to go about developing eLearning. In another post, I will dive into Agile with Scrum project management for eLearning projects.
In the video below, Hamid Shojaee covers Agile and Scrum in under 10 minutes. Shojaee has been involved with Axosoft, a company that has developed the software to aid in project management of software development. The software is OnTime Scrum, “OnTime Scrum is feature-packed, blazingly fast, easy to use, affordable, and built on HTML5 technology. Manage your dev team’s backlog, sprints and bug tracking—and you can manage unlimited projects. You’ll love the management dashboard, planning board, and burndown charts.” (http://www.ontimenow.com/scrum)
Beneath the video I have outlined some of the terms from the video.
Product Owner – Makes sure that specific features make it into the product backlog as well as other duties.
Scrum Master – Makes sure things with the project are moving along, sets up meetings, they are sort of like a project manager.
Team – Developer, Graphic Designer, Instructional Designer,(in eLearning cases) QA etc.
Agile Methodology with Scrum – Terminology
User Stories – Features that the user wants in their product.
Product Backlog – A compilation of user stories or a wish list of features that the user thinks would make the product great.
Estimates – How long it will take to build out specific components of the product; for example, you can estimate work in hours and round up specific component. Some components will need days to months even.
Release Backlog – The stories picked from the product backlog to be implemented. Each of the components will have an estimate or time to be completed.
Sprints – Short duration milestones that allow the team to tackle chunks of the project. They can be every few days to 30+ days depending on the complexity of the product. At the end of each sprint, you should have a testable version of the product.
Sprint Backlog – A compilation of components from the release backlog. You can break up components and place them in sprints.
Burndown Chart – A day by day measure of work remaining in a sprint.
Daily Scrum – Fast paced standup meetings where the entire team gets together to list the work they completed since the last meeting and obstacles they have come across.
Sprint Retrospective Meeting – After each sprint the team gets together to go over what went right during that sprint and what can be improved upon.