The IIL Blog

AUGUST 8, 2023

2005) Work & Stress. The focus was on burnout in people who were working. Since that time, models have been created to measure levels of burnout [Maslach and Jackson (1981), and Kristensen et al. 2014), and Jugdev et al., There are more options available for correcting project work-related issues. DOI: 10.1108/IJMPB-02-2017-0020.

Underperforming Technical Team 78

Underperforming Technical Team 2004 2005 2006 78

Scrum.org

JULY 1, 2020

Its been 25 (1995) years since the first Scrum project and the average internet speed was 56kbps! Here is a list of the important dates since then and the average internet speed in brackets: 1995 – First Scrum project (56kbps). 2005 – First HD video (980kbps). 2000 – First video Conferencing (280kbps). 2020 – COVID (26Mbps).

Technical Review 227

Technical Review 2005 2020 2001 227

Scrum.org

JANUARY 28, 2022

Als Gibson Biddle (ehemaliger VP) 2005 zu Netflix kam, kündigten etwa 4,5 % ihr monatliches Abo. Scrum Master sind eine Möglichkeit dafür und Professional Coaching eine andere. Wie man mit den Agilen Werten führt, ist eines der vielen interessanten Themen, die in meinen Professional Scrum Trainings behandelt werden. .

Agile 91

Agile 2005 2015 2019 91

nTask

SEPTEMBER 27, 2019

And since 2005, each year the remote workforce has increased by 10% which makes it 140% in 2019, which is huge. Conduct Daily Scrum Meetings. The team leader can use project management tools to conduct efficient scrum meetings. The team leader can use project management tools to conduct efficient scrum meetings.

Underperforming Technical Team 92

Underperforming Technical Team Agile Technical Review 2005 92

Herding Cats

DECEMBER 16, 2017

Estimating Software-Intensive Systems: Projects, Products, and Processes , Richard Stutzke, Addison-Wesley, 2005. Practices for Scaling Lean & Agile Development: Large, Multisite, and Offshore Product Development with Large-Scale Scrum , Craig Larman and Bas Vodde, Addison Wesley, 2010. Prentice Hall, 2000.

Software Developers 46

Software Developers Software Development Estimate 2006 46

Scrum.org

AUGUST 28, 2020

like choosing for Scrum?—?they These norms range from very basic ones, like attending a Daily Scrum every day, to abstract ones like “work together towards a shared goal instead of working on your own tasks” and “delivery small, working bits of product frequently instead of huge chunks occasionally”. Why Is Change Hard? Pittinger, D.

2012 156

2012 2006 2011 Influencer 156

Digite

AUGUST 14, 2017

While Scrum is probably most prevalent in IT, Kanban and Lean are significant too. Scrum provides a structured model, making it useful for transitioning from traditional development structures and methods. Where workflow is crucial as in service delivery, Scrum may be constraining but has value in its routines.

Agile 94

Agile Lean 2005 Risk Management 94

Gunther Verheyen

MARCH 2, 2018

Try benefiting from Scrum in a “Yes, but…” environment, where the primary response is to raise concerns and hindrances, where the conversation is all about obstacles, and that what cannot be done. Imagine adopting Scrum from a “Yes, and” stance. Over the past decade Scrum did more than just gain a critical mass to build on.

2005 67

2005 2006 2001 SCRUM 67

Scrum.org

FEBRUARY 3, 2020

Their paper provides useful insights into why the Scrum Framework might be so effective when it comes to managing complex work. Their article inspired me to apply the same insights to Scrum and to extend it with my own. Cognitive paradigms, applied to Scrum / Agile. When a Scrum Team starts work on a Sprint (e.g.

2002 211

2002 SCRUM 2007 2003 211

Herding Cats

MAY 10, 2019

Kadane, and Anthony O’Hagan, Carnegie Mellon University, Statistics & Data Science, January 5, 2005. The Rise and Evolution of the Chief Risk Officer: Enterprise Risk Management at Hydro One,” Tom Aabo, John Fraser, and Betty Simkins, Journal of Applied Corporate Finance , Volume 17, Number 3, Summer 2005. Elsevier, 2005.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

MAY 11, 2019

Kadane, and Anthony O’Hagan, Carnegie Mellon University, Statistics & Data Science, January 5, 2005. The Rise and Evolution of the Chief Risk Officer: Enterprise Risk Management at Hydro One,” Tom Aabo, John Fraser, and Betty Simkins, Journal of Applied Corporate Finance , Volume 17, Number 3, Summer 2005. Elsevier, 2005.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Wrike

AUGUST 14, 2020

Anderson is often credited as being the first to implement Kanban in software development in 2005. Unlike other frameworks that promote their own unique roles (such as Scrum master ), Kanban emphasizes working with the roles your team already has. . How is Kanban methodology different from Scrum? Keep roles.

Software Review 36

Software Review Technical Review 2005 SCRUM 36

Scrum.org

JUNE 24, 2022

When people first look at the Scrum framework, they often see the roles and the events first. They see only the structure of Scrum; who wears the hats and when. But Scrum and the Agile methodologies it builds on are so much more. Scrum is a great example of a motivation framework. And that makes sense.

SCRUM 196

SCRUM 2002 2006 2007 196

Scrum.org

AUGUST 9, 2022

If you are a Product Owner or other Scrum Team member, you may use another opportunity to build. on what your Scrum Team delivered, look together at measures, at a goal and look into the future, too. 1 Patrick Lencioni, Overcoming the Five Dysfunction of a Team, 2005. You can check my articles and videos here. Sprint Reviews.

Technical Review 184

Technical Review Cadence 2005 Initiating 184

Herding Cats

MARCH 30, 2019

Agile software development is more than frameworks such as Scrum, Extreme Programming or Feature-Driven Development (FDD). None of the MOE's MOP's KPP's, KSA's and TPM's are addressed in Scrum, XP, or similar Agile Software Development methods. Agile is the ability to create and respond to change. 81-100, 2009. [4] 5] "What is Agile?",

Software Developers 39

Software Developers Software Development Agile Software 39

Herding Cats

APRIL 4, 2019

Cooper, Stephen Grey, Geoffrey Raymond, and Phil Walker, John Wiley & Sons, 2005. Agile Risk Management and Scrum , Alan Moran, Institute for Agile Risk Management, 2014. Project Risk Management Guidelines, Managing Risk in Large Projects and Complex Procurements , Dale F. The Silver Lining of Project Uncertainties, Thomas G.

Risk Management 43

Risk Management Risk 2003 2011 43

Herding Cats

MAY 7, 2019

Flint, School of Management, Working Paper Series, September 2005.”. Eva Regnier, DRMI Newsletter, Defense Resources Management Institute, Naval Postgraduate School, Issue 12, April 8, 2005. Evaluating Software Project Prediction Systems,” Martin Sheppard, 11th IEEE International Software Metrics Symposium (METRICS 2005).

Estimate 40

Estimate Software Review Software 2012 40

Leading Agile

MARCH 11, 2020

And in those days, so if this was 2004, 2005, something in that kind of range, in those days, then, you know, for the most part, Agile was still maybe one team of six, or eight, or 10. I just don’t see as much of their work as I do the guys that are doing Scrum and LeSS and SAFe and things like that. – [Mike] Yeah, yeah.

Agile 103

Agile Fractional CTO CTO Hire Influencer 103

Herding Cats

NOVEMBER 7, 2016

And the same process is applied to the Scrum development processes on those projects. . When 90% Confidence Intervals are 50% Certain: On the Credibility of Credible Intervals,” Karl Halvor Teigen and Magne Jørgensen, Applied Cognitive Psychology Applied Cognitive Psychology, 19: 455–475 (2005). 400-407, 2009.

Estimate 64

Estimate 2006 2005 2013 64

Herding Cats

APRIL 16, 2019

RFETS was a nuclear bomb manufacturing plant, built in 1951, operating until 1989, and closed in 2005. Probabilistic Schedule and Cost Analysis , prepared for NNJ051R, NASA Crew Exploration Vehicle, 2005. Rocky Flats Environmental Technology Site (RFETS) was the marketing term for the 3rd worst toxic waste site on the planet.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Herding Cats

FEBRUARY 9, 2019

We were one of the first users of eXtreme Programming, long before Scrum was around and presented that early work in 2003, " Making Agile Development Work in a Government Contracting Environment, Measuring velocity with Earned Value." . It can be a complex as a scrum or scrums strategy map in SAFe 4.2 6, No 5, October 2014. [3]

Estimate 42

Estimate Technical Review Underperforming Technical Team Software Review 42