Scrum Methodology & Agile Scrum Methodologies Learning Scrum through Games While this is the session I ran in 2011 it has been replaced by: Learning Scrum Through Games – Goldilocks Iterations II. Last week at Agile Tour Toronto I had the privilege of working with my friend Paul Heidema to help introduce the basic concepts of Scrum in 60 minutes. This is a really interesting challenge, what’s the minimum amount you can teach people and still give them a taste of Scrum. We invited our teams to create Children’s Books of the Goldilocks story. Comments from participants: A number said it was surprising how well teams of complete strangers came together after two sprints.Several didn’t like the way I set them up for a mini “failure” by not playing the Product Owner role poorly and not communicating my needs. Attached below – are our materials: Feel free to use this simple simulation to help teach the very basic concepts of Scrum. About the Author Mark is an independent Certified Scrum Trainer since 2011 and Agile coach.
5分鐘 學 Scrum (簡介) 剛剛看到此篇: Scrum in a Nutshell or 5 minutes to learn scrum, 就想來做個簡單的整理好了. 上述那篇是英文版的, 看此篇中文版的也可以, 兩個都整理的蠻完整的, 現在這篇還有另外附圖(流程), 相互參考一下, 應該可以 5 分鐘看完吧.. XD 中文版: Agile Software-Development : Scrum 除了 Scrum 外, 其它的流程比較可見以前寫的文章 - 敏捷的軟體開發流程(CMMI) 以下內容大多轉載自 中文版: Agile Software-Development : Scrum 我只是轉載過來整理一下, 加幾句經驗之談而已, 詳細最好的還是看上述兩篇文章, 才能有更深入的了解. Scrum一詞源自英式橄欖球，在兩隊前鋒對峙下互相爭球，也可以解釋做「a usually brief and disorderly struggle or fight」。 Scrum 優勢: Scrum把專案開發進程化整為零，適合快速反應需求改變的專案，以及開發時間緊迫的專案。 Product BacklogSprint Backlog & Sprint Planning MeetingSprint (1~4 週) (視專案大小會有 n 個 1~4週), 一個 Sprint不建議超過一個月, 超過一個月最好想辦法再細分Brief Daily Meeting(Daily Scrum Meeting), Daily 主要要報告以下三件事: 昨天做了什麼事？ 相關網頁 Scrum 工具 This work, unless otherwise expressly stated, is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License. 對新奇的事物都很有興趣, 喜歡簡單的東西, 過簡單的生活.
How to Scale the Scrum Product Owner The product owner is the person in charge of the product. For products of modest complexity and small projects, it may be feasible to have one individual playing the product owner role. But how do we deal with product ownership on large Scrum projects that develop complex products? The Chief Product Owner A large agile project consists of many small teams. This puts us in a dilemma, as it conflicts with the Highlander Principle, which states that there should only be one product owner. There are two ways to apply the chief product owner role: working with one potentially large and complex product, or breaking up the product into multiple, independent sub products. Option 1: One Product If you develop one cohesive product with lots of functionality, you are likely to end up with a hierarchy of collaborating product owners with a chief product owner at the top, as the following image shows: Option 2: Product Suite Summary
What Is Scrum? According to the State of Agile Survey, approximately 60 percent of projects are Agile.1 After all, Agile frameworks help companies accelerate time to market, increase productivity, and respond to changes in priorities. Of all the Agile frameworks, Scrum is the most widely adopted. Professionals from around the world and in a variety of industries are using Scrum to position their teams for greater success. Join the global movement that is transforming the world of work, and bring Scrum to your workplace. To bring Scrum out of the classroom and into practice, you'll need a Certified Scrum Coach (CSC). Certified Scrum Trainers (CSTs) are licensed to teach Certified ScrumMaster® (CSM) and Certified Scrum Product Owner (CSPO) courses within your workplace environment. Scrum Alliance has developed a program for instructors and training organizations that offer certification and noncertification courses pertinent to Agile and Scrum professionals. 1 VersionOne.
Scrum (development) Scrum is an iterative and incremental agile software development framework for managing product development. It defines "a flexible, holistic product development strategy where a development team works as a unit to reach a common goal", challenges assumptions of the "traditional, sequential approach" to product development, and enables teams to self-organize by encouraging physical co-location or close online collaboration of all team members, as well as daily face-to-face communication among all team members and disciplines in the project. A key principle of Scrum is its recognition that during a project the customers can change their minds about what they want and need (often called "requirements churn"), and that unpredicted challenges cannot be easily addressed in a traditional predictive or planned manner. Later, Schwaber with others founded the Scrum Alliance and created the Certified Scrum Master programs and its derivatives. Each sprint is started by a planning meeting.
The SCRUM Blog: 5 Big Issues When Scaling Scrum I think it's a safe bet to say that if you're reading this blog then there is a good chance that you're at least interested in Scrum. The problem is that for many organizations, even the basic concepts in Scrum begin to break down as we scale it up to the entire organization. Imagine a daily stand-up when the development team consists of hundreds of developers and even more testers. These problems are not small and very often can mean the difference between a successful project or a horrific failure. So what are some of the bigger issues at hand? 1) Testing is done outside of the Scrum Team: I'm not talking about unit testing (although those should be part of your definition of done). 2) Team size is too large: Amazon has a rule that any team that can eat more than two pizzas for lunch is too large. 3) The daily standup (and other meetings) are conducted en masse: Each individual team will conduct it's own sprint planning, it's own daily stand-ups and it's own retrospectives.
Introduction to Scrum - An Agile Process Scrum is an agile way to manage a project, usually software development. Agile software development with Scrum is often perceived as a methodology; but rather than viewing Scrum as methodology, think of it as a framework for managing a process. In the agile Scrum world, instead of providing complete, detailed descriptions of how everything is to be done on a project, much of it is left up to the Scrum software development team. This is because the team will know best how to solve the problem they are presented. This is why in Scrum development, for example, a sprint planning meeting is described in terms of the desired outcome (a commitment to a set of features to be developed in the next sprint) instead of a set of Entry criteria, Task definitions, Validation criteria, Exit criteria (ETVX) and so on, as would be provided in most methodologies. Scrum relies on a self-organizing, cross-functional team. Within agile development, Scrum teams are supported by two specific roles.
Stop Using Story Points | Industrial Logic Sprints, standups and story points have come to symbolize Agile methods much like burgers, fries and cola symbolize fast food. Ready for your Agile Happy Meal? I hope not. Like researchers of fast food, we now know that the Agile Happy Meal contains unnatural ingredients that decrease agility and cause process indigestion. In 2007, a series of experiments led my colleagues and me to increase our agility by dropping story points and velocity calculations. Those same experiments led us to replace fixed-length sprints with a flow-based workflow, and move from standup meetings to frequent team huddles. Our process today looks nothing like a by-the-book, mainstream Agile method largely because we actively look for process waste and experiment to discover better ways of working. In this blog, I'll explain why we dropped story points and velocity calculations and what you can do to work successfully without them. My Early Days with Story Points Irrational Story Point Inflation Comparing Teams By Points
Software Development: Agile, Team Size and Dynamics | shmula I’ve long ranted about Amazon’s 2-Pizza Team, which is defined as the following: a team where the team size is no larger than 2 pizzas can feed. Amazon realized early on that in order to cut software development time, the solution was *NOT* to put more people on the project. What is required is a team, where the roles are defined and each member has the right skill for that role, and following a lean, agile, method — all focused on the customer. Agile Methodology Agile is a response to the well known issues in software development: rigid planning and nazi-like fidelity to original software requirements leads to customer needs not being met. Alistair Cockburn, one of the Agile Authors explains Agile this way: Some of Agile Methodology comes from the manufacturing world, specifically the Toyota Production System, but better known as Lean Manufacturing. For me, it is equally fascinating to apply the principles of Lean to software. Team Size and Dynamics At Amazon, there were six roles.
Scrum Log Jeff Sutherland