Scrum.org

APRIL 7, 2022

Even a single change in team membership can disrupt that process, and consequently, make it harder for teams to become high-performing sooner. Kozlowski & Ilgen (2006) describe this reciprocity as “process begets structure, which in turn guides process”. Or if these processes can be fast-tracked. Bradley et.

Underperforming Technical Team 156

Underperforming Technical Team 2007 2006 2009 156

Herding Cats

OCTOBER 30, 2018

There have been some recent posts about managing scope, defining needed Features, determining how to release software to stakeholders - in both traditional and agile processes. Capabilities-based planning enables the enterprise to identify business and technical needs, allocate resources, and track activities and outcomes. .

Planning 109

Planning 2007 Technical Review 2009 109

ProjectManager.com

DECEMBER 12, 2018

In 1969, in Philadelphia, Jim Snyder, of Smith, Kline & French Laboratories, and Gordon Davis, of the Georgia Institute of Technology, were having dinner and decided there was a need for an organization that offered project managers a forum to share information and discuss their industry. Certification.

PMI 279

PMI Technical Review Certification Software Review 279

Scrum.org

JUNE 1, 2022

And does your Sprint Review consist of team members listing their individual accomplishments? This recognition of the socio-dynamic processes in groups of people is also what attracts me to Scrum. Many methodologies are so focused on process efficiency that they seem to ignore the human factors involved. Brown, R., & Pehrson, S.

SCRUM 205

SCRUM 2007 2003 2006 205

Rebel’s Guide to PM

AUGUST 28, 2017

Training is a structured way to embed and support the new behaviours, explain new processes and get people comfortable with new ways of working. Here is some further reading that you might like: Emotional Intelligence for Project Managers, Anthony Mersino (Amacom, 2007). Women in Science, Engineering and Technology.

Change Management 290

Change Management Technical Review 2007 Engineering 290

Scrum.org

NOVEMBER 5, 2023

Inflexible Structures Hinder Adaptability : Traditional management often has rigid hierarchies and processes designed for stability. These structures can make it difficult to adapt when change is needed, leading to slow responses to market shifts, customer needs, and technological advancements. Harvard Business Review.

Leadership 158

Leadership Underperforming Technical Team 2007 Agile 158

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). Developing a new product requires understanding of the users, of the technologies involved and what makes something valuable (or not).

2002 190

2002 SCRUM 2007 2003 190

Leading Agile

JUNE 27, 2018

The impression was reinforced strongly when I attempted to bridge the divide by participating in the academic tracks of agile and technical conferences in the 2007-2008 time frame. I told them that practitioners wouldn’t bother using TDD if they hadn’t experienced benefits like that one. In the dirty, smelly field.

Software Review 88

Software Review Technical Review Underperforming Technical Team 2007 88

Rebel’s Guide to PM

SEPTEMBER 26, 2016

We wonder whether this desire to investigate and move to new technology comes from this new project management tools market configuration or it is its cause. It’s easy to find technical information online about each project management tool, and they are often compared against each other on the basis of technical and contextual aspects.

Software Review 150

Software Review Software Technical Review PMI 150

Agilemania

FEBRUARY 23, 2023

Concerns were voiced in the IT operations and software development sectors from 2007 to 2008 about the old software development paradigm that split operations from developers regarding how code was distributed and supported. To achieve speedier outcomes, developers must thoroughly grasp the entire DevOps process. What is DevOps?

Software Review 52

Software Review Technical Review Certification 2007 52

The IIL Blog

JULY 19, 2023

The wage and salary activities for the assigned workers were the responsibility of their functional managers and project managers often had very little input if any in the performance review processes. Team members relied upon their functional managers for encouragement, support, and performance reviews. Pendry et al.,

2002 78

2002 2023 Leadership 2007 78

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. And one of those services is Information Technology: IT. Keeps services under review to ensure they will continue to meet future needs.

Technical Review 71

Technical Review 2011 2007 Prince2 71

nTask

MARCH 10, 2021

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. Typically, however, since the DoD is aimed at guaranteeing that releases work well and basic technical requirements are met, the technical team leads the creation of the DoD.

Software Review 78

Software Review Technical Review 2002 2007 78

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. Taxonomy-Based Risk Identification,” Marvin Carr, Suresh Konda, Ira Monarch, Carlo Ulrich, and Clay Walker, Technical Report, CMU/SEI-93-TR-6, Software Engineering Institute, June 1993.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

MAY 11, 2019

Information about key project cost, (technical) performance and schedule attributes is often uncertain or unknown until late in the program. Taxonomy-Based Risk Identification,” Marvin Carr, Suresh Konda, Ira Monarch, Carlo Ulrich, and Clay Walker, Technical Report, CMU/SEI-93-TR-6, Software Engineering Institute, June 1993.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Planio

JULY 22, 2020

Swipe to Unlock: The Primer on Technology and Business Strategy. Project management is as much about people as it is about processes. Technical documentation. Why you should read this: Once you master the materials inside the PMBOK you’ll have a process for initiating and successfully running any project.

2020 148

2020 Underperforming Technical Team Technical Review Software Review 148

Rebel’s Guide to PM

JUNE 27, 2021

This event will cover the process of designing and delivering engaging, well-run and effective sessions, starting with an initial idea and through careful, step-by-step preparation to running them successfully, despite the inevitable challenges. So I’m going to do some technical wizardry and just remove me for a moment.

Technical Review 307

Technical Review Leadership Energy 2001 307

Epicflow Blog

APRIL 19, 2021

One of them is office politics, which exists in most environments and often affects the decision-making process. . For example, those engaged in office politics can make efforts to establish relationships necessary to gain a powerful voice in the decision-making process. Let’s take a closer look. .

2007 52

2007 Influencer Technical Review Software Review 52

Runrun.it

NOVEMBER 13, 2019

Well-rounded employees are needed for better outcomes in the technology sphere, which means that more minority groups will need to be represented throughout this industry. The Current Groups Missing in the Technology Sector. From 2007 to 2015, there has been a 15 percent decline in the number of African-American women professionals.

Technical Review 20

Technical Review Software Review 2007 2015 20

Resource Guru

JUNE 23, 2023

You can find previous parts in this series here: Part 1: The basics of agency project management Part 2: 5 agency project management methodologies Part 3: Your 9-step agency project management process Part 4: Agency team structure: Building a team for effective growth Part 5: You’re reading it. Do they offer a robust API?

Software Review 52

Software Review Technical Review Software 2021 52

Herding Cats

MAY 7, 2019

So start here to build your academic foundation, that can be put to work to build a foundation of validated experience of making estimates in the presence of uncertainty and protect yourself from fallacious claims that estimates are a waste, not needed, and produce bad resulting in the decision making process for those paying you to produce value.

Estimate 40

Estimate Software Review Software 2012 40

Herding Cats

NOVEMBER 7, 2016

The same process for estimating is applied to multi-billion dollar projects we work. And the same process is applied to the Scrum development processes on those projects. . Here's some materials that provide the tools and processes needed to learn how to estimate. 1, January 2007.

Estimate 64

Estimate 2006 2005 2013 64

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

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? In the usual Scrum process, the P.O. All code is reviewed by senior leads and only after that, Dev is considered complete. Is this you?

Development Team Review 154

Development Team Review Software Review Cadence Technical Review 154

Herding Cats

MARCH 11, 2018

Take for example the deployment of an ERP system, the installation, and startup of a process control system, the release of a suite of embedded software controllers for a car, aircraft, petrochemical plant. Amd of course, the Root Cause determined before any corrective or preventive action can be taken: Technical ?

Software Developers 34

Software Developers Software Development Risk Management Risk 34

Epicflow Blog

JANUARY 12, 2021

They work closely with portfolio office managers to oversee all processes are in line with the objectives and all tasks are accomplished according to the requirements. . This type of knowledge covers the understanding of the processes, job duties of all employees, rules, market trends that are peculiar for this professional environment. .

PMO 82

PMO 2007 Controlling Construction 82

Knowledgeline

NOVEMBER 14, 2006

Knowledgeline Tuesday, November 14, 2006 SharePoint 2007 Update - Enterprise Search Rocks!! So, we are now less than a month away from going live on our SharePoint 2007 portal. With the help of XMLAWs web part for Enterprise Search within WorkSite , we pointed the SharePoint 2007 Enterprise Search engine at our DMS and let it rip.

2007 40

2007 2006 Engineering Technical Review 40

Herding Cats

APRIL 16, 2019

Business, Technical, Systems, Risk, and Project Management Briefings and Presentations. Management Processes (#MP). Technical Performance Measures (#TPM). Cost, Schedule, and Technical Performance Management (#CSTPM). Business, Technical, Systems, Risk, and Project Management. Management Processes.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Herding Cats

OCTOBER 24, 2018

Root Cause is the fundamental initiating cause on a causal chain leading to a failure of a process which results in a recurrence of the problem. Root Cause Analysis is a systematic documented approach to arrive at the true Root Cause of the process problem. Gano, Atlas Books, 2007. Why Do Information Technology Projects Fail?”

2014 45

2014 Aerospace 2011 2013 45

Herding Cats

JULY 24, 2017

The Cone of Uncertainty is the Planned reduction in the uncertainty of critical project variables (cost, schedule, technical performance) needed to increase the probability of project success. Six Rules of Effective Forecasting," Paul Saffo, Harvard Business Review , July-August 2007. 37–48, 2007. . 37–48, 2007. .

2007 42

2007 2012 2006 2008 42

Online PM Courses

OCTOBER 14, 2018

Serving the project management community since 2007 with fresh project management articles every day! Dedicated to provide PM articles, detailed PM software reviews, PM book reviews, and the latest news for the most popular web-based collaboration tools: Project-Management.com. PM Blogs and Bloggers. PM Hut: @pmhut.

PMO 72

PMO Technical Review Underperforming Technical Team PMI 72

Herding Cats

NOVEMBER 5, 2018

In a previous post, Why Johnny Can't Estimate , mentioned some resources for estimating, the principles of business and technical management that demand estimates be made to make decisions, and background on the sources of uncertainty, that create risk, that require estimating to increase the probability of project success.

Software Review 34

Software Review Technical Review Estimate Software Developers 34

Herding Cats

MARCH 11, 2017

This quote demonstrates a lack of understanding of making decisions in the presence of uncertainty and the processes and events that create uncertainty. There is naturally occurring variability from uncontrolled processes. Aleatory uncertainty is expressed as a process variability. First, let's establish a principle.

2003 46

2003 2014 2015 2011 46

Herding Cats

JANUARY 22, 2017

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. Unanticipated technical issues with alternative plans and solutions to maintain effectiveness.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 17, 2017

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. Unanticipated technical issues with alternative plans and solutions to maintain effectiveness.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JUNE 19, 2017

The Cone of Uncertainty as a Technical Performance Measure. If the parameter of interest is not being reduced as needed, go find out why and fix it, or you'll be late, over budget, and the technical outcome unacceptable. The Cone of Uncertainty as a Technical Performance Measure. Technical Performance Measure.

Technical Review 35

Technical Review Performance Measurement Underperforming Technical Team Estimate 35