Agilemania

DECEMBER 2, 2021

The year was 2011 and there was a pressing need for a scaling framework that could help large organizations design efficient systems to build enterprise level products/solutions to cater to customer’s rapidly changing needs. He introduced the Scaled Agile Framework (SAFe). SAFe is based on following 10 Lean-Agile principles-.

Technical Review 98

Technical Review Agile Software Review Lean 98

Herding Cats

OCTOBER 15, 2017

A popular toss off aphrase in some agile circles is process reduces agility. I've been in the software development business for 30 years, mostly in the Software Intensive System of Systems world, where embedded systems are 100 times more prevalent than business, web and desktop systems. 217–231, 2017.

Process 39

Process Agile 2011 Aerospace 39

Scrum.org

JANUARY 6, 2022

Of course, this list changes with the markets, but if you compare that to 2011, the list is 60% different. Scrum, agile thinking, modern software development working practices are synonymous with Digital Technology and have evolved out of the fundamentally different characteristics of the opportunity presented by technology.

Underperforming Technical Team 221

Underperforming Technical Team Innovation 2001 2011 221

Inloox

JULY 1, 2021

Agility should no longer be a new term for most project managers. High flexibility, adaptability and increased communication are just a few of the benefits that have led to significant improvements through the introduction of agile work processes in organizations. So agility in itself is nothing new for many companies.

Technical Review 100

Technical Review Lean 2011 Cadence 100

Gunther Verheyen

DECEMBER 17, 2020

In the end, the sources I used for describing the evolutions of the definition of Scrum are: The paper “SCRUM Software Development Process” by Ken Schwaber (1995, 1996) The paper “SCRUM: An extension pattern language for hyperproductive software development” by Mike Beedle, Martine Devos, Yonat Sharon, Ken Schwaber and Jeff (..)

2010 141

2010 SCRUM 2002 2004 141

Scrum.org

AUGUST 1, 2022

Some find the process of creating them “childish” or “a waste of time”. Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. Note that we’re using functional job titles here for clarity; not all companies use them, and the Scrum Guide only talks about “developers”. Butchibabu, A.,

2004 225

2004 2010 2009 2016 225

Scrum.org

APRIL 7, 2022

Recently, the concept of “fluid teams”, “dynamic reteaming” or “ad-hoc teaming” has gained traction in the Agile community. Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. Kozlowski & Ilgen (2006) describe this reciprocity as “process begets structure, which in turn guides process”.

Underperforming Technical Team 155

Underperforming Technical Team 2007 2006 2009 155

Agilemania

DECEMBER 6, 2021

It was circa 2011 when Dean Leffingwell decided to conceptualize the Scaled Agile Framework. SAFe is a knowledge base of proven, integrated principles, practices, and competencies for achieving business agility using Lean, Agile, Systems Thinking, and DevOps. You need business agility. Let’s get kickstarted.

Lean 98

Lean 2011 Cadence Innovation 98

MPUG

SEPTEMBER 28, 2020

The following are examples of factors from the PMBOK Guide that lead to said project’s creation: Business process improvements. Software development. Even if you do not have defined model in place, you probably have some processes that could be used as part of your selected methodology. Competitive forces. New Technology.

Retail 119

Retail PMI 2001 2011 119

Agilemania

JANUARY 12, 2022

2011 marked a new beginning in the era of large-scale software project management. Since then, Dean Leffingwell’s brainchild, the Scaled Agile Framework (SAFe) has become the popular emerging agile framework for business agility according to the 15th State of Agile Survey. . But what is SAFe? .

Consulting 98

Consulting Certification Lean Underperforming Technical Team 98

Herding Cats

MARCH 11, 2018

By the way, the pure conjecture that agile enables late changing requirements to not have a significant impact on the cost and schedule of the development project is completely lacking any testable evidence outside of personal anecdotes of agile advocates. Now To Risk Management. Epistemic uncertainty ? from the Greek ??????µ?

Software Developers 34

Software Developers Software Development Risk Management Risk 34

Herding Cats

NOVEMBER 12, 2016

The paper Agile Base Patterns in the Agile Canon , Daniel R Greening, 2016 49th Hawaii International Conference on System Sciences is an important contribution to the discussion of agile at scale in organizations beyond 5 developers at the table with their customer. The Agile Cannon is composed of 5 elements.

Agile 61

Agile 2009 2008 2011 61

Herding Cats

MARCH 17, 2019

Managment Processes. Software for Your Mind: Patterns and Anti-Patterns for Creating and Maintaining a Shared Vision. Making the Impossible Possible: Applying Heliotropic Abundance for creating Program and Project Management Processes. Establishing the Performance Measurement Baseline , AACE Workshop , April 16, 2011.

2003 54

2003 2011 2008 Performance Measurement 54

Herding Cats

MAY 7, 2019

This blog page is dedicated to the resources used to estimate software-intensive systems using traditional and agile development methods. Cost Modeling Agile Software Development,” Maarit Laanti and Petri Kettunen, International Transactions on Systems and Applications, Volume 1 Number 2, pp. & Zein, S.,

Estimate 40

Estimate Software Review Software 2012 40

Herding Cats

NOVEMBER 7, 2016

The same process for estimating is applied to multi-billion dollar projects we work. And the same process is applied to the Scrum development processes on those projects. . Here's some materials that provide the tools and processes needed to learn how to estimate. The Future of Systems-and Software Development.

Estimate 64

Estimate 2006 2005 2013 64

Herding Cats

MAY 10, 2019

This blog page is dedicated to the resources used to assess risks, their impacts, and handling strategies for software-intensive systems using traditional and agile development methods. IEEE Transactions on Software Engineering , Vol. 5, September/October 2011. Risk Management Papers. “A 3, March 2002. 24, 2010.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

MAY 11, 2019

This blog page is dedicated to the resources used to manage the risk encountered on software-intensive systems using traditional and agile development methods. Let's start with a critical understanding of the purpose of managing risk on software development projects. IEEE Transactions on Software Engineering , Vol.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

MARCH 11, 2017

This quote demonstrates a lack of understanding of making decisions in the presence of uncertainty and the processes and events that create uncertainty. There is naturally occurring variability from uncontrolled processes. Aleatory uncertainty is expressed as a process variability. First, let's establish a principle.

2003 46

2003 2014 2015 2011 46

Leading Answers

APRIL 22, 2018

“ Software is eating the world ” claimed venture capitalist, Marc Andreessen in his 2011, New York Times article. Software is becoming omnipresent, it is embedded and integral to all industries. Yet the scientific project management that grew out of the industrialization of process is largely left behind.

Technical Review 124

Technical Review 2011 Transportation Development Team Review 124

EasyProjects

SEPTEMBER 24, 2019

What is Agile Project Management? . Have you ever seen a chef send a dish out without tasting it several times at every stage of the process? That is precisely what agile project management is – taste testing the stew at various points to ensure that it’s tasting the way it should. Agile Project Management Defined.

Agile 41

Agile Technical Review Software Review Underperforming Technical Team 41

Herding Cats

OCTOBER 5, 2018

The primary purpose of software estimation is not to predict a project’s outcome; it is to determine whether a project’s targets are realistic enough to allow the project to be controlled to meet them ? Little [8] makes the claim that agile methods don't follow the Cone - that is the uncertainty doesn't reduce as the project proceeds.

2012 48

2012 2007 2011 2010 48

Herding Cats

OCTOBER 24, 2018

But before going further, let's establish the definitions we need to understand and apply Root Cause Analysis needed to discover the corrective and preventive actions to increase the probability of project success - especially Software Project Success. What Are Problem Causes of Software Projects? All for the want of a nail.

2014 45

2014 Aerospace 2011 2013 45

Scrum.org

AUGUST 17, 2020

Ross & Nisbett (2011) offer an extensive overview of research in this area. . Survival bias happens when failures are ignored when you are evaluating if a process or decision is the right one (Schermer, 2014). HR departments can conclude that their recruitment process is working well because it is producing suitable candidates.

2015 212

2015 2014 2004 Influencer 212

Digite

JANUARY 7, 2018

Several good books have been written on Kanban and its application to various business processes, especially to Scrum, since David Anderson published his original Kanban “blue book”. hours, Published February 2nd, 2011 by Createspace Independent Publishing Platform). Personal Kanban: Mapping Work – Navigating Life. By Jim Benson.

Lean 79

Lean Software Review 2010 2014 79

Herding Cats

APRIL 16, 2019

Management Processes (#MP). Agile Project Management (#APM). Agile Software Development (#ASD). Integrating Agile and Earned Value Management (#AEVM). Agile and Earned Value Management Bibliography of papers, books, and thesis (#Biblio). Management Processes. Planning and Scheduling (#PS).

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Herding Cats

APRIL 4, 2019

Henry Montgomery (Editor), Universitetsforlaget; UK Edition, November 28, 2011. 3421, Second Edition, December 2011. Agile Risk Management and DSDM Pocketbook , Alan Moran, IARM. Agile Risk Management and Scrum , Alan Moran, Institute for Agile Risk Management, 2014. Gideon Keren (Editor),?

Risk Management 43

Risk Management Risk 2003 2011 43

Binfire

APRIL 23, 2020

Binfire , after all, has been a remote working environment since we started in 2011. Managing remote workers is not hard as long as you have set a good remote working process in place. . Having process and rules is good, but it is not worth the paper it is written on (if you still use physical papers) if they are not enforced!

2020 78

2020 Underperforming Technical Team 2011 Retail 78

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. Jeff Bezos, founder of Amazon, likes to use the “two-pizza rule” for strategy and development teams. Beedle, “Agile Software Development with Scrum”, Upper Saddle River, NJ, Prentice-Hall, 2002.

Underperforming Technical Team 52

Underperforming Technical Team 2022 Technical Review 2002 52

Epicflow Blog

MAY 14, 2019

Most organizations build structures and processes designed to prevent project failure. However, Muratgali Karimsakov , a Project Engineer at Karachaganak Petroleum, warns that lessons learned must be applied in the right way: “Unfortunately, the lessons learned process in many companies doesn’t work properly.

Underperforming Technical Team 75

Underperforming Technical Team Technical Review 2002 Software Review 75

Leading Answers

APRIL 22, 2018

“ Software is eating the world ” claimed venture capitalist, Marc Andreessen in his 2011, New York Times article. Software is becoming omnipresent, it is embedded and integral to all industries. Yet the scientific project management that grew out of the industrialization of process is largely left behind.

Technical Review 60

Technical Review 2011 Transportation Development Team Review 60

Planio

JULY 9, 2020

Comfort knowing you’re always running the latest, most stable version of the software. Agile Project Management out of the box. It was developed to help teams collaborate on the tasks, bugs, features, and steps needed to complete a project, visually track their progress, and plan their next steps using Gantt charts. Reliability.

2006 88

2006 2007 Closing Agile 88

Stepping Into Project Management

MARCH 10, 2014

Today we interview Siddhartha Govindraj, who specializes in Lean/Agile processes for software development. An occasional organizer of events as a part of Chennai Agile User Group and speaks in conferences in India and abroad. However, there are a few aspects where agile is still to make a significant mark.

2011 37

2011 Lean 2013 Agile 37

Herding Cats

JANUARY 20, 2018

But in the software development world, the domains of IT, there are two other colors of money. There are two types of software that are developed for a business: 1) internal-use software, and 2) software developed to be sold, leased or marketed (“software to be sold”). CAPEX and OPEX.

Software 38

Software 2006 Software Developers Software Development 38

Herding Cats

OCTOBER 20, 2017

For software development systems like Kanban, which is production line-centric, Litle's Law tells us. λ = average production rate of complete software components. λ = average production rate of complete software components. There are two fundamental assumptions for Little's Law to work in the software development domain".

Underperforming Technical Team 34

Underperforming Technical Team 2008 Software Developers Software Development 34

Wrike

SEPTEMBER 29, 2022

Wrike was launched in 2006 by founder and software developer Andrew Filev. His goal was to create a flexible project management platform that is smart, secure, and versatile enough to enable modern teams to configure it to suit their processes and ways of working. . What is Wrike? What is Asana? Advantages of using Wrike.

2006 36

2006 2011 Software Budget 36

Digite

MARCH 12, 2018

In the usual Scrum process, the P.O. I have often wondered – doesn’t speak too well of us as software professionals! Far too many projects and teams are occupied by far too many crises all through the development/ implementation lifecycle. Also, we have quite diverse roles in the team (i.e.,

Development Team Review 154

Development Team Review Software Review Cadence Technical Review 154

Wrike

NOVEMBER 7, 2018

Agile Project Management. Project Management Software & Tools. Having a knowledge transfer process in place boosts the chance of project success by over 20%. [6]. 19% say Agile techniques. Agile Project Management. 38% of organizations report using agile frequently. [6]. Feature Development Driven – 9%.

2015 60

2015 Technical Review Underperforming Technical Team Software Review 60