<body><script type="text/javascript"> function setAttributeOnload(object, attribute, val) { if(window.addEventListener) { window.addEventListener('load', function(){ object[attribute] = val; }, false); } else { window.attachEvent('onload', function(){ object[attribute] = val; }); } } </script> <div id="navbar-iframe-container"></div> <script type="text/javascript" src="https://apis.google.com/js/platform.js"></script> <script type="text/javascript"> gapi.load("gapi.iframes:gapi.iframes.style.bubble", function() { if (gapi.iframes && gapi.iframes.getContext) { gapi.iframes.getContext().openChild({ url: 'https://www.blogger.com/navbar/4684235500622716427?origin\x3dhttp://blog.caiwangqin.com', where: document.getElementById("navbar-iframe-container"), id: "navbar-iframe" }); } }); </script>

Caiwangqin's blog

Focus on Life, Cloud Service, Smart Hardware, Architecture, Technic and beyond…

Scrum 能够帮助团队提升效率吗？

2009年1月8日星期四

在2008年7月份的时候，我们团队启动了Scrum项目管理流程，建立了Redmine系统。在试行了5个sprint之后(每个sprint time box为2周)，10月初，我们悄无声息的停止了Scrum，原因主要有以下几种：
  1. Product backlog 不能预先确定，导致Sprint plan meeting时间长，效率低
  2. 团队加入一批新成员，不能适应Scrum工作方式
  3. 公司高层对Scrum支持力度比较小，一些制定好的方案最后不了了之，如daily meeting
  4. 计划的变更过于频繁（哪怕是已经在sprint blacklog中确定的）
  5. 对团队生成力的估计不准确（后期已经越来越准确了），在Sprint中安排了过多的任务，导致任务不能按时完成
这里有我们最后一个sprint的backlog，以下列出我们的retrospect:
  1. Sprint 1 retrospect

    GOOD
    daily scrums
    skype group
    tell team when you have finished a task
    google group
    communicate
    daily demos

    BAD
    not talking to other departments

    IMPROVE
    desiners work in the beginning of sprint 7
    testing environment 7
    everyone do demo, everyone give feedback 3
    sprint backlogs 3
    plan meetings 3
    task estimates 3
    points on task cards 2
    design before coding 2
    work more together 1
    1 point per task card 1
    sprint burndown chart 1
    person estimates 1
    unplanned items 0
    css development 0

  2. Sprint 2 retrospect
    GOOD
    daily scrums in 15 mins
    google group

    BAD
    no feature design
    no final style design
    no push to production

    IMPROVE
    feature design logic
    feature process and priority
    risk assessment design development
    testing team

  3. Sprint 3 retrospect

    GOOD
    good task estimate
    we had ui design team(got final version from alex)

    BAD
    planning meeting too long
    no drink in retrospect meeting, use late fee
    no training for research result
    refactor for project1

    IMPROVE
    prepare for demo meeting
    prepare for planning meeting
    report bug in english
    work on bugs
    one lab day every month
    two monitor for work


从上面大致可以了解一些我们团队执行Scrum的情况。由于团队成员扩充和变更，我们希望更好的制订工作计划，提升团队工作效率。可能再次启动Scrum项目管理方式，Scrum 能够帮助团队提升效率吗？

标签： ,

posted by Caiwangqin, 17:50

1 Comments:

时间 2009年1月17日 13:17 , Blogger Caiwangqin 说...

延伸阅读：
产品负责人成功之道: http://www.infoq.com/cn/articles/agile-product-owner
杀死团队的七种武器: http://bearwhisper.blogbus.com/logs/29095777.html

 

发表评论

订阅 博文评论 [Atom]

<< 主页