Scrum.org

JULY 14, 2021

This post is a non-technical version of an academic paper about Scrum teams that I wrote with Daniel Russo. Daniel is a Professor at the University of Aalborg and is specialized in empirical software engineering. I am an organizational psychologist and Scrum practitioner with a love for survey development and statistics.

SCRUM 241

SCRUM Influencer Technical Review Software Review 241

Scrum.org

OCTOBER 19, 2022

Is it really that important that they are autonomous, able to release frequently, interact closely with stakeholders and spend all that time on continuous improvement? However, the sheer effort involved is so gargantuan that this is close to impossible. So we went to Google Scholar and searched for review articles.

Agile 205

Agile 2010 2013 2008 205

Leading Agile

JUNE 27, 2018

” I was reminded of the old joke by a recent article by John Regehr, Professor of Computer Science at the University of Utah, entitled “Closing the Loop: The Importance of External Engagement in Computer Science Research.” ” Feedback Loop Between Academia and the Field. They said, well, no one has published it before.

Software Review 88

Software Review Technical Review Underperforming Technical Team 2007 88

Scrum.org

FEBRUARY 4, 2022

There are dozens of high-quality academic works to draw from, there are dozens of academic journals dedicated to (agile) software development (ASD) and change management. software estimation”), and then select “review articles” under “type” on the left. So where do you find it?

Agile 189

Agile Software Review Underperforming Technical Team Technical Review 189

PM Basics

JULY 1, 2020

But you don’t have a relevant degree, experience, or technical background…. For sure, the easiest way to become a software project manager is by getting a promotion inside an IT company. Technical Skill of an IT Project Manager. Combine it with challenges of cutting edge technologies. Yes, it is. Table of Content.

Software Review 98

Software Review Technical Review Underperforming Technical Team Leadership 98

PM Basics

MAY 16, 2022

But you don’t have a relevant degree, experience, or technical background…. Below you’ll find a full guide on how to become a software PM. TL;DR: The steps to becoming a software project manager. Develop technical proficiency. Technical Skills of an IT Project Manager. Yes, it is! Where Should I Start?

Software Review 59

Software Review Technical Review Software Leadership 59

Scrum.org

JANUARY 25, 2021

The reasons for this are apparent, with software eating the world and the pace of innovation accelerating as the market-entry barriers of the technology sector are continuously lowered. Current tech trends — accelerated by the pandemic — threaten the very existence of many legacy organizations. Agile Clinic. Agile Coaching.

SCRUM 192

SCRUM Technical Review Engineering Lean 192

Binfire

AUGUST 28, 2019

In the project management and software development fields, Agile project management principles realized and practiced. . The Agile Manifesto for Agile Software Development lists 12 core principles for Agile project management. Promote close day-to-day collaboration between business managers and developers.

Agile 60

Agile Technical Review Sustainability Software Review 60

Binfire

AUGUST 27, 2017

The Agile project management methodology has been used by software engineers and IT professionals for the past sixteen years. In the late twenty century, many software engineering researchers in academia were studying the disturbing fact that most software and IT projects finish late or fail to finish at all.

Agile 97

Agile Technical Review Software Review Development Team Review 97

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. México, 1 al 3 de Febrero de 2006. De Meyer, C. Loch, and M.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

MAY 11, 2019

Let's start with a critical understanding of the purpose of managing risk on software development projects. 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.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Binfire

APRIL 7, 2017

The Agile project management methodology has been used in the software development and IT industry for the past sixteen years, but recently it has gained wide acceptance by many number of industries and organizations. In 2001 a group of software engineers and scientists in IT industry got together and wrote Agile Manifesto.

Agile 100

Agile Technical Review Software Review Development Team Review 100

Teamweek

OCTOBER 20, 2022

You probably already know—Agile isn’t just for software developers anymore. After all, Agile projects deliver proven value in software projects: Higher profit More meaningful projects and client relationships Greater productivity Clearer communication. Takes place “behind closed doors” and is closely based on original specs.

Agile 52

Agile Technical Review SCRUM Executing 52

Herding Cats

MARCH 11, 2017

Accuracy - how close is the estimate to the actual value? So in the end, if we are to make a decision in the presence of uncertainty, we MUST make estimates to develop a reliable shipping date while producing an accurate and precise estimate of the cost, schedule, and technical performance of the product shipped on that date.

2003 46

2003 2014 2015 2011 46

Leading Agile

JUNE 18, 2018

Self-organize technical teams on a peer model rather than the Chief Programmer model , to help ensure common understanding and knowledge across the team and to increase the team’s bus number. The level of technical expertise required to use this kind of automation far exceeds that necessary for automating conventional functional checks.

Software Review 81

Software Review Underperforming Technical Team Technical Review Artificial Inteligence 81

Herding Cats

JANUARY 13, 2017

Barry Boehm's work in “Software Engineering Economics”. Estimates of cost, schedule, technical performance on the left have a lower probability of being precise and accurate than estimates on the right. This is due to many reasons, one is levels of uncertainty early in the project. Economics of Software Development.

Technical Review 28

Technical Review Software Review Estimate Software Engineering 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. The Cone of Uncertainty as a Technical Performance Measure. Closed Loop Stochastic Adaptive control in the presence of Evolving Uncertainty.

Technical Review 35

Technical Review Performance Measurement Underperforming Technical Team Estimate 35

Leading Agile

AUGUST 20, 2018

An unattended software delivery pipeline frees technical staff to spend more time on value-add activities rather than tediously performing repetitive tasks by hand, such as. Reviewing code by eyeballing it to ensure compliance with coding standards. Two closely related conceptual errors appear to be quite common.

Software Review 55

Software Review Software Technical Review Development Team Review 55

Herding Cats

JANUARY 14, 2017

Barry Boehm's work in “Software Engineering Economics”. The Cone is a project management framework describing the uncertainty aspects of estimates or any other project attribute (in this post, cost, schedule, and technical performance parameters). This is due to many reasons, one is levels of uncertainty early in the project.

Technical Review 28

Technical Review Software Review Underperforming Technical Team Risk Management 28

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

MPUG

MAY 14, 2021

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 1 PMI PDU in the technical category and the activity for claiming that with PMI is on the screen now. Fletcher Hearns: Great.

Performance Measurement 59

Performance Measurement Underperforming Technical Team Software Engineering Engineering 59

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. This is a closed loop system optimization process applied to all the projects we work. And money in the bank is what software development is about. Is this normal?

Estimate 42

Estimate Technical Review Underperforming Technical Team Software Review 42

MPUG

MAY 6, 2021

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 code for claiming that with PMI is on the screen now. Technology is wonderful.

Performance Measurement 52

Performance Measurement Underperforming Technical Team Software Review Governance 52