LiquidPlanner

MAY 31, 2022

Businesses need to be agile. This isn’t a new pressure – I remember the supply chain issues for electronics from Japan after the devastating tsunami in 2011. Join the debate on our LinkedIn page and let us know what you feel are the big factors influencing the future of project delivery. . What do you think?

Artificial Inteligence 155

Artificial Inteligence 2011 2021 PMO 155

Scrum.org

JUNE 29, 2019

Some people contributed independently, some built on work I had been doing since 2015, some of us leveraged the work of Ron Eringa and Ryan Ripley with their Professional Agile Leadership - Essentials class. The conversations strongly influenced what the reader will see in the coming posts in this blog series. Why agility?

Leadership 126

Leadership 2019 2011 2018 126

Scrum.org

AUGUST 1, 2022

Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. Many studies have found that psychological safety has a positive influence on team effectiveness (Edmondson, 2014). I also include insights from scientific research, as existing models about teamwork can provide a lot of focus.

2004 233

2004 2010 2009 2016 233

Herding Cats

MARCH 17, 2019

Establishing the Performance Measurement Baseline (PMB) , AACE Workshop, Denver, Colorado, April 16, 2011. Establishing the Performance Measurement Baseline , AACE Workshop , April 16, 2011. Agile Project Management. Integrating Agile with EVM , EVM World, 2013. A paradigm of Agile Project Management.

2003 54

2003 2011 2008 Performance Measurement 54

Scrum.org

MAY 29, 2020

If you’re not already aware, the way you think of testing within an agile approach is fundamentally different to the traditional one. The reason in 2011, Gojko Adzi introduce a different name to group these practices - “ Specification by Example ". But let us leave that for another day. Independently Deployable.

Software Review 135

Software Review Technical Review 2004 2003 135

Herding Cats

MAY 10, 2019

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. 5, September/October 2011. Effective Risk Management 2 nd Edition , Edmund Conrow, AIAA, 2003. Risk Management Papers. “A 3, March 2002. 24, 2010. “A

Risk Management 38

Risk Management Risk Technical Review 2002 38

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. 5, September/October 2011. These papers and other resources were retrieved from public sites. Risk Management is essential for development and production programs. “A

Risk Management 35

Risk Management Risk Technical Review 2002 35

Epicflow Blog

MAY 14, 2019

Donato Piccinno , a Project Manager at DXC Technology, advises to “measure and improve clarity, unity and agility. Merrow (Wiley, 2011), recommended by Giorgio Locatelli , an Associate Professor of Infrastructure Procurement and Management at the University of Leeds. then more often that not you’ll be fighting a losing battle!”

Underperforming Technical Team 75

Underperforming Technical Team Technical Review 2002 Software Review 75

Scrum.org

FEBRUARY 4, 2022

This post is for anyone who wants to inspire, change or influence others through their efforts as professionals, with emphasis on the latter. I think you should read this post, and take it to heart when you write content that is aimed at influencing others. What is the optimal size of a team? Is scaling always a bad idea?

Agile 193

Agile Software Review Underperforming Technical Team Technical Review 193

Stepping Into Project Management

MARCH 10, 2014

Today we interview Siddhartha Govindraj, who specializes in Lean/Agile processes for software development. An occasional organizer of events as a part of Chennai Agile User Group and speaks in conferences in India and abroad. Agile becoming mainstream now, how do you think the world of project management has changed?

2011 37

2011 Lean 2013 Agile 37

Planio

JULY 9, 2020

There’s a reason startups are obsessed with “community” and influencers tell you to find your “tribe”. Agile Project Management out of the box. While task management app Wunderlist was released in 2011 and, after being acquired by Microsoft, was discontinued in May 2020. Agile Project Management out of the box.

2006 88

2006 2007 Closing Agile 88

Scrum.org

AUGUST 17, 2020

Ross & Nisbett (2011) offer an extensive overview of research in this area. . Initially coined by cognitive psychologist Lee Ross (1977), it happens when people underestimate the influence of the situation on the behavior of others while overestimating the influence of their personal traits and beliefs (Berry, 2015).

2015 221

2015 2014 2004 Influencer 221

Velociteach

MARCH 20, 2023

And we set off, took off running in 2011. Alan Zucker’ s Agile Beyond IT course, delves deeply into how using an agile mindset can help improve productivity on all types of projects. And the success or the failure of the project so many times is so influenced by the leadership of that project manager.

Logistics 52

Logistics Transportation 2022 Governance 52

Scrum.org

JUNE 24, 2022

But Scrum and the Agile methodologies it builds on are so much more. Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. Its earliest members, like Herzberg, started to investigate how the psychological processes of workers influenced their motivation.

SCRUM 188

SCRUM 2002 2006 2007 188

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 168

Underperforming Technical Team 2007 2006 2009 168

International Institute for Learning

NOVEMBER 9, 2022

You get the word: “We are going AGILE!” Business analysts generally rely on their communication skills: negotiation, mediation, influence, and networking to get things done rather than authority. And, of course, the role of business analyst still exists in and around Agile and Scrum. By Steve P. Now what do you do? Steve Blais.

SCRUM 78

SCRUM Software Developers Software Development 2011 78

Scrum.org

DECEMBER 23, 2021

Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. It also ties well into a recent post where we discussed a scientific study that showed how critical the socio-technical skills of developers are to the success of Agile transformations. 2011, Politowski, 2020). Why do software teams?

Software Review 183

Software Review Technical Review Underperforming Technical Team 2015 183

MPUG

MARCH 18, 2021

Optimizes the use of organizational resources, helps to balance the influence of constraints on the project. 2011, when we had that earthquake in Maryland. This is on page 10, effective project management. Number one helps increase chances of success, delivers the right products at the right time. It’s that last one.

Risk Management 52

Risk Management Software Review Underperforming Technical Team Governance 52

Herding Cats

APRIL 16, 2019

Agile Project Management (#APM). Agile Software Development (#ASD). Integrating Agile and Earned Value Management (#AEVM). Agile and Earned Value Management Bibliography of papers, books, and thesis (#Biblio). PMI EVM Community of Practice, EVM World , May 16-18 2011. Agile Project Management.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Herding Cats

MARCH 11, 2018

By the way, the pure conjecture that agile enables late changing requirements to not have a significant impact on the cost and schedule of the development project is completely lacking any testable evidence outside of personal anecdotes of agile advocates. Editors, Springer, 2011. July 20, 2011. Hillson, D. and Simon, P.,

Software Developers 34

Software Developers Software Development Risk Management Risk 34

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. Prakash and V. 3, September 2017, pp.

Estimate 40

Estimate Software Review Software 2012 40

Herding Cats

NOVEMBER 7, 2016

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. “The Story Point Estimating,” Richard Carlson, ALEA, Agile and Lean Associates, 2013.

Estimate 64

Estimate 2006 2005 2013 64