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. How Many Licks: or how to estimate damn near anything , Aaron Santos, Running Press, 2009.

Software Developers 46

Software Developers Software Development Estimate 2006 46

The IIL Blog

JANUARY 3, 2024

How can Agile methodologies be adapted and implemented in non-software development projects?” “Why She has extensive experience with the entire Software Development Life Cycle (SDLC) using both Waterfall and Agile based development practices. Use these to get a broad understanding of a topic.

Artificial Inteligence 154

Artificial Inteligence Generative AI ChatGPT Software Review 154

The IIL Blog

DECEMBER 20, 2023

How can Agile methodologies be adapted and implemented in non-software development projects?” “Why She has extensive experience with the entire Software Development Life Cycle (SDLC) using both Waterfall and Agile based development practices. Use these to get a broad understanding of a topic.

Artificial Inteligence 167

Artificial Inteligence Generative AI ChatGPT Software Review 167

Scrum.org

APRIL 7, 2022

Research has linked team cognition to higher performance and motivation (Mathieu et al, 2000), increased effectiveness (Kearny, Gebert & Voelpel, 2009), and generally explains a substantial amount of the variance (~19%) in the effectiveness of teams (De Church & Mesmer-Magnus, 2010). So … stable teams or fluid teams? Forsyth, D. Kearney, E.,

Underperforming Technical Team 202

Underperforming Technical Team 2007 2006 2009 202

Herding Cats

MARCH 30, 2019

Agile software development is framed by a manifesto , a set of 12 principles, several methods. These are all focused on developing software, delivering that software to those paying the developers. Why This Missing Concept is Important to Agile Software Development? . 81-100, 2009. [4]

Software Developers 39

Software Developers Software Development Agile Software 39

Rebel’s Guide to PM

JANUARY 28, 2022

This brainstorming element normally falls outside of the traditional project management role, but is more prevalent in software projects, when engineers have a free reign to come up with new ideas and then have to see them through. This review first appeared on the blog in 2009. Section Two looks at skills. Ten stars for Berkun.

Software Review 195

Software Review Technical Review Underperforming Technical Team 2009 195

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 144

2010 SCRUM 2004 2002 144

Herding Cats

MARCH 11, 2018

Take for example the deployment of an ERP system, the installation, and startup of a process control system, the release of a suite of embedded software controllers for a car, aircraft, petrochemical plant. A recent survey of 600 firms indicated that 35% of them had at least one "runaway' software project. Now To Risk Management.

Software Developers 34

Software Developers Software Development Risk Management Risk 34

The IIL Blog

MAY 17, 2023

Systems development projects, especially those with a large software component, would spend years gathering requirements, designing, and building a system that would be plagued by changes and completely outdated by the time it was launched. 2 weeks until IIL’s Agile & Scrum 2023 Online Conference!

Aerospace 147

Aerospace Technical Review Underperforming Technical Team Governance 147

Digite

JANUARY 7, 2018

hours Published January 12, 2009, by Modus Cooperandi Press). A comprehensive guide to Scrumban for applying kanban and pull systems in software development. Probably the earliest treatise on Scrumban, the book describes applying lean manufacturing techniques to software development. By Corey Ladas.

Lean 79

Lean Software Review 2010 2014 79

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). Fitzgerald, B (2009). Creativity in agile systems development: a literature review.

Innovation 59

Innovation Agile 2002 2001 59

Herding Cats

MARCH 17, 2019

Deliverables Based Planning: Providing Actional Information to the Program Manager , 11th Annual Rocky Mountain Project Management Symposium, 2009. Increasing the Probability of Success , Dallas MPUG, May 6th, 2009. Product & Process Development Kaizen , LPPDE, Denver, Colorado, April 21-23, 2008. Agile Project Management.

2003 54

2003 2011 2008 Performance Measurement 54

Herding Cats

NOVEMBER 12, 2016

Agile Conference 2009, IEEE. . [4] Alleman, "Product & Process Development Kaizen for Software Development, Project, and Program Management, LPPDE, Denver Colorado, April 2008. [5] Ashkenas, “It’s Time to Rethink Continuous Improvement,” HBR blog [link] (2012). . [3]

Agile 61

Agile 2009 2008 2011 61

Online PM Courses

SEPTEMBER 16, 2018

In 2009 Ken Schwaber left Scrum Alliance to build his own Agile certification, PSM (Professional Scrum Master), at scrum.org. Their certified Digital Agilist qualifications are more software development than project management certifications. I will justify this statement after I’ve shown you what scrum.org has to offer.

Certification 140

Certification Agile Prince2 PMI 140

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 ? Verhoef, Science of Computer Programming, Volume 74, Issues 11–12, November 2009, Pages 934-988. Steve McConnell. Eveleens and C.

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. 12, 2008. “A

2003 46

2003 2014 2015 2011 46

Herding Cats

OCTOBER 15, 2017

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. the Secretary of Defense shall develop and implement a new acquisition process for information technology systems.

Process 39

Process Agile 2011 Aerospace 39

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. A Correction fixed the immediate non-conformance. All for the want of a nail.

2014 45

2014 Aerospace 2011 2013 45

Herding Cats

DECEMBER 28, 2017

The use of estimating in software development project mandates those estimates be updated with actual performance data to have any credibility in the construction of the Estimate to Complete and Estimate at Completion. Economics of Software Development. The Economics of Software Quality. The Fallacy.

2009 40

2009 Estimate Software Developers Software Development 40

Herding Cats

OCTOBER 30, 2018

This document is all but unknown in the Enterprise IT domain and completely unknown in the agile software development world. This missing document is a root cause of many failures in tradition and agile software development.

Planning 109

Planning 2007 Technical Review 2009 109

Herding Cats

APRIL 16, 2019

Agile Software Development (#ASD). Those lessons are directly transferable to the management of software development teams. Deliverables Based Planning: Providing Actional Information to the Program Manager - 11th Annual Rocky Mountain Project Management Symposium , 2009. Dallas MPUG , May 6th, 2009.

Technical Review 42

Technical Review Performance Measurement 2003 Governance 42

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. Tim Menzies, Steve Williams, Oussama Elrawas, Daniel Baker, Barry Boehm, Jairus Hihn, Karen Lum, and Ray Madachy, Software Process Improvement And Practice, (2009).

2007 34

2007 2012 2009 2010 34

Herding Cats

SEPTEMBER 25, 2018

7] "Decision Making Under Uncertainty: Think Clearly, act Decisively and Feel Confident - Unilever's Story," Sven Roden, 2009 Palisade Conference, Risk Analysis, Applications, and Training, 21-22 October 2009. . Tryin to measure every consequence from the choices between alternatives.

2009 34

2009 Artificial Inteligence 2013 2005 34

Herding Cats

OCTOBER 27, 2016

There are two kinds of uncertainty on all projects, no matter the domain, including software development projects. The process of making a decision involves three elements: values, alternatives, and facts (Buede, 2009). [1]. The Notion of Enterprise Software Development. Related articles. Quote of the Day.

2009 28

2009 2015 Influencer Performance Measurement 28

Herding Cats

FEBRUARY 23, 2016

This list starts with the earliest posts, beginning in 2009. . New Books for Work - making multiple decisions, forecasting and simulating software development projects, forecasting methods and applications. How to Estimate Software Development - Update. Estimating Software-Intensive Systems.

Estimate 39

Estimate Risk Management Finance Software Developers 39

Wrike

APRIL 12, 2016

In his conversational writing style, he tackles the parallels between software development and marketing, walks you through the workflows and best practices behind Agile marketing, and lays out everyday tactics for managing the entire marketing process successfully. Snapchat) as well as an entire chapter on sales & service.

2014 36

2014 2015 2016 Technical Review 36

Leading Agile

NOVEMBER 17, 2020

So we first worked together, I guess it was probably back in like late 2009, 2010. Talk to me about some of the challenges that you had taking it straight from a software development perspective. I wasn’t actually trying to help anybody get better at software development per se, or product management per se.

Technical Review 112

Technical Review Software Review Agile Governance 112

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

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

Herding Cats

FEBRUARY 4, 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 Estimate 2005 Software Review 28

MPUG

SEPTEMBER 9, 2020

Satya N Dash: In addition to that, I have seen management practitioners when they create a plan, they make a lot of mistakes, without any software tool, in this case Microsoft Project. As early as 2009, 2010, nearly 11 years before I was working as a PMO. One is a software developer.

Software Review 52

Software Review Critical Chain Technical Review Risk Management 52

Scrum.org

MARCH 16, 2020

I believe Agile software development is more than ready to use new forecasting techniques to express uncertainy to narrow their decision-making process. These new forecasting techniques are not based on estimations but historical data, thus saving time on the part of developers to focus on what they do best.

Agile 242

Agile Underperforming Technical Team Estimate 2030 242

MPUG

NOVEMBER 14, 2019

Let’s change this and set this to a month basis, for instance, where we see the date format changes to January 2009, which is a time ago, but what we see happening is that that S curve starts to show up, which is a very nice visual compared to what we previously had, what might have been a to higher up granularity. I click on create.

2013 40

2013 Finance 2007 Software Review 40

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 Development Software Developers 38

Herding Cats

APRIL 4, 2019

Probabilistic Risk Analysis: Foundations and Methods , Tim Bedford and Roger Cooke, Cambridge University Press, 2009. Software Risk Management , Barry W. Strategic Project Risk Appraisal and Management , Elaine Harris, Gower, 2009. Failure of Risk Management: Why It’s Broken and How to Fix It, Douglas Hubbard, 2009.

Risk Management 43

Risk Management Risk 2003 2011 43

Herding Cats

OCTOBER 16, 2018

"Applicable of Model-Based Systems Engineering Methods to Development of Combat System Architectures," John M.Greenn, 6 th Annual Acquisition Research Symposium of the Naval Post Graduate School: Volume 1: Defense Acquisition in Transition, May 13-14, 2009. Data Mining | DMIN'17.

Aerospace 41

Aerospace Engineering 2012 2014 41