Redmine @ Mippin

31
Redmine @ Mippin Intro & Conventions Maciej Matyjas Head of Development @matyjas

Transcript of Redmine @ Mippin

Page 1: Redmine @ Mippin

Redmine @ Mippin

Intro & Conventions

Maciej MatyjasHead of Development@matyjas

Page 2: Redmine @ Mippin

What It Is?

● support1● Redmine● Redmine Backlogs● git● cgit● gitolite

Page 3: Redmine @ Mippin

support1

Our Rackspace cloud server hosting new tools including

Redmine

Page 4: Redmine @ Mippin

Redmine

"Redmine is a flexible project management web application. Written using Ruby on Rails

framework, it is cross-platform and cross-database.

Redmine is open source and released under the terms of the GNU General Public License v2

(GPL)."*

* http://www.redmine.org

Page 5: Redmine @ Mippin

Redmine Backlogs

"A Redmine plugin for agile teams"*

* http://www.redminebacklogs.net/

Page 6: Redmine @ Mippin

git

"Git is a free & open source, distributed version control system

..."*

* http://git-scm.com/

Page 7: Redmine @ Mippin

cgit

"a web frontend for git repositories"*

* http://hjemli.net/git/cgit/

Page 8: Redmine @ Mippin

gitolite

"Gitolite allows you to setup git hosting on a central server ..."*

* https://github.com/sitaramc/gitolite

Page 9: Redmine @ Mippin

Relevant Redmine Features

● Self Registration● Projects and Sub-Projects● Roles● Trackers● SCM Integration● etc

Page 10: Redmine @ Mippin

Redmine: Self Registration

Get started by registering a user here

Page 11: Redmine @ Mippin

Redmine: Projects and Sub-Projects

Top Level Project Called 'Master'

● Backlog and Sprints Managed on this Level

● Encompasses all aspects of Mippin Business

Sub-projects● Mapped to SCM

Repositories● Super Easy to Move

Items Between Projects and Sub-projects

● Examples○ Analytics○ iOS App○ Symbian Builder ○ Buzz Widgets?

Page 12: Redmine @ Mippin

Redmine: Roles

Redmine Roles● Developer● Manager● Reporter

Scrum Roles● Team Member● Product Owner● ?● Scrum Master could use

any Redmine Role

Page 13: Redmine @ Mippin

Redmine: Trackers

Redmine Scrum Means

Bug Story Problem with software, not working as

expected or planned

Feature Story Improvements and new work in

user/marketing speak

Support Story Non-development work; run report, do release, manually

testTask Task Technical work in all

its gory detail

Page 14: Redmine @ Mippin

Redmine: SCM Integration

● Supports: git, Subversion, CVS and others● Commits automatically reflected● View current state of repository● Diff versions of files or dirs ● Killer feature => commit messages can resolve issues

○ "fixes #36 null pointer handled"○ "working on #45 to make sure all corners are rounded"

Page 15: Redmine @ Mippin

Redmine: etc

● Issue Creation via Email● Wiki● Calendar● Gantt● Release Management● News● Documents● Files● Forum

Page 16: Redmine @ Mippin

Redmine Backlogs Features

● Product Backlog● Stories● Sprints● Story Points● Tasks ● Task Board● Impediments ● Burn down Chart

Page 17: Redmine @ Mippin

Redmine Backlogs: Product Backlog

● Use the Master project for Product Backlog● Should be visible to everyone on the team● Owned by Product Owner● Priority can be changed via drag and drop ● Gives an idea of where we are going ● You can add a story!

Page 18: Redmine @ Mippin

Redmine Backlogs: Stories

● User or even Marketing oriented● Not detailed● Analogous to a subset of Issues in Redmine ● Types

○ Bug○ Feature○ Support

Page 19: Redmine @ Mippin

Redmine Backlogs: Sprints

● Set of Stories to be completed in 2 weeks● Prepared during Sprint Planning Meeting● Should be well understood once Sprint starts● Analogous to Versions in Redmine

Page 20: Redmine @ Mippin

Redmine Backlogs: Story Points

● Owned by Development Team● Abstract: do NOT represent days/hours/etc● Represent relative size of story● Fibonacci series: 1, 2, 3, 5, 8, 13, ...● Set for Stories during Sprint Planning Meeting● Helps to estimate how many Stories can fit into a Sprint

Page 21: Redmine @ Mippin

Redmine Backlogs: Tasks

● Child of a Story● Detailed work needed to complete a Story● Owned by Development Team● Has time estimate, in hours● First pass completed during Task Scope Meeting (right after

Sprint Planning)● Add Tasks whenever you need one ● Could be printed and stuck up on a board

Page 22: Redmine @ Mippin

Redmine Backlogs: Task Board

● Similar to what we had on the whiteboard● Stories are on left with 'swim lanes' projecting to right● Tasks live in 'swim lanes'● Dev Team can drag & drop Tasks into columns● Columns represent Task states

○ New○ In Progress○ Resolved○ Feedback○ Closed○ Rejected

● Different Roles could have different permissions

Page 23: Redmine @ Mippin

Redmine Backlogs: Impediments

● When Dev Team is blocked by something outside their control, they create an Impediment

● Top swim lane in Task Board● Become the responsibility of Scrum Master

Page 24: Redmine @ Mippin

Redmine Backlogs: Burn Down Chart

● Visual representation of Sprint progress● Y axis is work (story point or hours)● X axis is time● Perfect goes from nothing completed (on top

left) at beginning of Sprint to everything done (on bottom right) at the end of Sprint

● Pay attention to (hopefully) bottom bars which represent the amount of work per day that needs to be completed to finish everything by the end of the Sprint

Page 25: Redmine @ Mippin

Redmine Backlogs: Burn Down Chart

Page 26: Redmine @ Mippin

Redmine Backlogs: Burn Down Chart

Page 27: Redmine @ Mippin

Redmine Backlogs: Burn Down Chart

Page 28: Redmine @ Mippin

Redmine Backlogs: Burn Down Chart

Page 29: Redmine @ Mippin

Redmine Backlogs: Burn Down Chart

Page 30: Redmine @ Mippin

Redmine Backlogs: Burn Down Chart

Page 31: Redmine @ Mippin

Thanks!

Maciej MatyjasHead of Development

@matyjas