Epicflow Blog

MAY 30, 2023

Let’s consider an example: when a person undergoes medical treatment, the success of the endeavor will depend on the doctor’s expertise, the quality of medication, and the patient’s diligence in following the doctor’s recommendations. Therefore, it’s up to a project manager to review every possible event and plan responses to each of them.

Technical Review 52

Technical Review Software Review Aerospace 2010 52

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

Herding Cats

MAY 7, 2019

This blog page is dedicated to the resources used to estimate software-intensive systems using traditional and agile development methods. Cost Modeling Agile Software Development,” Maarit Laanti and Petri Kettunen, International Transactions on Systems and Applications, Volume 1 Number 2, pp. Performance Evaluation of non?Markovian

Estimate 40

Estimate Software Review Software 2012 40

Herding Cats

MARCH 11, 2018

Microeconomics is applicable to the development is software systems. If we look at the discipline of software engineering, we see that the microeconomics branch of economics deals more with the types of decisions we need to make as software engineers or managers. Software engineering economics." Macroeconomics is not. .

Software Developers 34

Software Developers Software Development Risk Management Risk 34

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). By Luigi Morsa. The most popular and pioneer methods, as highlighted by Conboy et al.

Innovation 59

Innovation Agile 2002 2001 59

Scrum.org

APRIL 7, 2022

Wang et al (2006) studied software teams tasked with ERP implementations and found that cohesive teams performed significantly better than less-cohesive teams. This is probably due to the difficulty of measuring many teams over a long period of time. The wish behind fluid teaming risks becoming the father of its thought.

Underperforming Technical Team 161

Underperforming Technical Team 2007 2006 2009 161

Strategy Execution | PMO Perspectives

MARCH 14, 2019

Although we face many uncertainties at all of these levels, both in terms of threats and opportunities, we can be confident that our corporate risk management structure enables us to understand the risks, and provides a framework within which acceptable risk may be managed in line with stakeholder expectations.

Risk Management 43

Risk Management Risk 2017 Technical Review 43

Wrike

NOVEMBER 7, 2018

Project Management Software & Tools. 64% of organizations say they frequently conduct risk management. [6]. Lean & Test Driven Development (TDD) – 11%. Managing small, low-risk projects. Managing medium-size, moderate-risk projects. Managing medium-size, moderate-risk projects. Project Failure.

2015 60

2015 Technical Review Underperforming Technical Team Software Review 60

Scrum.org

SEPTEMBER 11, 2020

Nexus is Scrum.org's framework for scaled product/software delivery. The example below (from 2013 or so) shows one such structure. This way, there's no need to review all the work across teams, just the overall flow/bottlenecks and specific stalled items. Scaling Scrum w/ Nexus. The Nexus Framework - Scrum.org.

SCRUM 201

SCRUM 2008 2013 Software Review 201

Project Pulse Journal

MAY 20, 2024

By prioritizing clear and consistent communication, project managers can significantly reduce the risks associated with miscommunication and ensure that all stakeholders have the information they need to make informed decisions and take appropriate actions. Set Up Channels: Ensure all stakeholders can access the chosen communication channels.

Communications Management 52

Communications Management 2005 2008 Technical Review 52

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

International Institute for Learning

SEPTEMBER 20, 2022

The risk with larger teams is that they can be more vulnerable to poor communication, fragmentation, and free riding due to a lack of accountability [3]. Martine Haas and Mark Mortensen, “The Secrets of Great Teamwork”, Harvard Business Review, June 2016. This alone is a good reason to pay attention to the two-pizza rule [5].

Underperforming Technical Team 52

Underperforming Technical Team 2022 Technical Review 2002 52

Teamweek

JUNE 25, 2020

According to a 2013 Harvard Study , employees spend 41% of their time on unproductive work. Here’s a review from SoftwareAdvice that sums up the frustration that teams have Asana. This Asana review on G2 , describes how frustrating it is to navigate across Asana’s features. Ease of use. Today it’s even worse.

Underperforming Technical Team 97

Underperforming Technical Team Software Review Planning Development Team Review 97

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 risk is created when we have not accounted for this natural variances in our management plan for the project. An aleatory risk is expressed as a relation to a value.

2003 46

2003 2014 2015 2011 46

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. What factors lead to software project failure?” All for the want of a nail.

2014 45

2014 Aerospace 2011 2013 45

PM Times

APRIL 7, 2021

It will discuss why the Core IT Complexity model is a good approach for most IT organizations and why it is important to determine project complexity as an ongoing and integral part of the Change Management and Risk Management process. It can also indicate potential risks to existing projects. Introduction. Kiridena, S. & Sense, A.,

2016 52

2016 2014 PMO Software Review 52

MPUG

JULY 30, 2020

Please find below a transcription of the audio portion of Rich Murphy’s showcase session, Triskell Software for Enterprise Governance, being provided by MPUG for the convenience of our members. Kyle: Hello everyone, and welcome to today’s MPUG vendor showcase session, Triskell Software for Enterprise Governance.

Governance 52

Governance Government Software Review Software 52

MPUG

JULY 30, 2020

Please find below a transcription of the audio portion of Rich Murphy’s showcase session, Triskell Software for Enterprise Governance, being provided by MPUG for the convenience of our members. Kyle: Hello everyone, and welcome to today’s MPUG vendor showcase session, Triskell Software for Enterprise Governance.

Governance 52

Governance Government Software Review Software 52

International Institute for Learning

APRIL 17, 2020

When using translation/interpretation software, we are aware of the risk of incorrect translations. For all interactions: We reduce “loss of face” risks by clearly stating our aim of mutual understanding and the use of “less-than-perfect English” as the communication norm. A picture is worth a thousand words! About the Author .

2013 55

2013 Engineering Software Review Energy 55

Wrike

MARCH 14, 2019

As a result, they’re missing out on rapid, innovative cloud solutions to challenges like scalability, software updates, mobile connectivity, etc. Wrike has also just completed the ISO 27001:2013 certification from BSI (British Standards Institution). This feature will be available in 2H 2019. Raising the bar.

2013 61

2013 Certification 2017 2018 61

Stepping Into Project Management

JUNE 18, 2018

This is a Guest Post by Fred Wilson, who is an Agile & Software Consultant at Ntask. Due to some uncertainties - or shall we say project management myths - teams often miss out on implementing best practices and approaching their projects in a truly effective manner. For some people, it seems more efficient to just get on with it.

Underperforming Technical Team 40

Underperforming Technical Team 2013 Software Review Consulting 40

Wrike

JUNE 3, 2021

All ticket-related information and records are stored in the ticketing software and can be used for upcoming process improvements and data analysis or to support team performance reviews. There’s no point in introducing new software if your team cannot measure the results. What are the benefits of IT ticketing software?

Technical Review 36

Technical Review Software Review Underperforming Technical Team Software 36

Digite

JUNE 13, 2018

Anderson best articulated its application to software development, in 2013, in the foundational book Kanban: Successful Evolutionary Change for Your Technology Business, and its adoption hasn’t been as universal as Scrum’s during the early days of Agile software development. You have permission to be different.

Agile 110

Agile Technical Review Cadence Software Review 110

MPUG

NOVEMBER 18, 2021

mpp) are proprietary, so there is compatibility issues if you open a project in another workstation that does not contain the software. SharePoint Designer 2013 needs to be used to build custom lifecycle workflows, it is clunky, out of date and not intuitive and normally requires a 3rd party to develop the workflows.

Underperforming Technical Team 52

Underperforming Technical Team 2019 2013 Technical Review 52

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

LiquidPlanner

NOVEMBER 2, 2017

He brings in PM experts to talk about a wide variety of topics, everything from how to become a PM to managing unknown risks. Hosted by Peter Taylor, this podcast began in 2013 after he published his best-selling book by the same name. For project professionals working in tech and software, Scrum certifications are an asset.

Technical Review 113

Technical Review 2018 Underperforming Technical Team Certification 113

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

JANUARY 22, 2017

Barry Boehm's work in “Software Engineering Economics”. This is due to many reasons. Aleatory and Epistemic uncertainties, which create the risk to the success of the project. Other uncertainties that create risk include: Unrealistic performance expectation with missing Measures of Effectiveness and Measures of Performance.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 17, 2017

Barry Boehm's work in “Software Engineering Economics”. This is due to many reasons. Aleatory and Epistemic uncertainties, which create the risk to the success of the project. Other uncertainties that create risk include: Unrealistic performance expectation with missing Measures of Effectiveness and Measures of Performance.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

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. Laird and M. 37–48, 2007. .

2007 42

2007 2012 2006 2008 42

Herding Cats

FEBRUARY 4, 2017

Barry Boehm's work in “Software Engineering Economics”. This is due to many reasons. Aleatory and Epistemic uncertainties, which create the risk to the success of the project. Other uncertainties that create risk include: Unrealistic performance expectation with missing Measures of Effectiveness and Measures of Performance.

Technical Review 28

Technical Review Estimate 2005 Software Review 28

Herding Cats

SEPTEMBER 19, 2018

Monte Carlo simulation on projects examines all paths through the network of activities or all possible states of the project for the duration, cost, and risk that create impacts on duration and cost. Flight software is always an issue where we work, so those ranges are wider even more. Statistics don't apply to single events.

Technical Review 43

Technical Review 2010 Estimate Software Review 43

Project Management Hacks

AUGUST 4, 2016

In 2013 , the company delivered 1.5 Through many discussions with my husband – who works in software development – I discovered an interest in the technology field. I led an effort to develop a risk-based software development process. Read Leigh Espy’s book review of “ The Obstacle is the Way.”. FedEx Profile.

2013 28

2013 2003 Technical Review 2010 28

MPUG

APRIL 29, 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 technical category and the MPUG activity code for claiming this session is on the screen now.

Estimate 52

Estimate Software Review Risk Management Risk 52

Herding Cats

JUNE 21, 2016

Here's another trail being ridden by our son at Nationals in 2013. Stability is a relative term, depending on speed, terrain, skill, risk taking tolerance, experience, technical equipment, and other intangible factors. The notion of Control is missed used in software development projects. What's coming due? A big drop.

Controlling 42

Controlling Technical Review Estimate 2013 42

MPUG

JULY 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. The MPUG activity code for claiming this session is on the screen. So for example, let’s say I click on this task here called risk management, right?

Initiating 52

Initiating Software Review Application Development Risk Management 52

MPUG

DECEMBER 15, 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 3/4 of a PMI PDU in the strategic category, and the code to claim that is on the screen now. This has a lot to do with risk.

Innovation 40

Innovation PMO Underperforming Technical Team Technical Review 40