Scrum.org

AUGUST 13, 2019

The first part contains my personal journey in becoming a Scrum Master, the second part includes recommendations for new Scrum Masters. Part 1 — Becoming a Scrum Master. Nine years ago I changed my title from Project Manager into Scrum Master. Do you have any recommendations for my Scrum Master journey?”.

SCRUM 117

SCRUM Certification Telecoms Agile 117

Inloox

JULY 1, 2021

In most cases, however, previous experience is based only on the small-scale use of Scrum or other agile methods in individual departments. SAFe picks up many already familiar elements and concepts from existing methods such as Scrum or Lean Project Management, which makes the transition easier for many companies.

Technical Review 100

Technical Review Lean 2011 Cadence 100

International Institute for Learning

APRIL 19, 2023

They build on lean-agile thinking, and standard Scrum, Kanban, and DevOps practices. DA was developed in 2011 by Scott Ambler and Mark Lines and is based on Scott’s work at Rational Software and IBM. Disciplined Agile is methodology agnostic and supports Scrum, Kanban, Program, and continuous delivery lifecycles.

Agile 59

Agile Cadence Certification Lean 59

International Institute for Learning

MAY 16, 2022

Larkland is participating in the panel on Agile at Large Organizations at IIL’s 2022 Agile & Scrum Online Conference. However, indisputable is the fact that hyper-personalized experiences, products, and services driven by innovative business models are the future for new revenue sources and increased market share.

Artificial Inteligence 59

Artificial Inteligence Agile Cadence 2011 59

Agilemania

JANUARY 24, 2022

The Agile approaches such as Scrum framework, DSDM, Kanban, Extreme Programming (XP) provide rules, practices, and guidelines to build products and solutions using the Agile values and principles. . Most organizations started their Agile journey with one of the frameworks mentioned above, and Scrum is the most popular one.

Agile 98

Agile Lean 2011 SCRUM 98

Scrum.org

FEBRUARY 22, 2021

Scrum has proven to be an effective product delivery framework for all sorts of products. However, Scrum is equally well suited to build the wrong product efficiently as its Achilles heel has always been the product discovery part. How that is supposed to happen is nowhere described in the Scrum Guide.

Software Review 145

Software Review Technical Review Cadence SCRUM 145

Scrum.org

FEBRUARY 25, 2021

Not only does the employees’ engagement matter regarding the topic of goals, but also the clear direction for the organization enables unexpected positive changes (for example, HR, Law, Finance - once they cooperate with Scrum Teams and Product Owners, frequently change their way of working and processes are simplified). 2] Ibidem. [3]

Agile 139

Agile Lean 2011 2015 139

Herding Cats

NOVEMBER 12, 2016

Quest for control (in manufacturing sense) makes innovation harder [2]. Innovation causes variability. Establish a Zero backlog approach to planning - Scrum creates Sprint Backlog. Highly effective Scrum teams have seven items in Sprint Backlog. Pink, Drive: The surprising truth about what motivates us (2011). . [2]

Agile 61

Agile 2009 2008 2011 61

Herding Cats

DECEMBER 16, 2017

Practices for Scaling Lean & Agile Development: Large, Multisite, and Offshore Product Development with Large-Scale Scrum , Craig Larman and Bas Vodde, Addison Wesley, 2010. Scaling Lean & Agle Development: Thinking and Organizational Tools for Large-Scale Scrum , Craig Larman and Bas Voode, Addison Wesley, 2008.

Software Developers 46

Software Developers Software Development Estimate 2006 46

Herding Cats

MAY 10, 2019

5, September/October 2011. A Simulation-Based Risk Network Model for Decision Support in Project Risk Management,” Chao Fang and Franck Marle, in Decision Support Systems , Elsevier, 2011. Khadaka, and Dan Melamed, AACE International , National Capital Section, March 17, 2011. IEEE Transactions on Software Engineering , Vol.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

MAY 11, 2019

5, September/October 2011. A Simulation-Based Risk Network Model for Decision Support in Project Risk Management,” Chao Fang and Franck Marle, in Decision Support Systems , Elsevier, 2011. Khadaka, and Dan Melamed, AACE International , National Capital Section, March 17, 2011. IEEE Transactions on Software Engineering , Vol.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

MARCH 11, 2017

“Quantifying Uncertainty in Early Lifecycle Cost Estimation (QUELCE),” Robert Ferguson, Dennis Goldenson, James McCurley, Robert Stoddard, David Zubrow, and Debra Anderson, Technical Report, CMU/SEI-2011-TR-026 ESC-TR-2011-026. Pesotskaya, 7 th Central and Eastern European Software Engineering Conference, 2011. “A

2003 46

2003 2014 2015 2011 46

The IIL Blog

JUNE 28, 2018

Companies are recognizing that brand loyalty accompanied by a higher level of quality does not always equate to customer retention unless supported by some innovations. According to management guru Peter Drucker, there are only two sources for growth: marketing and innovation [Drucker, 2008]. INNOVATION AND PROJECT MANAGEMENT.

Innovation 106

Innovation 2008 2011 2010 106

EasyProjects

SEPTEMBER 24, 2019

“For example, Microsoft, which began with one team in 2008, several teams in 2009, some 25 teams in 2010 in the Visual Studio group, then several hundred teams in the Developer Division in 2011, and then a commitment to take Agile across the whole organization around 2014. Scrum is used by software development teams. Salesforce .

Agile 41

Agile Technical Review Software Review Underperforming Technical Team 41

Agilemania

NOVEMBER 30, 2021

It was, for this reason, Dean Leffingwell decided to conceptualize SAFe® in 2011. Some of the responsibilities of a SAFe agilist include fixation of schedules, timely increment in systems, applying the synchronization, adoption of Agile and SAFe core values, face-to-face planning, innovation, and planning. Reduced delays.

Cadence 98

Cadence Lean 2011 Construction 98

Scrum.org

APRIL 7, 2022

Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. Bushe and Chu (2011) identify seven situations that drive the use of fluid teaming in those environments: High turnover among employees, leading to changes in teams. This post is my attempt to do this. The need for fluid teams.

Underperforming Technical Team 164

Underperforming Technical Team 2007 2006 2009 164

Agilemania

APRIL 20, 2021

Scaled Agile Framework (SAFe): SAFe was created by Dean Leffingwell and has been in existence since 2011. Large-Scale Scrum (LeSS): Craig Larman and Bas Vodde created the LeSS framework. It developed by taking Scrum and trying many different experiments to discover what works. depending upon the domain of the Scrum teams.

Agile 93

Agile Telecoms 2011 2013 93

Workzone

JULY 18, 2022

Proofhub is an all-in-one project planning software that was launched in 2011. Pros: VersionOne is designed for software development projects built around Agile and Scrum project methodologies. Pros: Highly customizable, JIRA can support Scrum, Lean, or Kanban project methods. Project servers are quoted individually.

Software Review 26

Software Review Underperforming Technical Team 2022 Software 26

Agilemania

APRIL 20, 2021

Scaled Agile Framework (SAFe): SAFe was created by Dean Leffingwell and has been in existence since 2011. Large-Scale Scrum (LeSS): Craig Larman and Bas Vodde created the LeSS framework. It developed by taking Scrum and trying many different experiments to discover what works. depending upon the domain of the Scrum teams.

Agile 52

Agile Telecoms 2011 2013 52

Workzone

APRIL 23, 2020

Proofhub is an all-in-one project planning software that was launched in 2011. . Pros: VersionOne is designed for software development projects built around Agile and Scrum project methodologies. Pros: Highly customizable, JIRA can support Scrum, Lean, or Kanban project methods. Project servers are quoted individually.

Software Review 26

Software Review Underperforming Technical Team Software Technical Review 26

Herding Cats

MAY 7, 2019

Nobel Approaches & Practical Applications, AIT 2011. Effort Estimation for Mobile Applications Using Use Case Point (UCP),” Anureet Kaur and Kulwant Kaur, Smart Innovations in Communication and Computational Sciences. 9, January 2011. Predicting Web Development Effort Using a Bayesian Network,” Emilia Mendes, EASE, 2007. “A

Estimate 40

Estimate Software Review Software 2012 40

Herding Cats

NOVEMBER 7, 2016

And the same process is applied to the Scrum development processes on those projects. . An Analysis of XP, TDD, Pair Programming, and Scrum (Using Real Options),” Dr. David Rico, [link] davidfrico.com/rico08b.pdf. Wetzel, Society of Cost Estimating and Analysis – International Society of Parametric Analysts, 22 December 2011, pp 41-63.

Estimate 64

Estimate 2006 2005 2013 64

International Institute for Learning

SEPTEMBER 20, 2022

For instance in the Agile Scrum Methodology [4] it is recommended to have 10 or fewer people in a team. Beedle, “Agile Software Development with Scrum”, Upper Saddle River, NJ, Prentice-Hall, 2002. Innovation. Regarding the right size of a team, it has been experienced that a good number is around 10. Schwaber, K. Hackman, J.

Underperforming Technical Team 52

Underperforming Technical Team 2022 Technical Review 2002 52