Epicflow Blog

MAY 20, 2019

The movement aims at increasing productivity in the domain of software development by promoting management agility. The #NoEstimates movement originated in 2012 , when Woody Zuill , an Agile guide and coach, started a Twitter discussion with members of the software development world using the #NoEstimates hashtag.

2019 68

2019 Underperforming Technical Team Software Developers Software Development 68

Planio

FEBRUARY 17, 2019

So you want a software engineering job at Facebook/Apple/Amazon/Google/Netflix? It’s every software engineer’s dream to work with one of the top technical teams in the world. Step 1: Are you ready to apply for a top software engineering job? Self-taught vs. school: Do top tech teams really care? Get in line.

Software Engineering 155

Software Engineering Technical Review Engineering Software Review 155

Teamweek

JUNE 25, 2020

And, while Asana is a great tool for micro-managing work, more creative teams are looking for Asana alternatives that allow better freedom at work. In this article, you’ll learn about 30 alternatives to Asana that are easy to use and help creative teams collaborate better. 3 Project Management Features That Matter To Creative Teams.

Underperforming Technical Team 97

Underperforming Technical Team Software Review Planning Development Team Review 97

Leading Agile

JUNE 18, 2018

I remember joining a team in the late 1970s that supported an application used worldwide by a large corporation. The team resolved to drive that number down. It’s amusing until one reflects on the potential consequences when a large proportion of software we depend on for everyday life is of this quality.

Software Review 101

Software Review Underperforming Technical Team Technical Review Artificial Inteligence 101

Leading Agile

JUNE 27, 2018

A multidisciplinary team of professors was assembled, headed by a theoretical physicist, and two weeks of intensive on-site investigation took place. The scholars then returned to the university, notebooks crammed with data, where the task of writing the report was left to the team leader. You probably spotted my error immediately.

Software Review 121

Software Review Technical Review Underperforming Technical Team 2007 121

Wrike

NOVEMBER 7, 2018

Keys to Project Success: 48% say the team’s technical skills. 26% say effective team communication. Lean & Test Driven Development (TDD) – 11%. Feature Development Driven – 9%. Dynamic Systems Development Method – 3%. Poor visibility & resource management : 31%. Poor purchasing processes: 23%.

2015 60

2015 Technical Review Underperforming Technical Team Software Review 60

Herding Cats

JUNE 12, 2018

This is simply good process development and management. This, of course, is simply poor process improvement and a fallacy since without the root cause the symptom cannot be fixed and will return. At a minimum, at the end of every week, a Scrum team assess physical percent complete at the end of the Sprint. Standish Number.

Underperforming Technical Team 40

Underperforming Technical Team Software Engineering Estimate Software Developers 40

Wrike

MAY 23, 2023

I joined the team as a QAA engineer in 2010, the first employee in this role. Over the past 12 or so years, we have built a super team of brilliant QAA engineers. The team made a complete audit of everything that could be checked and improved by at least 1%. But he was wrong — Team Sky won in just three. Hello, everyone!

Engineering 36

Engineering Underperforming Technical Team Controlling Software Review 36

Herding Cats

APRIL 16, 2019

Product Development (#ProdDev). Agile Software Development (#ASD). The following material comes from conferences, workshop, materials developed for clients. But each method needs to be based on 5 Immutable principles to be successful, no matter the domain or context, PMI Spring Seminar , 2012, Austin TX.

Technical Review 42

Technical Review Performance Measurement 2003 Underperforming Technical Team 42

Herding Cats

JUNE 12, 2018

This is simply good process development and business management. This, of course, is simply poor process improvement and a fallacy, since without the root cause the symptom cannot be fixed and will return. The notion of waterfall development on slide 9 as actually prohibited in our domain. Have you done a Root Cause Analysis?

Underperforming Technical Team 28

Underperforming Technical Team Software Engineering Estimate Development Team Review 28

Herding Cats

JUNE 19, 2017

The Cone of Uncertainty is a framing assumption used to model the needed reduction in some parameter of interest in domains ranging from software development to hurricane forecasting. This is a common problem in low maturity development organizations. Thesis, University of Southern California, August 2012.

Technical Review 35

Technical Review Performance Measurement Underperforming Technical Team Estimate 35

MPUG

JUNE 20, 2022

If you manage a resource-constrained project, you will often artificially delay activities as to not overwork (or burn out) your team members. Examples are software development, new product development, pharmaceutical clinical studies, telecommunication, research and development, education, and government projects.

2010 52

2010 Aerospace Underperforming Technical Team Government 52

Workzone

AUGUST 4, 2021

This list of alternatives for Asana the project management software will help you identify which project management software you should be using. They are widely used for basic task and project management, but oftentimes busy teams with growing workloads need more. Better visibility to your team’s work. Asana Pros.

2021 26

2021 Software Review Technical Review Underperforming Technical Team 26

BeeWits

JULY 3, 2018

The “price” of choosing a service which does not get adopted by your team can be very high. Besides the training costs and onboarding into the service, if the solution does not get traction, you’re going to be facing some very tough situations with your management team. Team and Project Management.

Software Review 29

Software Review Underperforming Technical Team Budget Defining 29

Scrum.org

DECEMBER 8, 2023

But, not all debt is bad!” 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. From 2005 (first beta) until 2012 they worked, successfully delivering a new version every 2 years. NKDAgility can help!

Underperforming Technical Team 202

Underperforming Technical Team Risk 2012 Cadence 202

Herding Cats

NOVEMBER 7, 2016

And the same process is applied to the Scrum development processes on those projects. . 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). Springer International Publishing, 2016.

Estimate 64

Estimate 2005 2006 2013 64

Herding Cats

MAY 10, 2019

Risk Management is essential for development and production programs. This blog page is dedicated to the resources used to assess risks, their impacts, and handling strategies for software-intensive systems using traditional and agile development methods. Effective Risk Management 2 nd Edition , Edmund Conrow, AIAA, 2003.

Risk Management 38

Risk Management Risk Technical Review 2002 38

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. Chakraborty and K.

Estimate 40

Estimate Software Review Software 2012 40

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. 255, April 2010. 920, November 2004. 1, March 2014.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

OCTOBER 16, 2018

It's the Planning and Controls processes working together with the Technical Development processes that provide the ability to forecast what should happen in the future if we keep going like we are going now using a Model of the possible future outcomes. This is the desired outcomes model. So the open question is. Which comes first?

Aerospace 41

Aerospace Engineering 2012 2014 41

PM That Works

MAY 23, 2020

della solutions, technology consulting and software development practice, he remains active in each one of these companies provide strategic guidance and support. I've had mentors who have been instrumental in my personal and professional development and without mentors, who knows where I would be in my life. What does matter?

Underperforming Technical Team 40

Underperforming Technical Team Leadership Consulting Government 40