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. A bit of context on NowOnline.

SCRUM 174

SCRUM 2003 2002 2001 174

International Institute for Learning

JULY 7, 2022

During the last two decades there has been the emergence of a number of software development methods as a response to the inefficiency of existing software development methods in rapidly changing environments (Highsmith, 2004). ” Software Development 9(8): 28-32. August 2002). Beedle (2002).

Innovation 59

Innovation Agile 2002 2001 59

Leading Agile

FEBRUARY 11, 2019

When I first learned about Agile methods in 2002, the principles seemed to offer an ideal solution to many organizational issues common at the time. How can the same principle be a good idea in 2002 and a bad idea in 2019? It is as close to a “single piece pull” model as will work for a software development process.

Agile 116

Agile Underperforming Technical Team Software Review Technical Review 116

International Institute for Learning

APRIL 12, 2023

I remember getting my PMP back in 2002 and being instructed over and over to prevent changes from even being raised! Rubin Jen has been in the project management field for over 25 years; Spanning aerospace, engineering, telecom, software development, outsourcing, consulting, and government sectors.

Agile 59

Agile 2002 Telecoms Aerospace 59

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

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. 8, August 2002 pp.

2003 46

2003 2014 2015 2011 46

Herding Cats

MARCH 17, 2019

Agile Software Development for Government Software Intensive System of Systems (SISoS) , Boulder Agile Meetup, 27 July 2016. Integrating Agile Software Development with Earned Value Management , College of Performance Management, IPM Workshop, 2015. Agile Software Development. Earned Value Management.

2003 54

2003 2011 2008 Performance Measurement 54

Herding Cats

JULY 8, 2018

This advocate continually confuses Macroeconomics of financial markets and sovereign finance with Microeconomics of software development. Here's a book review from 2008, about Black Swans and Fooled By Randomness in the context of managing software development in the presence of uncertainty. Pich, Christoph H.

2002 34

2002 2008 Technical Review Software Review 34

MPUG

SEPTEMBER 11, 2023

Jira’s inception traces back to April 2002, birthed by Atlassian, a company founded by two Australian friends, Mike Cannon-Brooks and Scott Farquhar. Today, in 2023, Jira stands as arguably the most preferred project management software globally. Today, I champion its use at Visor, aiming to inspire others with my passion for it.

Technical Review 52

Technical Review Software Review 2002 Manufacturing 52

Leading Agile

JUNE 18, 2018

In a 2002 piece entitled The Law of Leaky Abstractions , Joel Spolsky observed that abstractions over any implementation can leak details of that implementation. Our unit test suite gives us a degree of protection at build time, and using Design By Contract gives us a degree of protection at run time. Contracts vs. Promises.

Software Review 103

Software Review Underperforming Technical Team Technical Review Artificial Inteligence 103

Herding Cats

APRIL 13, 2018

This is the same paradigm of Agile software development where responding to change over following the plan is part of the original manifesto. If you google "Real Options software development" or "real options ICT" you'll find these and many dozens more. Here's a sample. 72, 2nd Quarter, 2008, pp.

2008 32

2008 2002 Estimate Software Engineering 32

Epicflow Blog

MAY 14, 2019

Facts and Fallacies of Software Engineering by Robert L. Glass ( Addison-Wesley Professional, 2002), also recommended by Giorgio Locatelli. Here are links to the surveys we conducted, where you can find even more useful insights: Discussion in Agile and Lean Software Development.

Underperforming Technical Team 62

Underperforming Technical Team Technical Review 2002 Software Review 62

Wrike

AUGUST 5, 2020

A 2002 PMI study found that “there is a strong link between the amount of risk management undertaken in a project, and the level of success of the project; more successful projects use more risk management.” . But why is risk management so important for project managers, anyway? . Why assessing risk is important.

Risk 41

Risk 2003 2002 PMI 41

Herding Cats

JULY 8, 2018

This advocate continually confuses Macroeconomics of financial markets and sovereign finance with Microeconomics of software development. Here's a book review from 2008, about Black Swans and Fooled By Randomness in the context of managing software development in the presence of uncertainty. Pich, Christoph H.

2002 28

2002 2008 Technical Review Software Review 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: 2002. Project Management for Humans: Helping People Get Things Done. Author: Brett Harned. Published date: 2017.

2020 148

2020 Underperforming Technical Team Technical Review Software Review 148

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 2003 Governance 42

Workzone

APRIL 23, 2020

53 Best Project Management Software Solutions. Workzone is a US-based company that has been a major player in the project management world since 2002. Pros: Workzone offers more than just a software solution. If your team does software development or another DevOps field, Planio could be a great option.

Software Review 26

Software Review Underperforming Technical Team Software Technical Review 26

Boost by Brightpod

SEPTEMBER 18, 2017

I started my career as a software developer in 2002 after graduating in B.S. Mathematical Sciences/ Computer Science from the University of North Carolina at.

2002 60

2002 Software Developers Software Development Software 60

Workzone

JULY 18, 2022

53 Best Project Management Software Solutions. Workzone has been a major player in the project management world since 2002. Pros: Workzone offers more than just a software solution. If your team does software development or another DevOps field, Planio could be a great option. See it in Action.

Software Review 26

Software Review Underperforming Technical Team 2022 Software 26

Workzone

AUGUST 4, 2021

Jira is the flagship product of Australian software developer Atlassian’s. Jira began as a bug tracking software, but it has grown into a popular project management tool. ProjectManager.com is a robust project planning software developed by ProjectManager.com, Inc. Pricing: Free – $20.83/user/month. user/month.

2021 26

2021 Software Review Technical Review Underperforming Technical Team 26

Workzone

JULY 13, 2021

After all, Workzone has been helping teams bring order to their project chaos since 2002. Its VersionOne (now known as Digital.ai) product offers a work management suite complete with project management software. is designed for software development projects built around Agile and Scrum project methodologies.

2021 26

2021 Software Review Technical Review Underperforming Technical Team 26

Herding Cats

APRIL 4, 2019

Managing Project Risk and Uncertainty: A Constructively Simple Approach to Decision Making , Chris Chapman and Stephen Ward, John Wiley & Sons, 2002. Software Engineering Risk Management: Finding your Path Through the Jungle, Version 1.0 , Dale Karolak, IEEE Computer Society, 1998.

Risk Management 43

Risk Management Risk 2003 2011 43

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

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 2012 64

Herding Cats

MAY 10, 2019

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

Risk Management 38

Risk Management Risk Technical Review 2004 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 2004 35

Leading Agile

AUGUST 20, 2018

They asked a software developer what it would take, and he estimated something like 20,000 pounds over several months. You probably remember the case of the Volkswagen software engineer who was sentenced to prison for writing code that enabled vehicles to pass emissions tests fraudulently. It is not true.

Software Review 78

Software Review Software Technical Review Development Team Review 78

International Institute for Learning

SEPTEMBER 20, 2022

Beedle, “Agile Software Development with Scrum”, Upper Saddle River, NJ, Prentice-Hall, 2002. Martine Haas and Mark Mortensen, “The Secrets of Great Teamwork”, Harvard Business Review, June 2016. Schwaber, K. Rich Karlgaard, “Team Management: Think Small and Agile”, forbes.com, Nov 13, 2013. Hackman, J. The design of work teams.

Underperforming Technical Team 52

Underperforming Technical Team 2022 Technical Review 2002 52