A BPM view on Scrum. Since the end of the 1990th, we see an ever growing interest in agile methods in software engineering.
At the beginning of this movement, radical methods like Extreme Programming (XP) were proposed. Even though you might need a radical move to kick-start a revolution, it is usually not the radical approach winning the hearts of the many. Nowadays, Extreme Programming plays only a minor role in software development, but the methodology Scrum is very fashionable. But hey, what has a software development method like Scrum to do with business process management? Well, there are many connections. Here at IDS Scheer, we use various development methods.
I took up the challenge to document the Scrum process using BPMN 2. Scrum defines three major roles, which are represented as lanes in my BPMN model: Scrum Master: He works as a mentor, helping all participants to implement the Scrum process. My BPMN model of Scrum shows the main interaction of the different roles. Scrum. Agile Alliance Article Categories. The Business Analyst Role in Agile Software Development (HTML) by Nancy Nee — 14-Jan-13 As companies transition to Agile and Scrum to manage their software development projects, how does this affect the work of business analysts?
Nancy Nee, VP Global Product Strategy at ESI International, shares her opinion on the role of business analysts in Agile software development projects and how this approach impacts the requirement gathering activity. She also provides some input on how to handle conflict between stakeholders. 5 Tips for Getting Software Testing Done in the Scrum Sprint (HTML) by Clemens Reijnen — 21-Sep-12 This article gives you five tips how a clear practice with the support of tools will help teams be more successful in delivering done products when using an agile approach.
Servant Leadership on Agile Teams (PDF) by Gint Grabauskas — 11-Dec-12 As agile coach and department director I mentor my leaders on the virtues of “servant leadership.” By Dusan Kocurek — 21-Dec-11 1. (No link) Scrum and XP from the Trenches. The tricky part to agile software development is that there is no manual telling you exactly how to do it.
You have to experiment and continuously adapt the process until it suits your specific situation. This book aims to give you a head start by providing a detailed down-to-earth account of how one Swedish company implemented Scrum and XP with a team of approximately 40 people and how they continuously improved their process over a year's time. Under the leadership of Henrik Kniberg they experimented with different team sizes, different sprint lengths, different ways of defining "done", different formats for product backlogs and sprint backlogs, different testing strategies, different ways of doing demos, different ways of synchronizing multiple Scrum teams, etc. They also experimented with XP practices - different ways of doing continuous build, pair programming, test driven development, etc, and how to combine this with Scrum.
This book includes: Free download Translations. Scrum Primer - Short Introduction to Scrum. Scrum Guides. Scrum (software 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.