Scrum.org

OCTOBER 19, 2022

They found that the ability of teams to develop a shared sense of value contributed significantly and strongly to project success. Hoda, Stuart & Marshall (2011) interviewed 30 Agile practitioners over a period of 3 years. Journal of systems and software , 81 (6), 961–971. Information and Software Technology , 78 , 83–94.

Agile 214

Agile 2010 2013 2008 214

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 237

Underperforming Technical Team Innovation 2001 2011 237

Gunther Verheyen

FEBRUARY 26, 2024

In 2011 I obtained my license as a Professional Scrum Trainer for Scrum.org from Ken Schwaber (co-creator of Scrum). Why 5: Certification (and beyond) As a licensed Professional Scrum Trainer (since 2011) I obviously teach the official Scrum.org Professional Scrum classes.

SCRUM 74

SCRUM Certification 2016 2011 74

Herding Cats

MARCH 17, 2019

Establishing the Performance Measurement Baseline (PMB) , AACE Workshop, Denver, Colorado, April 16, 2011. Establishing the Performance Measurement Baseline , AACE Workshop , April 16, 2011. Establishing the Performance Measurement Baseline , PMI, Northen Utah Chapter, Professional Development Day, 2012. Project Breathalyzer.

2003 54

2003 2011 2008 Performance Measurement 54

Agilemania

DECEMBER 6, 2021

It was circa 2011 when Dean Leffingwell decided to conceptualize the Scaled Agile Framework. Kanban is a preferred framework for implementing Agile and DevOps software development. 5+ years’ experience in software development, testing, business analysis, product, or project management. But, is there a solution?

Lean 98

Lean 2011 Cadence Innovation 98

MPUG

NOVEMBER 23, 2020

Although technology and software development tools are essential for most projects, it’s the leadership of a project that makes the difference between a project’s success or failure. These numbers were about the same in 2011. Success or Failure of a Project is a People Thing.

Underperforming Technical Team 104

Underperforming Technical Team Technical Review 2011 2015 104

MPUG

SEPTEMBER 28, 2020

Software development. In 2001, new methodology pioneers met in Snowbird, Utah to share their experiences and to suggest ideas for improving the world of software development. They came up with the Agile Manifesto to streamline the development process. Here are some of the major industries: Automotive. Health care.

Retail 119

Retail PMI 2001 2011 119

Herding Cats

MAY 10, 2019

IEEE Transactions on Software Engineering , Vol. 5, September/October 2011. Project risk management: lessons learned from software development environment,” Young Hoon Kwak and Jim Stoddard,” Technovation , 24(11), pp. Project Risk Management: Lessons Learned from Software Development Environment,” Y.

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

Agilemania

JANUARY 24, 2022

In 2011, Dean Leffingwell codified SAFe, the Scaled Agile Framework , to help bring the success that small teams have enjoyed with various agile methodologies such as Scrum or XP but scaled to the enterprise. At the end of every sprint or iteration, the teams should have a potentially deployable product.

Agile 98

Agile Lean 2011 SCRUM 98

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 ? A Probabilistic Method for Predicting Software Code Growth," Michael Ross, Journal of Cost Analysis and Parametrics 4:127-147, 2011. "10

2012 48

2012 2007 2011 2010 48

Herding Cats

OCTOBER 15, 2017

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. the Secretary of Defense shall develop and implement a new acquisition process for information technology systems.

Process 39

Process Agile 2011 Aerospace 39

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. Hybrid–Agile Software Development Anti–Patterns, Risks, and Recommendations,” Paul E.

2003 46

2003 2014 2015 2011 46

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

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. Seven years on, the trend continues, and project managers are also on the menu.   Role Changes.

Technical Review 124

Technical Review 2011 Transportation Development Team Review 124

Techno-PM

MARCH 29, 2022

The British Standards Institution has accredited them to provide certification for ITIL® professionals based on their latest release, ITIL 2011. IT Analyst: An IT analyst is an individual who evaluates, designs develops, and implements information technology systems.

Certification 64

Certification 2011 Healthcare Retail 64

Digite

JANUARY 7, 2018

hours, Published February 2nd, 2011 by Createspace Independent Publishing Platform). A comprehensive guide to Scrumban for applying kanban and pull systems in software development. Probably the earliest treatise on Scrumban, the book describes applying lean manufacturing techniques to software development.

Lean 79

Lean Software Review 2010 2014 79

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. SAFe is based on following 10 Lean-Agile principles-. Take an economic view. Apply Systems Thinking.

Technical Review 98

Technical Review Agile Software Review Lean 98

Binfire

APRIL 23, 2020

Binfire , after all, has been a remote working environment since we started in 2011. If you have software projects, here is a list of software development companies which might be useful if you need custom software development. . In this post, I outline the remote work best practices. Remote Work FAQ.

2020 78

2020 Underperforming Technical Team 2011 Retail 78

Guerrilla Project Management

FEBRUARY 2, 2011

Brought to you by: Project Management Telesummit: March 8-10, 2011 – Don’t miss hearing Rich speak at the Telesummit. Software development projects are. Brought to you by: Project Management Telesummit: March 8-10, 2011 – Don’t miss hearing Rich speak at the Telesummit. Software development projects are.

Sustainability 67

Sustainability 2011 Innovation Software Developers 67

Herding Cats

NOVEMBER 12, 2016

Pink, Drive: The surprising truth about what motivates us (2011). . [2] Alleman, "Product & Process Development Kaizen for Software Development, Project, and Program Management, LPPDE, Denver Colorado, April 2008. [5] Ashkenas, “It’s Time to Rethink Continuous Improvement,” HBR blog [link] (2012). . [3]

Agile 61

Agile 2009 2008 2011 61

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. Seven years on, the trend continues, and project managers are also on the menu.   Role Changes.

Technical Review 60

Technical Review 2011 Transportation Development Team Review 60

Herding Cats

JUNE 9, 2018

With these business principles of software development and projects in general, we can ask and answer five principles of project success. The success of a software product, service, and solution depends on good business, financial, and risk management. 5] "Decisions in software development projects management.

Transportation 39

Transportation Software Engineering Finance 2011 39

ProjectManager.com

MARCH 4, 2022

The scrum methodology was developed as a response to rigid project management approaches such as the waterfall method, which didn’t adapt to the needs of agile product and software development teams. Scrum is part of agile software development and teams practicing agile. What Is the Scrum Methodology? Scrum Values.

SCRUM 337

SCRUM Software Review Development Team Review Underperforming Technical Team 337

Stepping Into Project Management

MARCH 10, 2014

Today we interview Siddhartha Govindraj, who specializes in Lean/Agile processes for software development. He was nominated for the Brickell Key award in 2011, an award given by the Lean Software & Systems Consortium for recognizing achievements in the lean-agile industry and is also a Fellow of the Lean Systems Society.

2011 37

2011 Lean 2013 Agile 37

Herding Cats

JUNE 9, 2018

With these business principles of software development and projects in general, we can ask and answer five principles of project success. The success of a software product, service, and solution depends on good business, financial, and risk management. 5] "Decisions in software development projects management.

Transportation 28

Transportation Software Engineering Finance 2011 28

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

Epicflow Blog

MAY 14, 2019

Merrow (Wiley, 2011), recommended by Giorgio Locatelli , an Associate Professor of Infrastructure Procurement and Management at the University of Leeds. Facts and Fallacies of Software Engineering by Robert L. We would like to thank all participants in this study and wish them successful projects, involved teams, and pleasurable work!

Underperforming Technical Team 75

Underperforming Technical Team Technical Review 2002 Software Review 75

Wrike

SEPTEMBER 29, 2022

Wrike was launched in 2006 by founder and software developer Andrew Filev. The software makes it easy to customize your workspace to reflect your branding and tackle your needs. Rather than changing your processes to fit the software, you customize Wrike to fit your business. . What is Wrike? What is Asana?

2006 36

2006 2011 Software Budget 36

Planio

JULY 9, 2020

If you’re looking for a new project management tool, this guide will run you through the basics of what Redmine is, why it’s a great choice for most software development teams, and how you can get it set up and optimized for you! With the open source community behind it, Redmine has also developed a reputation for stability.

2006 88

2006 2007 Closing Agile 88

TrustRadius Project Management

MAY 1, 2020

Zoom integrates well with many other popular business tools, like Slack , Salesforce , and Google tools, and specializes in solutions for telehealth services, education, and software development. In 2011, Skype made up 40% of all VoIP usage. To learn more about Twilio Voice, check out more verified user reviews here.

Software Review 116

Software Review Technical Review Underperforming Technical Team Technical Support 116

Scrum.org

JANUARY 15, 2022

But, the reality is that over the last 20+ years of the Agile Manifesto, the context, use, and experience with agile provides some evidence that there is a fundamental attribution error concerning the approach to Agile Software development and its execution. It can be a challenging leadership problem and problematic to resolve.

Agile 234

Agile 2001 2011 Software Developers 234

Herding Cats

MARCH 11, 2018

Take for example the deployment of an ERP system, the installation, and startup of a process control system, the release of a suite of embedded software controllers for a car, aircraft, petrochemical plant. A recent survey of 600 firms indicated that 35% of them had at least one "runaway' software project. Editors, Springer, 2011.

Software Developers 34

Software Developers Software Development Risk Management Risk 34

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.

Agile 41

Agile Technical Review Software Review Underperforming Technical Team 41

Scrum.org

FEBRUARY 4, 2022

There are dozens of high-quality academic works to draw from, there are dozens of academic journals dedicated to (agile) software development (ASD) and change management. Some of the references in the paper “The impact of inadequate customer collaboration on self-organizing teams” by Hoda, Noble & Marshall (2011). That is great!

Agile 200

Agile Software Review Underperforming Technical Team Technical Review 200

Scrum.org

APRIL 7, 2022

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 corresponds with research on autonomous teams, as well as principles of Agile software development. The need for fluid teams. So … stable teams or fluid teams?

Underperforming Technical Team 175

Underperforming Technical Team 2007 2006 2009 175

Herding Cats

OCTOBER 16, 2018

A Predictive Analytics Approach to Project Management: Reducing Project Failures in Web & Software Development Projects," Tazeen Fatima, Int'l Conf. Developing analytics models for software project management,” Morakot Choetkiertikul, University of Wollongong, September 9, 2018. Data Mining | DMIN'17.

Aerospace 41

Aerospace Engineering 2012 2014 41