Project Management Essentials

AUGUST 3, 2019

In 2013, Mike Cohn coined the term scrum smells to describe the signs that a scrum team is in trouble. Scrum masters, agile coaches, and even team members can improve their teams’ performance by spotting these warning signs early and taking corrective actions. Who is the Scrum Master or Product Owner?

Underperforming Technical Team 40

Underperforming Technical Team Agile Technical Review Software Review 40

Digite

JUNE 13, 2018

Compared to Scrum, Kanban is a young work-management method. 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.

Agile 110

Agile Technical Review Cadence Software Review 110

Herding Cats

MARCH 11, 2017

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. Eggstaff, Thomas A.

2003 46

2003 2014 2015 2011 46

Scrum.org

DECEMBER 23, 2021

Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. So I was pleasantly surprised when Carsten Grønbejrg Lützen pointed at a peer-reviewed academic paper by Michele Tufano and his colleagues (2015), called “When and Why Your Code Starts To Smell Bad”. Technical Debt and Code Smells.

Software Review 182

Software Review Technical Review Underperforming Technical Team 2015 182

Online PM Courses

NOVEMBER 4, 2018

It is all too easy to settle for excellent technical skills and think ‘that’s it. A fully capable project manager needs a wide range of personal and professional skills outside of the realms of their technical project management competence. Take a look at our reviews of the last three ( 2016 , 2017 , 2018 ).

PMI 72

PMI Technical Review Certification Leadership 72

nTask

AUGUST 22, 2019

“Scrum” is a phenomenal subject – i.e. if you are familiar with it. As an Agile project manager, I have seen my fair share of so-called “Scrum Masters” and “Agile Experts” claiming to be masters of their craft. The truth, however, is that they don’t know a lot of things about Scrum and Agile. Introduction – Why Scrum?

SCRUM 132

SCRUM Technical Review Development Team Review Software Review 132

Scrum.org

AUGUST 3, 2020

What the Scrum Guide says: “Cross-functional teams have all competencies needed to accomplish the work without depending on others not part of the team. The team model in Scrum is designed to optimize flexibility, creativity, and productivity.” - K. Sutherland, Scrum Guide, 2013. Short Term: Scrum of Scrums.

Underperforming Technical Team 238

Underperforming Technical Team Technical Review Software Review Development Team Review 238

Rebel’s Guide to PM

OCTOBER 28, 2022

A survey showed that teams using Slack had: 32% less email 23% fewer meetings 24% of features (in technical teams) delivered on time 27% less time required for software testing 10% improvement in employee satisfaction. For most projects, you are going to need something else as well to create your Gantt chart or Scrum board, for example.

Technical Review 400

Technical Review Software Review 2013 Software 400

Scrum.org

APRIL 7, 2022

Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. For example, Mcgrath's (1991) Time-Interaction-Performance (TIP) Theory simply identifies four modes — inception, technical problem solving, conflict resolution, and execution — that teams generally go through, but in different and complex orders.

Underperforming Technical Team 167

Underperforming Technical Team 2007 2006 2009 167

Wrike

NOVEMBER 7, 2018

Keys to Project Success: 48% say the team’s technical skills. Most Popular Agile Tools and Processes: Scrum – 43%. Lean & Test Driven Development (TDD) – 11%. Technology. Shifting requirements/technical complexity. The number of firms with a PPM process in place grew from 64% in 2003 to 71% in 2013. [13].

2015 60

2015 Technical Review Underperforming Technical Team Software Review 60

Herding Cats

APRIL 16, 2019

Business, Technical, Systems, Risk, and Project Management Briefings and Presentations. Technical Performance Measures (#TPM). Cost, Schedule, and Technical Performance Management (#CSTPM). Business, Technical, Systems, Risk, and Project Management. Table of Contents (Click the Name to go to Section).

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Rebel’s Guide to PM

JUNE 24, 2019

A 2017 survey showed that teams using Slack had: 32% less email 23% fewer meetings 24% of features (in technical teams) delivered on time 27% less time required for software testing 10% improvement in employee satisfaction. For most projects, you are going to need something else as well to create your Gantt chart or Scrum board, for example.

Software Review 223

Software Review Technical Review 2013 2017 223

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

Workzone

AUGUST 4, 2021

As of April 1, 2021, Workzone is ranked as the #1 Asana Alternative in all ranking categories: Overall, Functionality, Ease of Use, Value for Money, and Customer Support by user reviews at Capterra , Software Advice , and GetApp by user reviews. 1 Asana Alternative Review: Workzone. Ready to see the #1 rated Asana alternative?

2021 26

2021 Software Review Technical Review Underperforming Technical Team 26

Herding Cats

MAY 7, 2019

International Journal of Technology in Education and Science (IJTES), 3(2), 72-84. What the Data Say About IT project Risk in the Public Sector,” Alexander Budzier and Bent Flyvbjerg, in Commonwealth Governance Handbook, 2012/2013: Democracy, development, and Public Administration, Commonwealth Secretariat, December 2012. 1809, 2013.

Estimate 40

Estimate Software Review Software 2012 40

MPUG

JULY 30, 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: The session is eligible for 1 PM@PDU in the technical category, and the MPUG activity code for claiming the session is on the screen. So, we do have a Gantt system.

Governance 52

Governance Government Software Review Software 52

MPUG

JULY 30, 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: The session is eligible for 1 PM@PDU in the technical category, and the MPUG activity code for claiming the session is on the screen. So, we do have a Gantt system.

Governance 52

Governance Government Software Review Software 52

Herding Cats

NOVEMBER 7, 2016

And the same process is applied to the Scrum development processes on those projects. . Review on Traditional and Agile Cost Estimation Success Factor in Software Development Project,” Zulkefli Mansor, Saadiah Yahya, Noor Habibah Hj Arshad, International Journal on New Computer Architectures and Their Applications (IJNCAA) 1(3): 942–952.

Estimate 64

Estimate 2006 2005 2013 64

International Institute for Learning

SEPTEMBER 20, 2022

Managing a team is definitely something really difficult because in addition, for instance, to the technical complexity of the topic, there is the challenge to coordinate people with different personalities, knowledge, background and even culture with the purpose of making the team work in an efficient way. Schwaber, K. Hackman, J.

Underperforming Technical Team 52

Underperforming Technical Team 2022 Technical Review 2002 52

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. Thomopoulos, Springer, 2013. [10] Lecture Eight: Decision Making. [9]

Technical Review 43

Technical Review 2010 Estimate Software Review 43