Scrum.org

SEPTEMBER 23, 2019

The first article of this series will address the Scrum Master engagement with the Development Team. So, for example, no engineers are mourning the demise of the hero-developer, who single-handedly saves the organization with beautifully crafted code while burning the midnight oil.). Scrum Master Engagement with the Development Team.

Development Team Review 134

Development Team Review SCRUM Software Review Technical Review 134

Scrum.org

FEBRUARY 3, 2020

A while ago, I received an interesting scientific article from Gunther Verheyen titled “Getting Things Done: The Science Behind Stress-Free Productivity” (Heylighen & Vidal, 2007). Their article inspired me to apply the same insights to Scrum and to extend it with my own. Why our brain is not built for software engineering.

2002 190

2002 SCRUM 2007 2003 190

nTask

MARCH 10, 2021

In 2002, Bill Wake published in his article the inconsistencies that arise from certain terms that are used within teams, including that if “done.”. It took until 2007 for the Definition of Done (DoD) to be a widespread full-fledged practice. This is of no fault due to the developer. Why do You Need a Definition of Done?

Software Review 78

Software Review Technical Review 2002 2007 78

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? Alternatively to the previous: I believe The IT Skeptic had an article about having two boards – one focused on the stakeholder epics, the other on the actual short-term tasks.

Development Team Review 154

Development Team Review Software Review Cadence Technical Review 154

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

Wrike

JANUARY 12, 2024

Jeff Kinney’s hit children’s book series, Diary of a Wimpy Kid , was first released in 2007 and is still rolling out installments each year. Feasibility analysis: Next, evaluate each idea for its feasibility — this means technical, financial, and market viability. Be creative and think outside the box!

Innovation 36

Innovation Process Technical Review Artificial Inteligence 36

Scrum.org

FEBRUARY 25, 2020

When I started using Scrum as a software developer back in 2007 I noticed that this new ways of working really worked, then I decided to learn more about and I became a Scrum Master in 2012 and in 2015 I started to teach Scrum, overcoming my fear of public speaking. I will explain the peer review at the end of this article.

2017 172

2017 2018 2016 SCRUM 172

Herding Cats

MAY 10, 2019

Information about key project cost, (technical) performance, and schedule attributes is often uncertain or unknown until late in the program. 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.

Risk Management 38

Risk Management Risk Technical Review 2002 38

TrustRadius Project Management

OCTOBER 28, 2019

He has written multiple detailed reviews for collaboration, video editing, and document management products – including MS SharePoint. Starting off as a call center representative in 2007, Daniel worked his way up to site supervisor, learning what works (and doesn’t) for a nationwide network of agents.

Technical Review 48

Technical Review Software Review 2007 Healthcare 48

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. Raz and E.

Risk Management 35

Risk Management Risk Technical Review 2002 35

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

Online PM Courses

NOVEMBER 11, 2018

And, whether you are an IT Project Manager or not, you may find yourself delivering IT in the form of hardware, infrastructure, software, or service processes as a part of your projects. Therefore, in this feature article, we’ll explore what ITSM and ITIL are. And one of those services is Information Technology: IT.

Technical Review 71

Technical Review 2011 2007 Prince2 71

Online PM Courses

OCTOBER 14, 2018

If you want to follow project management conversations on Twitter… Or if you want to keep up with the latest articles, or products… #PMOT is a good tag to follow. This article is going to be different to most of ours. Software Vendors. Ron’s Article at Online PM Courses: Are You a New Project Manager?

PMO 72

PMO Technical Review Underperforming Technical Team PMI 72

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

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

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. 12, 2008.

2003 46

2003 2014 2015 2011 46

MPUG

NOVEMBER 11, 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 1 PMI PDU in the technical category. The MPUG activity code for claiming that with PMI is on the screen now.

Software Review 52

Software Review Lean SCRUM PMI 52

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

MPUG

OCTOBER 24, 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 this session is eligible for one PMI, PDU in the Technical category. We’re going to take a quick review of Agile options and approaches. There we go.

Agile 40

Agile Technical Review Software Review Underperforming Technical Team 40

MPUG

DECEMBER 4, 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. There may be exclusions, such as those steps included in product demonstrations.

Software Review 52

Software Review Initiating Software Closing 52

MPUG

NOVEMBER 14, 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. PMI PDU use in the technical category. And you get asked a question to enter a code. And this code is 18 11 17. In 2007, it became in color.

2013 40

2013 Finance 2007 Software Review 40

MPUG

JULY 17, 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. This session is eligible for one PMI PEU in the technical category. Jim is the president of Critical Tools, the makers of WBS Schedule Pro Software. Kyle: Great.

Software Review 52

Software Review 2014 Planning Technical Review 52

Knowledgeline

OCTOBER 3, 2006

Given that Lexis has the Applied Discovery offering, it shouldnt be long before Thomson/West look to also acquire a company that provide an online review tool for e-discovery. SharePoint 2007 is full of surprises – let's talk. Practice Enhancement The Best KM Software Yet? Knowledge Management v.

2006 40

2006 2007 Technical Review Software Review 40

MPUG

JULY 1, 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. PMI PDUs in the technical category and the MPUG activity code for claiming the session was on the screen now. My name is Kyle and I’ll be the moderator today.

Risk Management 52

Risk Management Risk 2016 Underperforming Technical Team 52