The IIL Blog

JANUARY 24, 2024

Most of these roles were based on aspects of IT operation, such as mainframe operation and maintenance, which later evolved into software development and commercialisation. LEAN processes emerged in 1991, with the Agile Manifesto launched by a group of software engineers in 2001.

2007 78

2007 2001 Information Technology 2024 78

ProjectManager.com

MARCH 21, 2019

He literally wrote the book about it, It’s All in How You Slice It , which came out in 2005. The idea of a user story as it applies here comes from software development and product management. A user story is an informal description of one or more software features, written from the perspective of an end user in plain English.

Technical Review 296

Technical Review 2005 Software Review Development Team Review 296

Scrum.org

FEBRUARY 3, 2020

Software development is (generally speaking) very complex. Why our brain is not built for software engineering. Although our brain is a marvel of evolution, it has not evolved to excel at the kind of knowledge work (Davenport, 2005) that we actually do most of the time. 2005) Thinking for a living. Being there.

2002 205

2002 SCRUM 2007 2003 205

nTask

AUGUST 18, 2019

Geo-scientific Software Development Projects- Dishansh 2005. Dishansh 2005 is a software that calculates spatial relations by plotting planer and linear structural features, for seismological and geotechnical interpretations. Background. The Process. Network diagram was constructed and the critical path identified.

2005 100

2005 Underperforming Technical Team Technical Review Estimate 100

Productivity Land

MAY 30, 2023

According to a study by FlexJobs, remote work grew by 159% between 2005 and 2017, and the trend has only accelerated due to recent global events. Gone are the days of being bound to a single office location; now, as a remote worker, you can take advantage of modern technology and explore new possibilities.

Technical Review 79

Technical Review Infrastructure Transportation 2005 79

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

nTask

SEPTEMBER 27, 2019

As we have previously discussed that the outsourced software development has increased dramatically in recent years. And since 2005, each year the remote workforce has increased by 10% which makes it 140% in 2019, which is huge. Agile Project Management for Distributed Teams.

Underperforming Technical Team 92

Underperforming Technical Team Agile Technical Review 2005 92

Rebel’s Guide to PM

SEPTEMBER 26, 2016

Maria Cristina Barbero , PMP, PMI-ACP, SMC® has been the Director of the BU Change and IT Strategy of Nexen Business Consultants, the consulting company of Engineering Group, since 2005. She graduated in Mathematics and with an MBA in Global Management.

Software Review 150

Software Review Software Technical Review PMI 150

Wrike

MARCH 9, 2021

First introduced in his 2005 book , user story mapping was a revolutionary concept that took software developers and project managers by surprise. Simply put, user story mapping product management is a concept that starts with giving value to a customer and prioritizes what they want.

Software Review 36

Software Review 2005 Project Life Cycle Development Team Review 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. Management Challenges to Implementing Agile Processes in Traditional Development Organizations," Barry Boehm, Richard Turner, IEEE Software, September/October 2005.

2007 34

2007 2012 2009 2010 34

Herding Cats

SEPTEMBER 25, 2018

Gregory, Operations Research , 23, 2005. [2] Tryin to measure every consequence from the choices between alternatives. 1] "Selecting Attributes to Measure the Achievement of Objectives ," Ralph L. 1] "Selecting Attributes to Measure the Achievement of Objectives ," Ralph L. Keeney and Robin S.

2009 34

2009 Artificial Inteligence 2013 2005 34

Scrum.org

AUGUST 9, 2022

Business does not understand the complexity of software development or engineering work. 1 Patrick Lencioni, Overcoming the Five Dysfunction of a Team, 2005. Sometimes there are plenty of misunderstandings. between these departments regarding their way of working and processes. It may happen that. vice versa.

Technical Review 178

Technical Review Cadence 2005 Initiating 178

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 Government 42

Herding Cats

JANUARY 22, 2017

Software Cost Estimation with COCOMO II, Prentice-Hall, 2000. [10] Agile Estimating and Planning, Prentice-Hall, 2005. [12] Controlling Software Projects: Management, Measurement, and Estimation, Yourdon Press, 1982. [13] Software Sizing, Estimation, and Risk Management, Auer-bach, 2006. [15]Jorgensen, Software Eng.,

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 17, 2017

Software Cost Estimation with COCOMO II, Prentice-Hall, 2000. [10] Agile Estimating and Planning, Prentice-Hall, 2005. [12] Controlling Software Projects: Management, Measurement, and Estimation, Yourdon Press, 1982. [13] Software Sizing, Estimation, and Risk Management, Auer-bach, 2006. [15]Jorgensen, Software Eng.,

Technical Review 28

Technical Review 2005 Estimate Software Review 28

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

FEBRUARY 4, 2017

Software Cost Estimation with COCOMO II, Prentice-Hall, 2000. [10] Agile Estimating and Planning, Prentice-Hall, 2005. [12] Controlling Software Projects: Management, Measurement, and Estimation, Yourdon Press, 1982. [13] Software Sizing, Estimation, and Risk Management, Auer-bach, 2006. [15]Jorgensen, Software Eng.,

Technical Review 28

Technical Review Estimate 2005 Software Review 28

ProjectManager.com

MARCH 21, 2019

He literally wrote the book about it, It’s All in How You Slice It , which came out in 2005. The idea of a user story as it applies here comes from software development and product management. The idea of user story mapping can be traced back to Jeff Patton. What Is a User Story?

2005 33

2005 Agile Lean Risk Management 33

Wrike

AUGUST 14, 2020

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

Software Review 36

Software Review 2005 Technical Review SCRUM 36

MPUG

NOVEMBER 14, 2021

I am a computer engineer by education, and MS Project or any tool, software tool, comes sort of naturally to me. In 1995, I started as a software developer, grew up in the ranks, started managing projects very quickly in my career journey. And in 2005, I did my PMP, Project Management Professional certification.

Software Review 59

Software Review 2005 2008 Initiating 59

Leading Agile

NOVEMBER 26, 2018

You have to do special things to your enviroment (such as editing config files) to run it” That’s from a 2005 article. It can’t run at the same time as any of your other unit tests. This next one was published in 2018, but it isn’t a brand new idea. Michael “GeePaw” Hill.

Software Review 91

Software Review Technical Review 2005 Executing 91

Scrum.org

DECEMBER 8, 2023

I hear the phrase “but not all debt is bad” a lot, usually coupled with “some level of debt is manageable” and, as a software developer, it makes me cringe. The non-linear accumulation of technical debt A good example of this is from the Developer Division (DivDev) at Microsoft in developing a product called Team Foundation Server.

Underperforming Technical Team 180

Underperforming Technical Team Risk 2012 Cadence 180

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 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. Flint, School of Management, Working Paper Series, September 2005.”. Springer, Singapore, 2019.

Estimate 40

Estimate Software Review Software 2012 40

Herding Cats

MAY 10, 2019

Project risk management: lessons learned from software development environment,” Young Hoon Kwak and Jim Stoddard,” Technovation , 24(11), pp. Kadane, and Anthony O’Hagan, Carnegie Mellon University, Statistics & Data Science, January 5, 2005. Elsevier, 2005. 15 July 2005. 255, April 2010. 920, November 2004.

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. Elsevier, 2005. 255, April 2010. Kwak and J.

Risk Management 35

Risk Management Risk Technical Review 2002 35

MPUG

DECEMBER 4, 2019

We were founded in 2005, and as such, we’re one of the oldest, and most established PPM consulting firms in the United States. Could probably be done through custom software development and using an Excel workbook that a company’s each project, or something like that. Now, a word from our sponsor. Kyle: Thanks Dale.

Software Review 52

Software Review Initiating Software Closing 52

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. The first Kanban system at Microsoft in 2005 produced productivity gains of 230%. The method wars.

Agile 94

Agile Lean 2005 Risk Management 94

Herding Cats

APRIL 4, 2019

Cooper, Stephen Grey, Geoffrey Raymond, and Phil Walker, John Wiley & Sons, 2005. Software Engineering Risk Management , Dale Karolak, IEEE Computer Society Press, 1996. Risk Management in Software Development Projects , John McManus, Routledge, 2003. The Silver Lining of Project Uncertainties, Thomas G.

Risk Management 43

Risk Management Risk 2003 2011 43

Teamweek

JANUARY 23, 2020

In their words: Founded in 2005 as an intimate gathering of friends DLD (Digital – Life – Design) has developed into Europe’s leading innovation conference for visionaries from around the globe. In their words: The Biggest multitrack Tech Conference of the Netherlands for all software developers. DLD Conference.

Technical Review 52

Technical Review 2020 Artificial Inteligence Software Review 52