Scrum.org

JUNE 5, 2019

This is what another Scrum Master told me after we took turns during a recent training to share a success story about a Development Team. Agile software development started with developers. These days, it seems to be more about Scrum Masters, Agile Coaches, Product Owners, and other “process roles”. We worked with .NET

SCRUM 139

SCRUM 2002 2003 2001 139

Project Pulse Journal

APRIL 2, 2024

Enhanced decision-making, risk mitigation, resource optimization, and stakeholder satisfaction that propel your projects to new heights of success and recognition. Regulatory requirements are not optional; alignment with them should always be a vital part of your risk management. The result?

Influencer 40

Influencer Governance Government Technical Review 40

Herding Cats

MARCH 11, 2017

The risk is created when we have not accounted for this natural variances in our management plan for the project. Dealing with Aleatory (irreducible) uncertainty and the resulting risk requires we have margin. An aleatory risk is expressed as a relation to a value. An aleatory risk is expressed as a relation to a value.

2003 46

2003 2014 2015 2011 46

Herding Cats

DECEMBER 16, 2017

Here are some resources that will provide guidance to produce credible software development estimates, in both traditional and agile domains. While some have publication dates that may seem old, the principles in these books are immutable, even for agile projects. Agile Estimating and Planning , Mike Cohn, Prentice Hall, 2006.

Software Developers 46

Software Developers Software Development Estimate 2006 46

ProProfs Project Management

JANUARY 15, 2021

David even built on the methodology to define the kanban method and released a book in 2010 called “Kanban: Successfully Evolutionary Change for your Technology Business”. To become agile, it is important to implement the feedback loops. Q1: Is Kanban better than scrum? The Scrum board is more methodical. Happy reading!

Software Review 81

Software Review Technical Review 2004 SCRUM 81

Scrum.org

FEBRUARY 16, 2021

TL; DR: How to Make Agile Work in Fast-Growing Startups. For years, I worked in several Berlin-based, fast-growing startups in my capacity as Scrum Master, agile coach, and Product Owner. These are my lessons learned on making ‘agile’ — including Scrum as a framework — work in a fast-growing startup.

Agile 132

Agile Technical Review Software Review Underperforming Technical Team 132

Leading Agile

MARCH 11, 2020

Agile Unplugged is your chance to explore LeadingAgile’s freshest ideas, mental models, frameworks, and solutions with the people that are actually doing the work of leading large-scale Agile Transformation, out in the field. So, I had never, I’d like heard of Agile, but like, I had no experience with Agile.

Agile 104

Agile Fractional CTO CTO Hire Influencer 104

Leading Agile

OCTOBER 3, 2023

And that’s typically how I think about a lot of the talks that I give because everything in the agile communities about doing it and learning from it and sharing with people and getting feedback and figuring out how to do it better and that kind of stuff. What is an Agile Culture So, here’s the end of the talk.

Governance 62

Governance Government SCRUM Agile 62

Herding Cats

APRIL 4, 2019

In a recent exchange in social media, it was clear the notion of risk and the sources of risk, the consequences or risks and managing in the presence of risk was in very unclear, when it was conjectured , we can simply slice the work into small bits and REDUCE risk. . This is good, but it doesn't reduce risk.

Risk Management 43

Risk Management Risk 2003 2011 43

Scrum.org

APRIL 7, 2022

Recently, the concept of “fluid teams”, “dynamic reteaming” or “ad-hoc teaming” has gained traction in the Agile community. Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. This corresponds with research on autonomous teams, as well as principles of Agile software development.

Underperforming Technical Team 167

Underperforming Technical Team 2007 2006 2009 167

MPUG

JULY 1, 2020

This is project 2016 I’m using for this demonstration, and I think that this will go all the way back to like project 2010 or even earlier than that. Use them that’s your own risk and in particular, watch out for that checkbox that we saw on the tasks calendar where the resources calendars can be ignored. Here we go.

Risk Management 52

Risk Management Risk 2016 Underperforming Technical Team 52

The IIL Blog

JUNE 28, 2018

Innovation requires: An acceptance of significant risk, more so than in traditional project management. The future will be flexible project management models such as those used in Agile and Scrum projects. We have learned from Agile and Scrum that flexible project management approaches are necessary for many projects.

Innovation 106

Innovation 2010 2008 2011 106

MPUG

OCTOBER 9, 2019

Please find below a transcription of the audio portion of Tim Runcie’s Agile Series Part 1 webinar being provided by MPUG for the convenience of our members. Kyle: Hello everyone and welcome to today’s MPUG training series, part one, Understanding and Incorporating Agile Project Management. It’s not all or nothing.

Agile 40

Agile Technical Review Lean Underperforming Technical Team 40

nTask

NOVEMBER 23, 2018

Introduced in 2006, with a major redesign in 2010, the platform serves as a single systematic and flexible solution for all the task management needs of a team. Issues and risks management. Issues and Risks management to tackle their occurrence likelihood. Kanban and Scrum boards. Customizable Scrum boards.

2019 111

2019 2006 2010 Software Review 111

MPUG

OCTOBER 16, 2019

Please find below a transcription of the audio portion of Tim Runcie’s Agile Series Part 2 webinar being provided by MPUG for the convenience of our members. Kyle: Hello everyone and welcome to part two of MPUG’s Agile training series. Hence Agile, right? My name is Kyle and I’ll be the moderator today.

Agile 40

Agile Technical Review Software Review Engineering 40

Herding Cats

APRIL 16, 2019

Business, Technical, Systems, Risk, and Project Management Briefings and Presentations. Agile Project Management (#APM). Risk Management (#RM). Agile Software Development (#ASD). Integrating Agile and Earned Value Management (#AEVM). Business, Technical, Systems, Risk, and Project Management.

Technical Review 42

Technical Review Performance Measurement 2003 Underperforming Technical Team 42

Wrike

NOVEMBER 7, 2018

Agile Project Management. 64% of organizations say they frequently conduct risk management. [6]. 19% say Agile techniques. Agile Project Management. 38% of organizations report using agile frequently. [6]. Agile organizations grow revenue 37% faster and generate 30% higher profits than non-agile companies. [6].

2015 60

2015 Technical Review Underperforming Technical Team Software Review 60

MPUG

SEPTEMBER 9, 2020

Satya N Dash: You have also agile record concepts coming into time management that you have a lot of additional concepts such as burn up chart, burn down chart, release planning, story map. As early as 2009, 2010, nearly 11 years before I was working as a PMO. It will have measured risks for your project.

Software Review 52

Software Review Critical Chain Technical Review Risk Management 52

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. 61, September 2004. 153, 2007 “Overspend?

Estimate 40

Estimate Software Review Software 2012 40

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 2005 2006 2012 64

Herding Cats

SEPTEMBER 19, 2018

Monte Carlo simulation on projects examines all paths through the network of activities or all possible states of the project for the duration, cost, and risk that create impacts on duration and cost. This is a Closed Loop Control Systems for managing the performance of a Software Intensive System of Systems, all developed using Scrum.

Technical Review 43

Technical Review 2010 Estimate Software Review 43