Rebel’s Guide to PM

AUGUST 28, 2017

Creates a deliverable e.g. a new software system Creates an environment where benefits can be realised e.g. new software is used to improve efficiency. 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 289

Change Management Technical Review 2007 Engineering 289

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

Scrum.org

JUNE 1, 2022

And does your Sprint Review consist of team members listing their individual accomplishments? Wang et al (2006) studied software teams tasked with ERP implementations and found that cohesive teams performed significantly better than less-cohesive teams. Psychological review , 57 (5), 271. 2007, August). R., & Dion, K.

SCRUM 219

SCRUM 2007 2003 2006 219

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

Wrike

JANUARY 12, 2024

Jeff Kinney’s hit children’s book series, Diary of a Wimpy Kid , was first released in 2007 and is still rolling out installments each year. Feasibility analysis: Next, evaluate each idea for its feasibility — this means technical, financial, and market viability. Be creative and think outside the box!

Innovation 36

Innovation Process Technical Review Artificial Inteligence 36

Scrum.org

DECEMBER 23, 2021

Why is code quality so often an issue? Why do software teams?—?despite 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 187

Software Review Technical Review Underperforming Technical Team 2015 187

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. 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.

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. Let's start with a critical understanding of the purpose of managing risk on software development projects. IEEE Transactions on Software Engineering , Vol. Raz and E.

Risk Management 35

Risk Management Risk Technical Review 2002 35

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 174

2017 2018 2016 SCRUM 174

Runrun.it

NOVEMBER 13, 2019

Project management software can also help improve collaboration between different groups of employees. 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.

Technical Review 20

Technical Review Software Review 2007 2015 20

Online PM Courses

OCTOBER 14, 2018

Software Vendors. 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 Bloggers.

PMO 75

PMO Technical Review Underperforming Technical Team PMI 75

Herding Cats

OCTOBER 24, 2018

But before going further, let's establish the definitions we need to understand and apply Root Cause Analysis needed to discover the corrective and preventive actions to increase the probability of project success - especially Software Project Success. Gano, Atlas Books, 2007. What factors lead to software project failure?”

2014 45

2014 Aerospace 2011 2013 45

Herding Cats

JULY 24, 2017

Shipping on time, to specifications, and within budget might be meaningless if a competitor is shipping software that has a greater value to the market. It's suggested from observations, the Cone of Uncertainty (CoU) is not a valid model of how uncertainty behaves in software development projects. 37–48, 2007. . Laird and M.

2007 42

2007 2012 2006 2008 42

Leading Agile

JUNE 27, 2018

In 2012, I wrote a blog post entitled “Delivering provably-correct code.” ” In it, I suggested several approaches developers could use to gain high confidence that their code would be suitable for release. When they talk about the “correctness” of software, they’re talking about two different things.

Software Review 123

Software Review Technical Review Underperforming Technical Team 2007 123

Herding Cats

JANUARY 22, 2017

Barry Boehm's work in “Software Engineering Economics”. 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. Prentice-Hall, 1981.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 17, 2017

Barry Boehm's work in “Software Engineering Economics”. 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. Prentice-Hall, 1981.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

FEBRUARY 4, 2017

Barry Boehm's work in “Software Engineering Economics”. 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. Prentice-Hall, 1981.

Technical Review 28

Technical Review Estimate 2005 Software Review 28

Herding Cats

MARCH 11, 2017

The naturally occurring work effort in the development of a software feature - even if we've built the feature before - is an irreducible uncertainty. The Development of Progress Plans Using a Performance–Based Expert Judgment Model to Assess Technical Performance and Risk,” Justin W. They cannot be suppressed or removed. 12, 2008.

2003 46

2003 2014 2015 2011 46

Herding Cats

JUNE 19, 2017

The Cone of Uncertainty is a framing assumption used to model the needed reduction in some parameter of interest in domains ranging from software development to hurricane forecasting. The Cone of Uncertainty as a Technical Performance Measure. The Cone of Uncertainty as a Technical Performance Measure. Measure of Effectiveness.

Technical Review 35

Technical Review Performance Measurement Underperforming Technical Team Estimate 35

Rebel’s Guide to PM

SEPTEMBER 26, 2016

The project and portfolio management (PPM) software market is changing. In this article we look at emerging software in the PPM space and discuss how its selection and implementation needs to be done in line with an overarching digital strategy. A tiny snapshot of the analysis that the different software tools went through.

Software Review 150

Software Review Software Technical Review PMI 150

Scrum.org

APRIL 7, 2022

Wang et al (2006) studied software teams tasked with ERP implementations and found that cohesive teams performed significantly better than less-cohesive teams. This is probably due to the difficulty of measuring many teams over a long period of time. This effect is stronger for smaller teams than larger teams. Bradley et.

Underperforming Technical Team 175

Underperforming Technical Team 2007 2006 2009 175

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). Software development is (generally speaking) very complex. Why our brain is not built for software engineering.

2002 208

2002 SCRUM 2007 2003 208

MPUG

NOVEMBER 11, 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. Today’s session is eligible for 1 PMI PDU in the technical category. The MPUG activity code for claiming that with PMI is on the screen now.

Software Review 52

Software Review Lean SCRUM PMI 52

Planio

JULY 22, 2020

The Culture Code: The Secrets of Highly Successful Groups. Swipe to Unlock: The Primer on Technology and Business Strategy. Technical documentation. Each chapter ends with quick reviews making this a useful “PMBOK for Dummies”. Author: Harvard Business Review. Influence: The Psychology of Persuasion.

2020 148

2020 Underperforming Technical Team Technical Review Software Review 148

MPUG

JULY 17, 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. This session is eligible for one PMI PEU in the technical category. Jim is the president of Critical Tools, the makers of WBS Schedule Pro Software. Kyle: Great.

Software Review 52

Software Review 2014 Planning Technical Review 52

Herding Cats

MARCH 11, 2018

Microeconomics is applicable to the development is software systems. If we look at the discipline of software engineering, we see that the microeconomics branch of economics deals more with the types of decisions we need to make as software engineers or managers. Software engineering economics." Macroeconomics is not. .

Software Developers 34

Software Developers Software Development Risk Management Risk 34

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 73

Technical Review 2011 2007 Prince2 73

Scrum.org

SEPTEMBER 23, 2019

So, for example, no engineers are mourning the demise of the hero-developer, who single-handedly saves the organization with beautifully crafted code while burning the midnight oil.). Let me provide you with an example: Back in 2007/2008, I was a member of a Scrum Team that was split between Berlin and Wroclaw in Poland.

Development Team Review 136

Development Team Review SCRUM Software Review Technical Review 136

Leading Agile

JANUARY 15, 2019

The title is based on a quote from the 2007 movie, Ghost Rider. Connection with Software Development. Software development teams often find themselves tangled up with more work than they can handle gracefully, if at all. The two fight briefly. cutting corners only results in the illusion of speed. Easier Said Than Done.

Software Review 89

Software Review Development Team Review 2007 Technical Review 89

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 my over 25+ years in the software industry, this has been an all too familiar situation! I have often wondered – doesn’t speak too well of us as software professionals!

Development Team Review 154

Development Team Review Software Review Cadence Technical Review 154

Wrike

APRIL 29, 2008

Conference 2007, she gave a presentation on Social Project Management , where she pointed out several distinctive features of the new wave in the project management discipline. According to her, these ways emerge in project management due to the penetration of social software into in the enterprise. At Enterprise 2.0

Technical Review 28

Technical Review 2007 Software Review Influencer 28

Knowledgeline

OCTOBER 3, 2006

Given that Lexis has the Applied Discovery offering, it shouldnt be long before Thomson/West look to also acquire a company that provide an online review tool for e-discovery. SharePoint 2007 is full of surprises – let's talk. Practice Enhancement The Best KM Software Yet? Knowledge Management v.

2006 40

2006 2007 Technical Review Software Review 40

Epicflow Blog

APRIL 19, 2021

Considering all these factors, it becomes nearly impossible to have a high-performing project team with individuals who are not only technically skilled but motivated to contribute to the project’s outcome. Paper presented at PMI® Global Congress 2007—North America, Atlanta, GA. References.

2007 52

2007 Influencer Technical Review Software Review 52

Epicflow Blog

JANUARY 12, 2021

Read more: Industry, Product, and Technical Knowledge: What Makes a Project Manager an Expert? As, for example, an IT project manager orchestrates IT projects and leads corresponding teams in their software development efforts. Paper presented at PMI® Global Congress 2007—North America, Atlanta, GA. References. Arras People.

PMO 82

PMO 2007 Controlling Construction 82

Herding Cats

APRIL 16, 2019

Here's a collection of presentations, briefings, papers, essays, book content used to increase the Probability of Project Success (PoPS) I've written and applied over my career in the software-intensive system of systems and other domains. Business, Technical, Systems, Risk, and Project Management Briefings and Presentations.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

MPUG

JULY 1, 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. PMI PDUs in the technical category and the MPUG activity code for claiming the session was on the screen now. PMI PDUs in this technical category.

Risk Management 52

Risk Management Risk 2016 Underperforming Technical Team 52

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