On October 23rd, 2014, we updated our
By continuing to use LinkedIn’s SlideShare service, you agree to the revised terms, so please take a few minutes to review them.
Agenda• Where we are• SCRUM What is it ?• How did it start with us ?• How our teams are organized ?• How do we do this?• Where should we aim at?• Bonus: Kanban
Where we are• From 1 to 35 within 12 months• 3 Drupal teams 2 mobile teams 1 magento• Procedures and processes• B.DK, BT.DK, AOK.DK, sporten.dk• Main dev power
SCRUM. What is it? This is not a shortened SCRUM course but... i will tell you • What is is SCRUM about • How do we use it • Share our best practices and tweaks
SCRUM. What is it?• A methodology for software project development• Lets you focus on most important business values• Business sets the priorities. Self organized team decides on the best technical way.• Each sprint all parties interested can see real functioning product so to decide either to release it or continue improvements in the next sprint
SCRUM. What is it? • Define teams• Divide products by features • Define business value• Do a release plan • Constantly optimize your process
SCRUM. What is it?
How did it start ?• 2009 big company, dear colleagues• 2010 path of transformation and savings• 2010 Ukraine as the best combination for price, quality, sales
How did it start ?• Right thinking. Like - minded persons• Right procedures. Adjustments• Right people. Interview, July 2010 first sprint
How our teams are organized
How our teams are organized
How do we do this• Releases• Estimations• Planning• Retrospectives
How do we do this• Daily scrum, sharp schedule• Overtimes are illegal• One task not more than 2 days (16 hours)• Importance instead of priority (importance can be 500 instead of priority 1)• Pool (15% of sprint time) for urgent issues• If you are sick you are in the sprints as a task!• One task one team member 1:1• Pare programming and discussions, workshops• New features and areas are documented• Same rules for everybody
How do we do this with testing• Tester tries to reproduce issue before estimation session starts
How do we do this with retrospectives• Retrospective for distributed team
Where to aim• Trust. Thats nearly everything• Sense of Urgency• Good communications• Process understanding• Think out of the box what else can i do ?• One change a a time• Constant improvements
What next ?• What can i improve for the company i am working in?• What out of that will i do first?• When will i do it ?
Thank you for your attention! questions ? Dennis Popovdepo@berlingskemedia.dk firstname.lastname@example.org skype: celenia_dep
Read, try, feelPeoplewareManagement 3.0Agile Project Management with ScrumAgile Software Development with ScrumKanban и Scrum: getting best of both (Ru)SCRUM gamesmikogo, planning poker onlineversion oneKnibergs bloghttp://www.controlchaos.com/http://scrumalliance.org/Scrum Cheat sheet
Bonus: Kanban in 3 min.Scrum board but with - workflow visualized and • WIP limits • Buffers • Throughput speed