Herding Cats

MARCH 17, 2019

Applying Deliverables Based Planning ® To Increase Our Probability of Success , PMI Fort Worth, Chapter Meeting, 15 July 2010. Agile Software Development for Government Software Intensive System of Systems (SISoS) , Boulder Agile Meetup, 27 July 2016. How to Develop Credible Cost & Schedule Estimate.

2003 54

2003 2011 2008 Performance Measurement 54

Herding Cats

NOVEMBER 7, 2016

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 ‒ Steve McConnell. The Future of Systems-and Software Development. Springer International Publishing, 2016.

Estimate 64

Estimate 2006 2005 2013 64

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 ? Steve McConnell. Quantifying IT Forecast Quality,” J. Eveleens and C. GAO Cost Estimating and Assessment Guide," GAO-09-3SP.

2012 48

2012 2007 2011 2010 48

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. Software Development Effort Estimation using Fuzzy Bayesian Belief Network with COCOMO II,” B.

Estimate 40

Estimate Software Review Software 2012 40

Wrike

NOVEMBER 7, 2018

Organizations that use a methodology: 38% meet budget. 71% meet scope. 68% meet quality standards. 60% meet expected benefits. [4]. VS. Organizations that don’t use a methodology: 31% meet budget. 61% meet scope. 60% meet quality standards. 51% meet expected benefits. [4]. 3% use PRINCE2.

2015 60

2015 Technical Review Underperforming Technical Team Software Review 60

Project Pulse Journal

MARCH 25, 2024

The product manager is operationally focused on functions such as market research, product development, and ensuring products meet customer needs and company goals. Challenges include solving product failures, meeting tight deadlines, and managing cross-departmental communication.

Sustainability 52

Sustainability Development Team Review Innovation 2024 52

Digite

MARCH 12, 2018

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. 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

Herding Cats

MAY 10, 2019

255, April 2010. Project risk management: lessons learned from software development environment,” Young Hoon Kwak and Jim Stoddard,” Technovation , 24(11), pp. 24, 2010. “A Project Risk Management: Lessons Learned from Software Development Environment,” Y. 920, November 2004. Kwak and J. Yamamoto, and K.

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. 255, April 2010. 24, 2010. “A Kwak and J.

Risk Management 35

Risk Management Risk Technical Review 2002 35

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

Wrike

MAY 23, 2023

I joined the team as a QAA engineer in 2010, the first employee in this role. Together, we have developed a unique quality control system for Wrike, our lovely project management platform, allowing us to deploy product code to production more quickly and without bugs. Hello, everyone! I’m Alexander, and I’m a QAA manager at Wrike.

Engineering 36

Engineering Underperforming Technical Team Controlling Software Review 36

Scrum.org

JUNE 5, 2019

Agile software development started with developers. Agile software development was started by developers. Starting out with a strong focus on website development, I built my first site for them in 2002, first as a freelancer later as an employee. I wish this for every developer out there.

SCRUM 139

SCRUM 2002 2003 2001 139

ProProfs Project Management

JANUARY 15, 2021

Anderson was the first person to implement this kanban approach to project management to their IT, Software Development, and knowledge work in 2004. David even built on the methodology to define the kanban method and released a book in 2010 called “Kanban: Successfully Evolutionary Change for your Technology Business”.

Software Review 81

Software Review Technical Review 2004 SCRUM 81

Herding Cats

JULY 24, 2017

customer satisfaction prioritized over arbitrarily meeting a deadline. Landmark’s measure of success over these three years had much more to do with customer satisfaction and market share than with meeting knowingly aggressive targets. Estimating Software Effort Hours for Major Defense Acquisition Programs," Corinne C.

2007 42

2007 2012 2006 2008 42

Herding Cats

SEPTEMBER 19, 2018

From the notebooks, they made estimates for the reducible and irreducible uncertainties to be assured they could meet the contractual dates . Monte Carlo and Agile Development . Harrison, AIP Conference Proceedings , January 5, 2010, 1204, pp. Harrison, AIP Conference Proceedings , January 5, 2010, 1204, pp.

Technical Review 43

Technical Review 2010 Estimate Software Review 43

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

MARCH 4, 2017

These four root causes are: Unrealistic performance expectations - we have optimism that the resulting product or service will performance at the needed levels to deliver the needed capabilities to meet the business goals. Software development project schedule estimation has long been a difficult problem.

2010 28

2010 2007 Estimate Aerospace 28

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

Project Management Hacks

AUGUST 4, 2016

Through many discussions with my husband – who works in software development – I discovered an interest in the technology field. It was a growth experience for me because it involved coming together with the customer to identify creative solutions to meet their needs. Editor’s Note: Rita Mulcahy passed away in 2010.

2013 28

2013 2003 Technical Review 2010 28

Wrike

AUGUST 14, 2020

Anderson is often credited as being the first to implement Kanban in software development in 2005. His book on Kanban , published in 2010, is still one of the most comprehensive resources out there for technology-focused projects. It wasn’t until the early 2000s that Kanban started to take root in project management.

Software Review 36

Software Review Technical Review 2005 SCRUM 36

Herding Cats

JANUARY 22, 2017

When actual measures of cost, schedule, and technical performance are outside the planned cone of uncertainty, corrective actions must be taken to move those uncertanties inside the cone of uncertanty, if the project is going to meet it's cost, schedule, and technical performance goals. . ASE’10, September 20–24, 2010, Antwerp, Belgium. . [8]

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 17, 2017

When actual measures of cost, schedule, and technical performance are outside the planned cone of uncertainty, corrective actions must be taken to move those uncertanties inside the cone of uncertanty, if the project is going to meet it's cost, schedule, and technical performance goals. . ASE’10, September 20–24, 2010, Antwerp, Belgium. . [8]

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Runrun.it

OCTOBER 1, 2019

The concept originated from software development companies, who found the traditional method of project and workflow management was stifling in many situations. Members were collectively equipped to meet tasks requirements, and the collaborative nature of the team easily allowed members with less expertise to catch up fairly quickly.

Agile 20

Agile Software Review Leadership Technical Review 20

Herding Cats

FEBRUARY 4, 2017

When actual measures of cost, schedule, and technical performance are outside the planned cone of uncertainty, corrective actions must be taken to move those uncertanties inside the cone, if the project is going to meet it's cost, schedule, and technical performance goals. . ASE’10, September 20–24, 2010, Antwerp, Belgium. . [8]

Technical Review 28

Technical Review Estimate 2005 Software Review 28

MPUG

OCTOBER 9, 2019

And so this is where agile kind of fits in and isn’t just necessarily only for software development. And remember, agile is kind of born out of the need for technical project management or in many cases, software development. But it is clearly not limited to just software.

Agile 40

Agile Technical Review Lean Underperforming Technical Team 40

MPUG

OCTOBER 16, 2019

So somebody tells me what they’re looking for, and I’m thinking how can I deliver this without actually meeting the requirement? And the focus of where the effort is with the intent to have these things meet in the middle. Tim Runcie: Legacy Project is powerful. That is great.

Agile 40

Agile Technical Review Software Review Engineering 40