Favoriser l'amélioration continue
Découvrez une vaste gamme de sujets et de modèles scrum avancés qui peuvent augmenter la vélocité de votre équipe. Cours en ligne et classes pour Scrum Masters, Scrum Product Owners, et les membres de l'équipe qui cherchent à s'améliorer continuellement. Si vous n'êtes pas membre, visitez notre page de tarifs et de plans pour plus de détails.
Modèles : Finir tôt, accélérer plus vite
Finish Early, Accelerate Faster (FEAF) est un langage de modèles Scrum composé d'un certain nombre d'éléments suivants Modèles Scrum utilisés ensemble. Le FEAF est un langage de modèles incroyablement puissant parce qu'il aide les nouveaux utilisateurs à Les équipes établir des bonnes pratiques et prendre des équipes expérimentées Hyperproductif; défini comme un Vélocité 400% supérieure à la vitesse initiale de l'équipe.
Scrum Rétrospectives
L'un des principes fondamentaux de Scrum est l'idée d'amélioration continue. Chaque Sprint les L'équipe s'engage dans un cycle d'inspection et d'adaptation au cours de l'année. Rétrospective réunion. Cependant, le guide Scrum n'offre pas beaucoup d'informations sur la manière de mener une rétrospective réussie et d'utiliser la réunion pour améliorer la production, la qualité et la rapidité.
Tous les sujets relatifs à l'amélioration continue
Scrum Influencers: Colin Angle, CEO of IRobot
Scrum origins include the work of Colin Angle. As an MIT student, he sublet space in 1990 at my Object Databases lab in Cambridge and had his early robots hunting me down in my office. I spent a lot of time understanding Rodney Brooks subsumption architecture and it...
The First Scrum Project Manager
John Scumniotales, the first ScrumMaster "The end of the project manager, the birth of the ScrumMaster, a transient job valid until the organization has changed and is self-managing." Ken Schwaber The quote from Ken Schwaber elequently describes the role of a project...
Scrum Evolution: What’s it all about?
Love it or hate it, the Agile 2005 Conference reviewers thought the paper below was either a major innovation or a gross violation of the principles (dogma) of Scrum. It's motto is innovate or die and only the paranoid survive in the global economy. Does it show the...
Attila II: Scrum Progenitor Honors Scrum Gathering
Attila II: Progenitor of Scrum, hotel@MIT The Scrum Gathering this week is at hotel@MIT in Cambridge. I'm sitting in on a ScrumMaster training course led by Ken Schwaber. We plan on doing one together at PatientKeeper in Boston in August. This would be a great...
Scrum: Where Did Rapid Application Development Come From?
IEEE Computer published an issue on agile development in 2003. Of particular interest is an article on the history of iterative development, highly recommended for anyone interested in the background Agile methods. Most of the "Rapid Application Development (RAD)"...
Scrum Godfathers: Takeuchi and Nonaka
Takeuchi and Nonaka are Godfathers of the Scrum Agile Process since they coined the term in their seminal paper in the Harvard Business Review in 1986: Takeuchi, H. and I. Nonaka, The New New Product Development Game. Harvard Business Review, 1986(January-February)....
Scrum Evolution: Type A, B, and C Sprints
One of the key influences that led to creation of the first Scrum was a paper on the Japanese way of new product development by Takeuchi and Nonaka [2]. This paper had a chart showing product development separated into silo’s (Type A), phases slightly...
Scrum: Involving the Customer
Creation of the Agile Manifesto at Snowbird 2001 There was a dialogue in the scrumdevelopment group today on how customers should be involved with Scrum teams, prompting me to regurgitate a few of the examples I have been involved in since the first Scrum in 1993....
Google Gmail
Now that I have given away Gmail accounts to anyone on the PatientKeeper development team who wants one, I have a few more to pass on to people in the Scrum community. If you have been looking for a Gmail account, send me a note. First come, first serve.
Scrum: Subsumption Architecture and Emergent Behavior
PicBot exhibiting emergent behavior Yesterday's posting on the birth of Scrum generated some questions on Rodney Brooks' subsumption architecture. One could argue that Agile processes emerge architectures by building the simplest possible thing and evolving into more...