Digite

MARCH 12, 2018

That is, does the question below, which I answered on a technical forum recently, describe a situation you might be facing or may have faced in the past? In my over 25+ years in the software industry, this has been an all too familiar situation! I have often wondered – doesn’t speak too well of us as software professionals!

Development Team Review 154

Development Team Review Software Review Cadence Technical Review 154

Leading Agile

NOVEMBER 17, 2020

He is helping us build our technology transformation studio. And in that we grew the company where originally, we did a mixture, as you know, between transformation and building custom software solutions. Over time, we grew to focus more, mainly on customer soft, custom software solutions, and eventually Accenture purchased us.

Technical Review 86

Technical Review Software Review Agile Governance 86

Herding Cats

MAY 10, 2019

Risk Management is essential for development and production programs. Information about key project cost, (technical) performance, and schedule attributes is often uncertain or unknown until late in the program. IEEE Transactions on Software Engineering , Vol. 255, April 2010. México, 1 al 3 de Febrero de 2006.

Risk Management 38

Risk Management Risk Technical Review 2002 38

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

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 2002 35

nTask

AUGUST 8, 2019

This helped us to simplify how nTask project management software can be used for solving such issues. Its simplicity and ease of implementation has made it the most popular version of the systems development life cycle (SDLC) for software engineering and IT projects. Waterfall is a popular SDLC project management model.

Software Review 97

Software Review 2019 Development Team Review Technical Review 97

ProProfs Project Management

JANUARY 15, 2021

As a result, 37% of projects fail due to lack of defined project objectives and milestones visually. Anderson was the first person to implement this kanban approach to project management to their IT, Software Development, and knowledge work in 2004. Some are under review, some are open or complete and some are on hold.

Software Review 81

Software Review Technical Review 2004 SCRUM 81

Herding Cats

NOVEMBER 14, 2018

When we hear of the difficulties of making decisions in the presence of uncertainty, especially about software features and capabilities, there are straightforward ways to solve this problem. In our agile software development world, AHP is rarely found. There are nine technology readiness levels.

Technical Review 47

Technical Review 2010 2014 Software Developers 47

Herding Cats

MARCH 11, 2017

The naturally occurring work effort in the development of a software feature - even if we've built the feature before - is an irreducible uncertainty. The Development of Progress Plans Using a Performance–Based Expert Judgment Model to Assess Technical Performance and Risk,” Justin W. They cannot be suppressed or removed.

2003 46

2003 2014 2015 2011 46

EasyProjects

SEPTEMBER 24, 2019

If you follow the instructions to a tee, it’s going to taste fantastic – just like the reviews say. Agile is most popular in the software industry, but it has found homes in the information technology, engineering, product development, and marketing industries to name a few. Deliver code that is extensible.

Agile 41

Agile Technical Review Software Review Underperforming Technical Team 41

Herding Cats

APRIL 16, 2019

Here's a collection of presentations, briefings, papers, essays, book content used to increase the Probability of Project Success (PoPS) I've written and applied over my career in the software-intensive system of systems and other domains. Business, Technical, Systems, Risk, and Project Management Briefings and Presentations.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Herding Cats

NOVEMBER 5, 2018

In a previous post, Why Johnny Can't Estimate , mentioned some resources for estimating, the principles of business and technical management that demand estimates be made to make decisions, and background on the sources of uncertainty, that create risk, that require estimating to increase the probability of project success. taken from [3]).

Software Review 34

Software Review Technical Review Estimate Software Developers 34

Herding Cats

SEPTEMBER 19, 2018

In this case, the Business as Usually ranges is -5% for low and +10% for a high around the most likely value for the duration, cost, or some technical performance parameter. The business as usual, but with some technical processes get a bit wider. Flight software is always an issue where we work, so those ranges are wider even more.

Technical Review 43

Technical Review 2010 Estimate Software Review 43

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. This can mean multiple review stages, or reports and metrics communicating performance. .

Software Review 36

Software Review Technical Review 2005 SCRUM 36

Herding Cats

JULY 24, 2017

Shipping on time, to specifications, and within budget might be meaningless if a competitor is shipping software that has a greater value to the market. It's suggested from observations, the Cone of Uncertainty (CoU) is not a valid model of how uncertainty behaves in software development projects. Wallshein, Ph.D.

2007 42

2007 2012 2006 2008 42

Herding Cats

JANUARY 22, 2017

Barry Boehm's work in “Software Engineering Economics”. The Cone is a project management framework describing the uncertainty aspects of estimates (cost and schedule) and other project attributes (cost, schedule, and technical performance parameters). This is due to many reasons. Prentice-Hall, 1981.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 17, 2017

Barry Boehm's work in “Software Engineering Economics”. The Cone is a project management framework describing the uncertainty aspects of estimates (cost and schedule) and other project attributes (cost, schedule, and technical performance parameters). This is due to many reasons. Prentice-Hall, 1981.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

FEBRUARY 4, 2017

Barry Boehm's work in “Software Engineering Economics”. The Cone is a project management framework describing the uncertainty aspects of estimates (cost and schedule) and other project attributes (cost, schedule, and technical performance parameters). This is due to many reasons. Prentice-Hall, 1981.

Technical Review 28

Technical Review Estimate 2005 Software Review 28

Workzone

APRIL 30, 2020

In 2010 daPulse, created by Wix.com , joined the vast array of project management tools on the market, and in 2017, daPulse went through a transformation to become Monday.com. Designed to come across as colorful and friendly, Monday aims to help you kick your case of the Monday blues through the use of its software.

2020 38

2020 Software Review Technical Review Software 38

MPUG

SEPTEMBER 9, 2020

You may wish to use this transcript for the purposes of self-paced learning, searching for specific information, and/or performing a quick review of webinar content. Today’s session is eligible for one PMI PDU in the Technical category, and the MPUG Activity Code for claiming is on the screen now.

Software Review 52

Software Review Critical Chain Technical Review Risk Management 52

MPUG

JULY 23, 2020

You may wish to use this transcript for the purposes of self-paced learning, searching for specific information, and/or performing a quick review of webinar content. Kyle: Today’s session is eligible for one PMI PDU in the technical category, and the MPUG activity code for claiming the session with PMI is on the screen now.

Risk 52

Risk Software Review Estimate Underperforming Technical Team 52

MPUG

JULY 23, 2020

You may wish to use this transcript for the purposes of self-paced learning, searching for specific information, and/or performing a quick review of webinar content. Kyle: Today’s session is eligible for one PMI PDU in the technical category, and the MPUG activity code for claiming the session with PMI is on the screen now.

Risk 52

Risk Software Review Estimate Underperforming Technical Team 52

MPUG

MAY 24, 2020

You may wish to use this transcript for the purposes of self-paced learning, searching for specific information, and/or performing a quick review of webinar content. Today’s session is 45 minutes long and eligible for three quarters of a PMI PDU in the technical category. My name is Kyle, and I’ll be the moderator today.

Software Review 40

Software Review Artificial Inteligence Software Developers Software Development 40

MPUG

OCTOBER 16, 2019

You may wish to use this transcript for the purposes of self-paced learning, searching for specific information, and/or performing a quick review of webinar content. And today’s session is eligible for one PMI PDU in the technical category, and the code for claim that is on the screen now, that’s mpugwebnlearn091819.

Agile 40

Agile Technical Review Software Review Engineering 40

MPUG

OCTOBER 9, 2019

You may wish to use this transcript for the purposes of self-paced learning, searching for specific information, and/or performing a quick review of webinar content. Today’s session is eligible for one PMI PDU in the technical category and the code for claiming today’s session is on the screen now.

Agile 40

Agile Technical Review Lean Underperforming Technical Team 40

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. For further insight on Leigh’s entry into project management, read her blog post: How I Made the Move to IT Project Management With No Technical Experience.

2013 28

2013 2003 Technical Review 2010 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. The change in Bank of America’s approach began roughly around 2010, when it hired a new chief information officer, one who championed the use of agile methodology.

Agile 20

Agile Software Review Leadership Technical Review 20