Scrum.org

JANUARY 26, 2020

A software development effort is always a system! Small changes can produce big results—but the areas of highest leverage are often the least obvious (Peter Senge, The Fifth Discipline, 2006). There is no blame (Peter Senge, The Fifth Discipline, 2006). The problem is chronic and not a one-off event.

2006 221

2006 Underperforming Technical Team Consulting SCRUM 221

Herding Cats

NOVEMBER 7, 2016

“Believing is Seeing: Confirmation Bias Studies in Software Engineering, “Magne Jørgensen and Efi Papatheocharous, 41st Euromicro Conference on Software Engineering and Advanced Applications (SEAA). The Use of Precision of Software Development Effort Estimates to Communicate Uncertainty,” Magne Jørgensen, Software Quality Days.

Estimate 64

Estimate 2006 2005 2013 64

Herding Cats

MAY 7, 2019

Effort Distribution to Estimate Cost in Small to Medium Software Development Project with Use Case Points,” Putu Linda Primandari and Sholiq, The Third Information Systems International Conference, Procedia Computer Science, 72, pp. COSMIC Software Estimation Approach,” Alain Abran, ICEAA Workshop, Portland Oregon, June 6?9,

Estimate 40

Estimate Software Review Software 2012 40

MPUG

SEPTEMBER 8, 2019

There are many who have the misconception that Agile is just for software development. As a Microsoft Project MVP since 2006, it has been an amazing journey for me to watch the Microsoft engineering team move from a Waterfall software development program to an Agile one by fully utilizing Project/Project Server.

Agile 89

Agile Technical Review Software Review 2006 89

nTask

NOVEMBER 23, 2018

Introduced in 2006, with a major redesign in 2010, the platform serves as a single systematic and flexible solution for all the task management needs of a team. Considered a #1 software chosen by agile teams for software development, Jira makes a pretty strong contender for Smartsheet.

2019 111

2019 2006 2010 Software Review 111

Scrum.org

AUGUST 17, 2020

More recent analyses have shown that this bias isn’t as fundamental as previously thought (Malle, 2006). The Dunning-Kruger effect manifests when people without any experience with software development make strong claims about how easy a particular change should be. How to reduce this bias. Hazlewood & Olson, 1986). June 1984).

2015 219

2015 2014 2004 Influencer 219

Scrum.org

FEBRUARY 25, 2020

A growth mindset is a term coined by Carol Dweck in 2006 in her book mindset Mindset: The new Psychology of success to describe the underlying beliefs people have about learning and intelligence. In summary, the person with a growth mindset believe that new abilities can be developed through practice. .

2017 173

2017 2018 2016 SCRUM 173

Herding Cats

MAY 10, 2019

México, 1 al 3 de Febrero de 2006. Taxonomy-Based Risk Identification,” Marvin Carr, Suresh Konda, Ira Monarch, Carlo Ulrich, and Clay Walker, Technical Report, CMU/SEI-93-TR-6, Software Engineering Institute, June 1993. Pich, Working Paper, 21/2006, Cambridge University, Judge Business School. De Meyer, C. Loch, and M.

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. México, 1 al 3 de Febrero de 2006. De Meyer, C.

Risk Management 35

Risk Management Risk Technical Review 2002 35

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 ? Schedule Estimation and Uncertainty Surrounding the Cone of Uncertainty," Todd Little, IEEE Software , May/June 2006.

2012 48

2012 2007 2011 2010 48

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! Redmine was launched in 2006 and is still being regularly updated. What is Redmine? Need convincing?

2006 88

2006 2007 Closing Agile 88

Herding Cats

APRIL 4, 2019

Stewart, ACTEX Publications, 2006. Software Risk Management , Barry W. Loch, Arnoud DeMeyer, and Michael Pich, Wiley, 2006. Software Engineering Risk Management , Dale Karolak, IEEE Computer Society Press, 1996. Risk Management in Software Development Projects , John McManus, Routledge, 2003.

Risk Management 43

Risk Management Risk 2003 2011 43

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

Resource Guru

JANUARY 27, 2023

The launch of Google Docs back in 2006 sure brought collaboration to a new (much-needed) level. We’ll run you through some of the features to look out for, to help you collaborate with ease: Collaborative editing: We all loved the early 2000s, but let’s be real, nobody wants to send documents back and forth over email.

Underperforming Technical Team 97

Underperforming Technical Team 2006 Project Life Cycle Logistics 97

Wrike

MARCH 14, 2023

Founded in 2006, Wrike is a flexible and powerful work management solution that helps teams, organizations, and enterprises to plan, collaborate, and execute in one easy-to-use platform. Jira doesn’t offer native time Gantt charts, which means it can’t support projects managed through Waterfall methodology. What is Wrike?

Software Review 41

Software Review Technical Review 2006 Engineering 41

Herding Cats

AUGUST 1, 2018

The Cone of Uncertainty,” Stephen Gryphon, Phillippe Kruchten, and Steve McConnell, Letters, IEEE Software , 23 (5) 2006, pp 8?10. Shrinking the Cone of Uncertainty with Continuous Assessment for Software Team Dynamics in Design and Development,” Pongtip Aroonvatanaporn,”Ph.D. 37–48, 2007.

2012 29

2012 2007 2010 2006 29

Herding Cats

MARCH 17, 2019

Event-Based Scheduling , 10 November 2006. Agile Software Development for Government Software Intensive System of Systems (SISoS) , Boulder Agile Meetup, 27 July 2016. Agile Software Development for Government Software Intensive System of Systems (SISoS) , Boulder Agile Meetup, 27 July 2016.

2003 54

2003 2011 2008 Performance Measurement 54

Wrike

MAY 12, 2023

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. Wrike was launched in 2006 by founder and software developer Andrew Filev.

2006 36

2006 Software Budget Software Developers 36

Herding Cats

DECEMBER 15, 2016

The Standish report: does it really describe a software crisis?" 8, pages 15-16, August 2006. Laurens Eveleens and Chris Verhoef, IEEE Software , vol. Forgetting even more that "agile" is a bottom-up software development solution. The Bunk of Using decades-old report (1966) for basis of #NoEstimates conjectures.

2006 28

2006 2010 Estimate Agile 28

Wrike

AUGUST 3, 2023

While Jira has its strengths — particularly for software developers — it may not provide the full range of features, integrations, and automation a modern organization requires. If you’ve ever been part of a software development team, you’ve probably heard of Jira. But the key here is choosing carefully.

Technical Review 36

Technical Review Software Review Development Team Review Software 36

Herding Cats

DECEMBER 3, 2017

Seems there is still some confusion (intentional or accidental) about the Cone of Uncertainty and its purpose and its use in software development. In “Schedule Estimation and Uncertainty Surrounding the Cone of Uncertainty” (May/June 2006), (the author) expresses some concern about whether uncertainty really does decrease over time.

2007 34

2007 2012 2009 2010 34

Herding Cats

JULY 24, 2017

It's suggested from observations, the Cone of Uncertainty (CoU) is not a valid model of how uncertainty behaves in software development projects. In all software development businesses, showing up late and over budget has a direct impact on the bottom line. . Carol Brennan, John Wiley & Sons, 2006.

2007 42

2007 2012 2006 2008 42

Digite

AUGUST 14, 2017

Be it the “software development process” or the “employee onboarding process” or “the procurement process” – agility is rapidly becoming a cornerstone of our digital world. It was replicated at Robert Bosch’s South Bend, Indiana facility in 2006. The method wars.

Agile 94

Agile Lean 2005 Risk Management 94

Wrike

SEPTEMBER 29, 2022

Wrike was launched in 2006 by founder and software developer Andrew Filev. We’ll introduce both tools, share their best features and advantages, and make a side-by-side comparison to help you choose the best project management solution for your business. What is Wrike?

2006 36

2006 2011 Software Budget 36

Herding Cats

OCTOBER 11, 2016

Here's a typical graph showing a core problem in the software development domain. . Schedule Estimation and Uncertainty Surrounding the Cone of Uncertainty, Todd Little, IEEE Software , May/June 2006. Your project may be different in practice, but the principles are the same. A Few References and Resources .

Performance Measurement 28

Performance Measurement Aerospace 2006 Estimate 28

Herding Cats

JULY 17, 2016

There is a popular graph showing project performance versus the estimated project performance in " Schedule Estimation and Uncertainty Surrounding the Cone of Uncertainty ," Todd Little, IEEE Software , May/June 2006. . In fact estimates can easily be wrong for many reasons.

2006 28

2006 Estimate Software Developers Software Development 28

Planio

JULY 22, 2020

If you’re also interested in Agile project management, pair the PMBOK with the PMI’s new Agile Practice Guide or our own Guide on How to Pick the Software Development Process that’s Right For you. Published date: 2006 (Revised edition). Published date: 2006 (Revised edition). Author: Brett Harned. Published date: 2017.

2020 148

2020 Underperforming Technical Team Technical Review Software Review 148

Herding Cats

MARCH 11, 2017

Hybrid–Agile Software Development Anti–Patterns, Risks, and Recommendations,” Paul E. McMahon, Cross Talk: The Journal of Defense Software Engineering , July/August 2015, pp. Architecting Large Scale Agile Software Development: A Risk–Driven Approach,” Ipek Ozkaya, Michael Gagliardi, Robert L. 12, 2008. “A

2003 46

2003 2014 2015 2011 46

Online PM Courses

DECEMBER 11, 2017

There is so much I’ve highlighted in my 2006 hardback edition, that I don’t know where to start. Jim works in Software Development and talks about a particularly tough year. And if you take on enough of the advice, who knows… Maybe in some future survey, you peers will see you as an Alpha Project Manager.

PMI 61

PMI 2006 Software Review Engineering 61

Wrike

SEPTEMBER 2, 2009

The idea of constant dialogue in project management surfaced in 2001 as one of the principles of so-called agile software development and is described in the Agile Manifesto. Now agile methods are used to manage various projects outside of the software development. Agile Management Essentials. for the Enterprise.

Agile 42

Agile 2006 2003 2001 42

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

Herding Cats

FEBRUARY 9, 2019

There's been a rash of conjectures about all kinds of bad business, project, and software development (agile and traditional) management ideas of late. And money in the bank is what software development is about. Traditional software development processes are like watchmaking.

Estimate 42

Estimate Technical Review Underperforming Technical Team Software Review 42

Herding Cats

APRIL 16, 2019

Agile Software Development (#ASD). Those lessons are directly transferable to the management of software development teams. Parametric Project Monitoring and Control - Earned Value is an approach to Performance measurement for monitoring and controlling the progress of software development projects.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Herding Cats

AUGUST 22, 2018

There's been a rash of conjectures about all kinds of bad business, project, and software development (agile and traditional) management ideas of late. These are classic examples from an author who is either unskilled, untrained, and inexperienced in estimating software development. Save Millions of Dollars?

Estimate 35

Estimate Underperforming Technical Team Technical Review Software Review 35

Herding Cats

JANUARY 23, 2019

There's been a rash of conjectures about all kinds of bad business, project, and software development (agile and traditional) management ideas of late. For software development starts with. maybe a read of the resources of Estimating Agile Software Development may help. Almost impossible?

Estimate 37

Estimate Technical Review Underperforming Technical Team Software Review 37

Herding Cats

JANUARY 22, 2017

Software Sizing, Estimation, and Risk Management, Auer-bach, 2006. [15]Jorgensen, Software Development Effort Estimation: Formal Models or Expert Judgment?” IEEE Software, March-April 2009, pp. A Systematic Review of Software Development Cost Estimation Studies,” IEEE Trans. Software Eng.,

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 17, 2017

Software Sizing, Estimation, and Risk Management, Auer-bach, 2006. [15]Jorgensen, Software Development Effort Estimation: Formal Models or Expert Judgment?” IEEE Software, March-April 2009, pp. A Systematic Review of Software Development Cost Estimation Studies,” IEEE Trans. Software Eng.,

Technical Review 28

Technical Review 2005 Estimate Software Review 28