scrum

I am working alone at the beginning of a sizable open source project and would like to leverage some of the core ideas/methods from Scrum to help manage my time and remain focused on development and deploying early, demonstrable functionality. I would like to hear from others who have used Scrum alone and what you have found particularly useful to these ends. Thanks. You might take a look at Peter Bell's post on Solo Scrum including the comments. If you're after solo, focusing timeboxes, try the pomodoro technique - 25 mins doing stuff, 5 mins reflection. There's a great free app here: http:/

在软件开发中花了很多时间等待事情发生。这种形式的浪费很容易在大多数开发团队中被发现。新的Scrum团队发现自己在一个Sprint中等待很多事情，包括： 允许做某事 完成需要一个漫长的过程 从一个团队或个人中脱离 运行测试或者完成验证 访问所需要的资源 与团队之外的人员合作 比等待Scrum团队的效率低下更加糟糕的是客户和企业需要花费时间等待软件集成、打包和交付。这个问题随着开发组织的规模增长而增加。随着更多的开发人员或团队加入到一个项目中，他们的工作集成到单个产品的成本也随之而增加。 Scrum中最长的等待是Sprint迭代时间。作为所有Scrum活动的容器，对Sprint持续时间的唯一要求是一个月或更少。这就限制了等待软件的工作增量为不超过一个月的时间。大多数Scrum团队更频繁地交付可工作的软件增量。 一个公司有六个Scrum团队正在开发一个庞大而复杂的软件产品。每个Scrum团队专注于特定的功能，并通过主Product Backlog在协同工作。每个Sprint迭代周期是是三周，包括整合所有开发团队的工作。 在此之前，每一个Sprint迭代周期是两周，但是随着产品的功能不断增加，开发的复杂性越来越高了。随着新的Scrum团队的加入，他们需要更多的时间来工作，所以根据集成活动的需要Sprint迭代周期增加了。 三周现在被称作整合周。将新功能集成到主程序中是在此期间的主要活动

在看板方法中第一步需要将一个团队的实际工作流程可视化。这是实现精益的“看到全貌”原则和需要看到实际的工作流程，而不是用文档来描述一个理想的版本或者使用其他什么模型来描述工作过程。一个有用的可视化模型表达了什么将会实际发生。 一旦可视化的工作存在，工作过程就可以用它来追踪。一个典型的入口（stage-gated），或瀑布模型，开发过程可以被在过程中使用如下几个特征所展示。 Scrum团队已经使用多年的可视化工作流程来展示Sprint的工作。在Scrum开发团队中最常见的可视化工作流程形式是Scrum的“任务板”或简单的“Scrum Board”。这种可视化模型使用起来比上述的模型简单，并且看上去也符合下面的模型。 这种典型的工作流可视化的形式受到Scrum跨功能开发团队规则的强烈影响。关注跨职能开发团队是Scrum框架的一个定义特性。跨职能团队拥有在每一个Sprint迭代中交付完整的可工作的软件增量所需要的所有开发能力。团队成员同时进行多项软件开发活动。 跨职能团队可以一起做一些事情，因为他们一起实现一个功能。这是与计划驱动的模型有很大的差别的，其中专家专注于在一次做所有的活动。此外，跨职能团队的成员可能有专业特点，但所有团队成员为交付所需要的软件而在一起执行常规的工作活动，无论这些活动是否属于个人的专业领域。跨职能的软件开发团队倾向于表现突出的专家团队。

Closed . This question is opinion-based. It is not currently accepting answers. Learn more . Want to improve this question? Update the question so it can be answered with facts and citations by editing this post . How significant are the differences between Visual Studio Scrum 1.0 & MSF for Agile Software Development v5.0 process templates? Has anyone used one over the other? We are currently using external tools ( TRAC ) for implementing Scrum in our development process, since MS came up with additional process guidance in TFS2010, these 2 things confuse me to the core! Unsure, which one to

We have been using Scrum for around 9 months and it has largely been successful. However our burndown charts rarely look like the 'model' charts, instead resembling more of a terrifying rollercoaster ride with some vomit inducing climbs and drops. To try and combat this we are spending more time before the sprint prototyping and designing but we still seem to discover much more work during the sprint than initially thought. Note: By this I mean the work required to meet the backlog is more involved than first thought rather than we have identified new items for the backlog. Is this a common

As I understand things, the Scrum backlog is composed of a series of Stories that represent something for the end user and this is further decomposed into Features. If this is the case, where does all the behind the scenes features go that aren't really linked to a story but are still useful? For example, say I'm making an application that catalogs the contents of a hard drive. A story wouldn't require it but having an md5 hash on each file would be a nice feature for flagging duplicates. The classic template to write good stories is: "As a <role> , I want to <action> so that <business value>

My company has recently started using Scrum; we've done 2 sprints. We're still learning, but we've definitely exposed and fixed some problems in our development process already. So in general I think it has been good for us. In reading many of the internet musings about Scrum from evangelists, cynics and everyone in between, three common and somewhat contradictory themes have stood out to me: Scrum implementation fails because the processes of Scrum are not followed closely enough. Scrum implementation fails because the organization does not adapt Scrum to its own environment/culture/practices

Anyone out there using Fogbugz and Scrum together? We use Fogbugz extensively, and I'm looking for ideas from anyone who may be using it as part of Scrum. I found these two items, but they are archived and unvailable for further discussion. I'm specifically interested in ideas for mapping Scrum concepts into Fogbugz. Some things are fairly obvious. Releases and sprints map well to each other. But other parts of Scrum don't really fit. http://support.fogcreek.com/default.asp?fogbugz.4.12143.4 http://support.fogcreek.com/default.asp?fogbugz.4.19971.3 I'm also thinking it might not be too hard to