Gunther Verheyen

DECEMBER 17, 2020

The first, official version of the Scrum Guide was released in February 2010. So, how was Scrum defined before 2010 then? How did its definition evolve before and after 2010 and become the framework that we know today? The Scrum Guide holds the definition of Scrum, they say.

2010 141

2010 SCRUM 2002 2004 141

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”. 262 pages, ET to read: 4 hours, Published April 7th, 2010 by Blue Hole Press). Scrumban and Other Essays on Kanban Systems for Lean Software Dev.

Lean 79

Lean Software Review 2010 2014 79

The IIL Blog

OCTOBER 24, 2023

AI is a branch of computer science that focuses on providing computer hardware and software with the ability to execute intelligent tasks with Generative AI (GenAI) learning and improving with each query. For over a quarter of a century, the Standish Group has tracked, reported, and improved software-intensive project success rates. [1]

Artificial Inteligence 88

Artificial Inteligence Technical Review ChatGPT Generative AI 88

Rebel’s Guide to PM

NOVEMBER 15, 2017

Buzzsumo reports that average shares for video content are trending up by almost double and as far back as 2010 Forbes was reporting that video is a critical information source for senior executives, highlighting an upward trend to watching business content in online video format. Screen capture from Alexa.com, 17 September 2017. And why not?

2010 287

2010 2017 Construction Engineering 287

Rebel’s Guide to PM

OCTOBER 28, 2019

Zombie PM is a term I came up with in 2010 when I put together a project management alphabet. “But this PMO was managing software applications, both in development and in operation. They don’t suggest ways to improve the project management processes. How to spot a zombie project. Why is it they just wouldn’t die?

Underperforming Technical Team 268

Underperforming Technical Team PMO 2010 Governance 268

Herding Cats

DECEMBER 16, 2017

The estimating of software development is both straightforward and complex. Here are some resources that will provide guidance to produce credible software development estimates, in both traditional and agile domains. Software Sizing and Estimating: Mk II FPA , Charles Symons, John Wiley & Sons, 1991. Don't hear one?

Software Developers 46

Software Developers Software Development Estimate 2006 46

Rebel’s Guide to PM

NOVEMBER 12, 2018

Here’s my Must-Read Reading List for some great pointers on the skills, process and experience of engaging people and working together, whether your job is to lead or to follow. Communicating Projects is a process driven book that fully explains the processes of communicating formally on projects. Anthony Mersino: Amacom, 2013.

2013 292

2013 2009 2011 2006 292

ProjectManager.com

OCTOBER 17, 2018

The service simplifies the process to make case preparation often take half the time it would on paper. With dashboards, task lists, document checklists and integration with other case management software, the product is seamless for those in the legal industry. It can even be customized to fit the needs of a specific firm.

Innovation 286

Innovation 2006 2007 2010 286

Teamweek

MAY 30, 2022

It’s a powerful text editing software. Here’s what we’ll cover: How to make a checklist in Word 2010? How to make a checklist in Word 2010? The disadvantage of this method is that it works only with Microsoft Word 2010 and up. And signing up for an app or downloading it may seem like a lot of work. Let’s dive in.

2010 52

2010 2007 Controlling Planning 52

Proofhub

APRIL 6, 2022

Software as a service has been the fastest-growing segment since 2010, and businesses are now investing 50% more in these cloud-based technologies than they did a couple of years ago. It’s important to use well-informed content to educate your target audience about how the software works and how it can benefit their business.

2022 148

2022 2010 Software Review Technical Review 148

Gunther Verheyen

APRIL 24, 2020

Having worked with Scrum since 2003, I am fascinated by its ever-expanding use, which is not limited to software and (new) product development. Ken Schwaber first documented Scrum in 1995 in the paper “ SCRUM Development Process.” In 2010 he initiated the creation of the Scrum Guide.

SCRUM 110

SCRUM 2003 2010 2013 110

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”). The presidents are always dead presidents.

Software 38

Software 2006 Software Developers Software Development 38

Function Point

MAY 9, 2022

Agencies are interested in better defining their workflow processes, are looking for solutions that meet specific needs and the ability to collect all (or most) of their relevant data in one system. The provider will effectively become the business process partner of the agency and serve as both business consultants and IT experts.

2010 40

2010 Software Review Consulting Estimate 40

The Lazy Project Manager

MAY 5, 2016

Based on my ideas and this feedback I checked out the PMI congresses in EMEA and NA and APAC since 2010 and guess what? Stream 1 is the CFP (Call for Papers) process which is formal and automated. – a billion dollar software organisation delivering Workforce Management Solutions. There is no escape from reality now.

PMI 150

PMI 2010 2015 2009 150

Teamweek

SEPTEMBER 10, 2020

Advantages and disadvantages of creating Gantt charts in Excel Step-by-step process to create a Gantt chart using Excel Free Excel Gantt chart templates A simpler and free alternative to making Excel Gantt charts. You can use a whiteboard, or spreadsheet software like Microsoft Excel, or an online tool like Toggl Plan.

2010 98

2010 2013 2016 Risk Management 98

Project Pulse Journal

MARCH 25, 2024

The development process of products and the project lifecycle integrate to deliver the perceived value to stakeholders. Strategic Decision-Making Informative decision-making processes regarding product development, innovation, and investment are crucial for enhancing the likelihood of project and product success.

Sustainability 52

Sustainability Innovation Development Team Review 2024 52

Herding Cats

MARCH 17, 2019

Here are my collected works, presentations, briefings, journal papers, articles, white papers, and essays, used to increase the Probability of Project Success (PoPS) I've developed and applied over my career in the software-intensive system of systems domain. Managment Processes. Presentations and Briefings. Flawless Execution.

2003 54

2003 2011 2008 Performance Measurement 54

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 ? This variation can be explained by the fact that initial concepts do not describe the final software system accurate enough.

2012 48

2012 2007 2011 2010 48

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. 255, April 2010. 24, 2010. “A México, 1 al 3 de Febrero de 2006. 3, March 2002.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Project Pulse Journal

APRIL 2, 2024

As more and more project managers utilize software to track progress, project data becomes more available, leading to data consumption within organizations. Software usage in project management helps managers adapt to the internal and external environment.

Influencer 40

Influencer Governance Government Technical Review 40

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. 24, 2010. “A

Risk Management 35

Risk Management Risk Technical Review 2002 35

Scrum.org

JUNE 5, 2019

Why is there such a strong emphasis on the people needed for the process and so little on the people doing the work? Agile software development started with developers. These days, it seems to be more about Scrum Masters, Agile Coaches, Product Owners, and other “process roles”. But I doubt the reverse is true. does it deploy?)

SCRUM 143

SCRUM 2002 2003 2001 143

Wrike

MAY 23, 2023

I joined the team as a QAA engineer in 2010, the first employee in this role. So we decided to consciously think about how to control this process, predict the potential problems of a rapidly growing test code base, and define the current problems and bottlenecks in the test development process, framework, and test infrastructure.

Engineering 36

Engineering Underperforming Technical Team Controlling Software Review 36

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

Herding Cats

AUGUST 1, 2018

Specific actions to reduce the Episuncertaintiesnaties and Margin to handle the Aleatory uncertainies are part of any good project management process. . The Cone of Uncertainty,” Stephen Gryphon, Phillippe Kruchten, and Steve McConnell, Letters, IEEE Software , 23 (5) 2006, pp 8?10. 37–48, 2007.

2012 29

2012 2007 2010 2006 29

Scrum.org

MAY 26, 2020

“ Christiaan : A friend of mine started a software company. Barry : Failed software development projects. Barry : Failed software development projects. In 2010 I worked as a project manager for a web agency. I was responsible for managing software development projects. He sold solutions, I developed them.

Agile 103

Agile 2004 SCRUM Software Developers 103

ProProfs Project Management

JANUARY 15, 2021

Here’s how the project kanban board looks like: Kanban technique originated from Toyota’s “just-in-time” (JIT) production system and created by Taiichi Ohno who wanted a simple planning system in place to help them manage and control the production process efficiently. Coordinating Sales Process. However, after 1940 David J.

Software Review 81

Software Review Technical Review 2004 SCRUM 81

ProjectManager.com

MARCH 18, 2021

Unfortunately, since MPP files were not designed to be shared outside of Microsoft Project, the project management software that they are created in, trying to open an MPP file extension can cause confusion and delay. Microsoft Project is one of the oldest project management software options around and is a part of MS Office suite.

2003 228

2003 2007 2010 2002 228

Wrike

AUGUST 14, 2020

Toyota was looking for a way to improve their engineering and production processes. The Kanban process was the result of this adaptation. . Toyota used physical cards to signal separate steps in their manufacturing process. Anderson is often credited as being the first to implement Kanban in software development in 2005.

Software Review 36

Software Review Technical Review 2005 SCRUM 36

Herding Cats

DECEMBER 3, 2017

The planned uncertainty not only needs to decrease over time passing, but this reduction diminishes any impacts of risk on the decision-making processes. Seems there is still some confusion (intentional or accidental) about the Cone of Uncertainty and its purpose and its use in software development. 37-48, 2007. 37-48, 2007.

2007 34

2007 2012 2009 2010 34

Herding Cats

NOVEMBER 19, 2018

For software projects, Scrum can be used. These questions and the principles, processes, and practices to support them are Governance of the project. Risk-Informed Decision Making , NASA/SP-2010-576. In our space and defense domain, we have an increasing maturity of the deliverables captures in the Integrated Master Plan.

2010 39

2010 Governance Government Performance Measurement 39

The IIL Blog

JANUARY 10, 2019

I first met Rich Sheridan when we toured Menlo Innovations as part of a career transformation program I was leading in 2010, called “Shifting Gears.” It was one of our first offerings to teach our “Why” (namely, to end human suffering in the world as it relates to technology and return joy to software) and our “How” (i.e.,

Innovation 103

Innovation 2001 2010 Energy 103

Techno-PM

SEPTEMBER 2, 2022

Created by the National Institute of Standards and Technology (NIST) in 2010, RMF’s initial use was to “improve information security, strengthen risk management processes, and encourage reciprocity among federal agencies.” Therefore, creating risk contingency strategies is the next step in a risk management framework.

Risk Management 36

Risk Management Risk Finance Governance 36

Herding Cats

NOVEMBER 14, 2018

When we hear of the difficulties of making decisions in the presence of uncertainty, especially about software features and capabilities, there are straightforward ways to solve this problem. This method is the Analytic Hierarchy Process (AHP). In our agile software development world, AHP is rarely found. The Wrap Up .

Technical Review 47

Technical Review 2010 2014 Software Developers 47

Proofhub

JULY 6, 2021

If you only tell the team things once, it means people will only get one shot at processing and remembering that information. Then blows like sudden resignations show up to put processes in jeopardy and add to the pile of things that cause the manager stress. Losing concentration and forgetting things is normal.

Underperforming Technical Team 78

Underperforming Technical Team 2010 Software Review Executing 78

Herding Cats

JANUARY 9, 2017

Aleatory uncertainty, which is the naturally occurring yields variances in the underlying processes. Epistemic uncertainty comes from probabilistic processes that can be addressed with handling responses. The idea of risk and its management and handling is a critical success factor for all software development. Related articles.

Estimate 28

Estimate Risk 2010 Software Engineering 28

Herding Cats

DECEMBER 15, 2016

The Non-Existent Software Crisis: Debunking the Standish Report. The Standish report: does it really describe a software crisis?" Laurens Eveleens and Chris Verhoef, IEEE Software , vol. 1, Jan-Feb 2010, pages 30-36. Forgetting even more that "agile" is a bottom-up software development solution. Related articles.

2006 28

2006 2010 Estimate Agile 28