Scrum.org

JULY 7, 2020

On many occasions in the recent past, working with distributed agile teams has amplified existing organizational, technical, and cultural challenges in many organizations. Frederick Brooks stated in his 1975 book The Mythical Man-Month: Essays on Software Engineering that “adding manpower to a late software project makes it later.”.

Technical Review 139

Technical Review Agile Software Review Software Engineering 139

Scrum.org

MARCH 22, 2023

I dove into sustainable IT and started with a ‘Planet Earth Retrospective’ for my Scrum Team, where we reviewed the Principles of Green Engineering. The sprint review showed the value they achieved for the planet, reducing an estimated 4 tons of CO2 per year. MP: Get the conversation started!

SCRUM 179

SCRUM Sustainability Infrastructure Technical Review 179

ActiveCollab

DECEMBER 20, 2018

At first glance, you could say these two are (fantasy) worlds apart, but people working in tech actually have more in common with classic Dungeons & Dragons classes than you might think. A proper Project Manager, just like a Paladin - leads by virtuous example. Software Engineer - Rogue. Project Manager - Paladin.

Technical Review 44

Technical Review Software Review Software Engineering Engineering 44

Scrum.org

JANUARY 25, 2021

The reasons for this are apparent, with software eating the world and the pace of innovation accelerating as the market-entry barriers of the technology sector are continuously lowered. Current tech trends — accelerated by the pandemic — threaten the very existence of many legacy organizations. Continuous integration.

SCRUM 194

SCRUM Technical Review Engineering Lean 194

Scrum.org

NOVEMBER 24, 2021

For example, there are supposedly eight stances for Product Owners. This includes training, technical support, and preparation for new releases. One of the reviewers of this article, Maarten Dalmijn , noted that he missed “product discovery” as a core activity in the work by Bass (2018). What strategies make them more?—?or

2014 216

2014 2008 Technical Review 2019 216

Scrum.org

JULY 14, 2021

This post is a non-technical version of an academic paper about Scrum teams that I wrote with Daniel Russo. Daniel is a Professor at the University of Aalborg and is specialized in empirical software engineering. Please note that our paper is currently reviewed by academic peers. . What about Sprint Goals?

SCRUM 242

SCRUM Influencer Technical Review Software Review 242

Wrike

FEBRUARY 18, 2021

Say, for example, you’re leading a project to create a new mobile app. Requirements analysis in software engineering . While requirements analysis is beneficial to any project, it is most common in software engineering. Requirement analysis document example . How do you find out project requirements?

Software Engineering 69

Software Engineering Engineering Technical Review Underperforming Technical Team 69

Scrum.org

OCTOBER 19, 2022

For example, an organization with a very flat hierarchical structure may both enable high agility as well as high morale or high stakeholder satisfaction. So we went to Google Scholar and searched for review articles. 2010) reviewed 28 scientific studies that investigated how Scrum is associated with overall business outcomes.

Agile 210

Agile 2010 2013 2008 210

Planio

FEBRUARY 17, 2019

So you want a software engineering job at Facebook/Apple/Amazon/Google/Netflix? It’s every software engineer’s dream to work with one of the top technical teams in the world. So how do you get a software engineering job at one of these companies? Self-taught vs. school: Do top tech teams really care?

Software Engineering 155

Software Engineering Technical Review Engineering Software Review 155

Leading Agile

OCTOBER 19, 2022

Agile Impediments exist at many levels, but most large scale Transformations now require that technical practices are more sound than ever. . As strategic priorities shift toward a focus on technology, hiring Scrum coaches just isn’t going to suffice to make Agile work.

Agile 96

Agile Software Review Technical Review Software Engineering 96

Scrum.org

JANUARY 10, 2021

Staggered iterations lead to more technical debt and lower quality software. TL;DR; The expected result of staggered iterations would be an increase in rework and in technical debt. There is a better way than staggered iterations for delivery that will keep you on the path to agility. Updated to reflect the 2020 Scrum Guide!

Software Review 180

Software Review Technical Review Software Engineering SCRUM 180

Project Pulse Journal

APRIL 17, 2024

Due to their different approaches to project management, this definition varies significantly between Agile and Waterfall methodologies. Examples from Other Frameworks Relating to the Definition of Done Kanban is less prescriptive than Scrum and requires a DoD to ensure workflow items are handled and completed.

Software Review 52

Software Review Development Team Review Technical Review 2024 52

Teamweek

DECEMBER 28, 2022

Technology is advancing at unprecedented speeds. Review a candidate’s entire portfolio. You should look at their past projects, hobby projects, and examples of code, as well as any blogs or open-source projects they have worked on. Hiring a great programmer is a monumental challenge for many reasons. Soft skills.

Development Team Review 52

Development Team Review Software Review Technical Review Artificial Inteligence 52

Leading Agile

MAY 25, 2023

Solid technical practices and your full-stack developer’s software craftsmanship are also limited by the conditions inside your organization. And so what we were talking about was the idea, on theme for the last couple of these recordings of, what are the necessary preconditions to be able to do software craftsmanship well?

Underperforming Technical Team 62

Underperforming Technical Team Software Review Technical Review CTO Hire 62

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

Let's start with a critical understanding of the purpose of managing risk on software development projects. Information about key project cost, (technical) performance and schedule attributes is often uncertain or unknown until late in the program. IEEE Transactions on Software Engineering , Vol. De Meyer, C.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

MARCH 11, 2017

The likelihood of a failure for example. So in the end, if we are to make a decision in the presence of uncertainty, we MUST make estimates to develop a reliable shipping date while producing an accurate and precise estimate of the cost, schedule, and technical performance of the product shipped on that date. Eggstaff, Thomas A.

2003 46

2003 2014 2015 2011 46

Teamweek

DECEMBER 8, 2023

Common causes for skills mismatches are poorly written job description ads, gaps in the hiring procedures, overemphasizing job experience over skills, and emerging technologies. For example, hiring managers admit that they hire the wrong person in 74% of cases.

Technical Review 52

Technical Review Underperforming Technical Team Software Review Artificial Inteligence 52

Paymo App

JANUARY 25, 2018

Provided that all team members can view the project’s timeline, they’ll see exactly who is in charge of a task, when the task started and when it’s due, and if there is any gap in the timeline where they can allocate additional tasks. Examples of time trackers. Because you’ll have the evidence of your work measured second by second.

Technical Review 86

Technical Review Software Review Monitoring Software Engineering 86

LiquidPlanner

JULY 10, 2018

For instance, in product development, the mechanical engineers don’t need to sit in on schematic reviews with the electrical engineers or code reviews with the software developers. They need to focus on the mechanical parts of the design and trust that the other engineers are doing their jobs well.

Software Review 140

Software Review Underperforming Technical Team Engineering Technical Review 140

Herding Cats

OCTOBER 24, 2018

This is an example of Stop Doing Stupid Things on Purpose. The classic example is in Animal Planet's Finding Bigfoot where the investigators have pre-determined the cause of the occurrence. An example of a Root Cause Analysis is Benjamin Franklin's Why Analysis †. Why Do Information Technology Projects Fail?”

2014 45

2014 Aerospace 2011 2013 45

Epicflow Blog

MAY 14, 2019

Over 200 PM experts from ExxonMobil, INEOS, DXC Technology, and other companies have shared their experience and proved that it’s a super hot topic. Business drivers have to be translated into project drivers by a strong technical team, not management. Read more: Examples of Lessons Learned in Construction Projects.

Underperforming Technical Team 75

Underperforming Technical Team Technical Review 2002 Software Review 75

PM Basics

APRIL 24, 2018

So, I will bring more clarity to this topic and will show examples of SDLC below. When I googled “software development life cycle definition” I found different variants. Examples of Software Development Life Cycles. So, now we will review each possible phase of SDLC. Review of SDLC Phases. But they exist.

Software Developers 67

Software Developers Software Development Software Review Software 67

Herding Cats

DECEMBER 8, 2017

It can be the needed performance of a measure - Effectiveness, Performance, Key Performance Parameter, or a Technical Performance Measures. The specifics of the Technical Performance Measures applied to inform Physical Percent Complete and the Cone of Uncertainty around the TPM are shown here. Here's a summary of these elements.

Performance Measurement 35

Performance Measurement Technical Review 2017 2008 35

MPUG

MAY 14, 2021

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. And today’s session is eligible for 1 PMI PDU in the technical category and the activity for claiming that with PMI is on the screen now. Fletcher Hearns: Great.

Performance Measurement 59

Performance Measurement Underperforming Technical Team Software Engineering Engineering 59

Herding Cats

JANUARY 14, 2017

Barry Boehm's work in “Software Engineering Economics”. The Cone is a project management framework describing the uncertainty aspects of estimates or any other project attribute (in this post, cost, schedule, and technical performance parameters). This is due to many reasons, one is levels of uncertainty early in the project.

Technical Review 28

Technical Review Software Review Underperforming Technical Team Risk Management 28

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

ProjectManager.com

JANUARY 12, 2022

Technical Project Management Conference. Project management at its core is a technical discipline, and the Technical Project Management conference, produced by the American Management Association, is a great place for those in the IT and technology space. For example, this year’s theme is retro gaming.

2022 276

2022 Technical Review PMO Underperforming Technical Team 276

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

Scrum.org

JUNE 13, 2022

Also, Developers enjoy complete autonomy regarding the technical side of their work: For each selected Product Backlog item, the Developers plan the work necessary to create an Increment that meets the Definition of Done. The term “Developer” seems to limit the role to technical people, for example, software engineers.

Underperforming Technical Team 149

Underperforming Technical Team SCRUM Technical Review Software Review 149

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

Leading Agile

NOVEMBER 29, 2023

About three or four years ago, we went down the path, Matt Van Vleet from previous and from Pillar Technology and from Accenture joined us and we started a studio. You need to start having the software engineers that can code the data scientists that can analyze. You’re not just a strategy firm.

Technical Review 62

Technical Review Software Review Engineering Infrastructure 62

Leading Agile

NOVEMBER 29, 2023

About three or four years ago, we went down the path, Matt Van Vleet from previous and from Pillar Technology and from Accenture joined us and we started a studio. You need to start having the software engineers that can code the data scientists that can analyze. You’re not just a strategy firm.

Technical Review 62

Technical Review Software Review Engineering Infrastructure 62

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. So a quick review again.

Technical Review 35

Technical Review Performance Measurement Underperforming Technical Team Estimate 35

Leading Agile

OCTOBER 17, 2018

Most technical coaches, including me, have a lot of difficulty clarifying the difference; not because it’s inherently complicated, but because it’s so obvious that it’s hard to come up with a verbal explanation. Keeping code clean at all times really ought to be considered baseline job performance for a software engineer.

Software Review 103

Software Review Technical Review Software Engineering Underperforming Technical Team 103

Scrum.org

MARCH 11, 2020

Finally, the term Development Team seems to limit the role to technical people, for example, software engineers. Ignoring technical debt: The Development Team is not demanding adequate capacity to tackle technical debt and bugs during the Sprint. Read more on technical debt and Scrum.). Team leads?

Development Team Review 223

Development Team Review Underperforming Technical Team Software Review Technical Review 223

Teamweek

NOVEMBER 9, 2022

And choosing from the many different project management software types can be quite a challenge. To make it simpler for you, we’ve compiled this list of 21 different types of project management software and example tools for each type. Types of project management software based on the use case. Example: Toggl Plan.

Software Review 52

Software Review Software Technical Review Construction 52