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. Chakraborty and K.

Estimate 40

Estimate Software Review Software 2012 40

Gunther Verheyen

DECEMBER 17, 2020

For every source I have described the same three topics to show what Scrum consisted of at the time (regardless the different terms used), what the ‘definition’ of Scrum was at the time: Roles, responsibilities, accountabilities Controls, deliverables, artifacts Phases, meetings, time-boxes, events.

2010 141

2010 SCRUM 2002 2004 141

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. Coe and Jeffrey H.

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 226

Underperforming Technical Team Innovation 2001 2011 226

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. Even a single change in team membership can disrupt that process, and consequently, make it harder for teams to become high-performing sooner. The need for fluid teams.

Underperforming Technical Team 164

Underperforming Technical Team 2007 2006 2009 164

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”. This is the original book where David Anderson first laid down the definition of and guidance to the Kanban Method for software and knowledge work.

Lean 79

Lean Software Review 2010 2014 79

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. software estimation”), and then select “review articles” under “type” on the left. Academic journals vary in how strict their peer-review process is.

Agile 190

Agile Software Review Underperforming Technical Team Technical Review 190

Inloox

JULY 1, 2021

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. What usually started in software development can now be extended to the entire company and thus, change the way people collaborate.

Technical Review 100

Technical Review Lean 2011 Cadence 100

Agilemania

DECEMBER 6, 2021

It was circa 2011 when Dean Leffingwell decided to conceptualize the Scaled Agile Framework. Software and IT teams delivering in an agile way alone isn’t enough. A SAFe Agilist applies Lean, Agile, and the Product Development flow principles to improve productivity, employee satisfaction, time to market, and quality.

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

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

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. Regardless of whether an organization has a formal program for mentoring or not, the process of skill development needs to be established and pursued.

Underperforming Technical Team 104

Underperforming Technical Team Technical Review 2011 2015 104

Agilemania

JANUARY 12, 2022

2011 marked a new beginning in the era of large-scale software project management. SAFe is a knowledge base of proven, integrated principles, practices, and competencies for attaining business agility using Lean, Agile, Systems Thinking, and DevOps to manage large scale software development. . But what is SAFe? .

Consulting 98

Consulting Certification Lean Underperforming Technical Team 98

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

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. When organizations become more software-driven their systems are never “done”. Well, that’s where things get interesting.

Technical Review 124

Technical Review 2011 Transportation Development Team Review 124

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

Agilemania

JANUARY 24, 2022

The entire organization had to be in the process, not just a few self-managed teams. . 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. What is SAFe?

Agile 98

Agile Lean 2011 SCRUM 98

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

Risk Management 38

Risk Management Risk Technical Review 2002 38

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

Techno-PM

MARCH 29, 2022

The ITIL 4 Managing Professional Transition Module Training is for those who are leading or managing the transition process of an organization, which includes both the people and technology aspects. The British Standards Institution has accredited them to provide certification for ITIL® professionals based on their latest release, ITIL 2011.

Certification 64

Certification 2011 Healthcare Retail 64

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

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

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 factors lead to software project failure?” 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 219

2015 2014 2004 Influencer 219

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

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. Prompt team members to ask questions regularly and ensure there is no ambiguity about process improvements.

Technical Review 98

Technical Review Agile Software Review Lean 98

Herding Cats

APRIL 4, 2019

Research shows that for projects, especially software projects Aleatory uncertainty is the predominant source of risk. So here are some books, handbooks, and guides that sit on my shelf that are used pretty much all the time on the Software Intensive System of Systems we work on. Software Risk Management , Barry W.

Risk Management 43

Risk Management Risk 2003 2011 43

Productivity Land

SEPTEMBER 12, 2023

Since its inception in 2011, the Xamarin community has grown to 1.4 million developers in 120 countries. Xamarin App Development IDEs & Tools Xamarin provides a comprehensive set of tools to facilitate the development of cross-platform mobile applications using C# and the.NET framework.

Software Review 52

Software Review 2011 Transportation Healthcare 52

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. When organizations become more software-driven their systems are never “done”. Well, that’s where things get interesting.

Technical Review 60

Technical Review 2011 Transportation Development Team Review 60

Workzone

JULY 18, 2022

As of January 2022, there are over 450 project management software solutions on the market, according to Software Advice ! With so many choices available, you’re likely wondering which software is right for your team. Top 3 Benefits of Project Management Software. Ranking the Best Project Management Software.

Software Review 26

Software Review Underperforming Technical Team 2022 Software 26

Herding Cats

APRIL 16, 2019

Here's a collection of presentations, briefings, papers, essays, book content used to increase the Probability of Project Success (PoPS) I've written and applied over my career in the software-intensive system of systems and other domains. Management Processes (#MP). Agile Software Development (#ASD).

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Digite

MARCH 12, 2018

In the usual Scrum process, the P.O. In my over 25+ years in the software industry, this has been an all too familiar situation! I have often wondered – doesn’t speak too well of us as software professionals! However, the fact is that software development is a complex activity – perhaps more so than any other type of projects?

Development Team Review 154

Development Team Review Software Review Cadence Technical Review 154

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

Wrike

SEPTEMBER 29, 2022

With today’s speed of work and innovation, it’s imperative that your business finds an ideal work management software to streamline projects , optimize workflows , automate tasks , and enhance team productivity without causing burnout. . Wrike was launched in 2006 by founder and software developer Andrew Filev.

2006 36

2006 2011 Software Budget 36

Herding Cats

JUNE 9, 2018

Cognitive bias - a mistake in reasoning, evaluating, remembering, or other cognitive processes, often occurring as a result of holding onto one's preferences and beliefs regardless of contrary information. Because of that, we don't separate the thinking processes into a dual-system. A process based on tangible evidentiary materials.

Transportation 39

Transportation Software Engineering Finance 2011 39

International Institute for Learning

SEPTEMBER 20, 2022

Visionary impulse is not needed, and therefore it is better to involve, as much as possible, all the team members in the decisions making process., Beedle, “Agile Software Development with Scrum”, Upper Saddle River, NJ, Prentice-Hall, 2002. References. Schwaber, K. Hackman, J. The design of work teams.

Underperforming Technical Team 52

Underperforming Technical Team 2022 Technical Review 2002 52

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. There are two fundamental assumptions for Little's Law to work in the software development domain". Kanban and Software Development.

Underperforming Technical Team 34

Underperforming Technical Team 2008 Software Developers Software Development 34