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 292

PMI Technical Review Certification Software Review 292

Scrum.org

MAY 15, 2023

Suggest how to help the Scrum team balance technical debt and new feature development. Create a workshop on Scrum for new stakeholders. Balance technical debt and new feature development based on: [Your work item list]. Create a workshop on product management in Scrum for new stakeholders. Design a Sprint board.

ChatGPT 209

ChatGPT Technical Review SCRUM Artificial Inteligence 209

Scrum.org

FEBRUARY 25, 2024

These anti-patterns can emerge due to a variety of reasons, such as resistance to change, lack of understanding of Scrum principles, or misalignment of organizational practices with Scrum values.

SCRUM 226

SCRUM ChatGPT Technical Review Development Team Review 226

Scrum.org

JUNE 3, 2021

According to Michael James , dependencies in knowledge work — as in software development — are caused by knowledge gaps and not by the laws of physics. . Progress in development can only be made tangible through the delivery of software. Communicate in Code. But there is a problem — dependencies. . He's right. Inner Sourcing.

Software Review 232

Software Review Technical Review Sustainability Closing 232

Rebel’s Guide to PM

DECEMBER 18, 2022

Adapt and flex as you go, reviewing priorities and working on what you can while the other stuff unfolds. Very handy for when there is a lot of software testing to do. When the project’s technology changes. We do a lot of workshops and process mapping, looking at as is/to be or current state and future state.

Underperforming Technical Team 412

Underperforming Technical Team Technical Review Budget Software Review 412

Scrum.org

OCTOBER 26, 2021

However, in my experience (which has mainly been within the software development industry) many of these teams appear to be thought of and treated as a delivery capability. As well as sessions on Agile, subjects ranged from new development tools, facilitation techniques, build pipelines, TDD workshops, case studies and much more.

Technical Review 202

Technical Review Software Review Agile SCRUM 202

Scrum.org

JUNE 17, 2019

Writing code is like finding your path through a dark forest. For me, this attitude encapsulates the essence of writing software empirically. But how does it translate into the practice of writing code? I strongly believe that you shouldn’t write code before you at least understand the purpose of what you intend to create.

Software Review 166

Software Review Initiating Technical Review SCRUM 166

Scrum.org

OCTOBER 10, 2024

Working Software. Two related concepts in the agile world that people trying to leverage Agile/Scrum’s empiricism outside of the software/technology space struggle with. The work done towards an increment to bring before this panel will be structured to enable a holistic review of where we stand. Done Increments.

Software Review 192

Software Review Technical Review Sustainability Manufacturing 192

Scrum.org

NOVEMBER 20, 2023

Overemphasis on Utilization : Prioritizing keeping teams busy with feature work over allowing time for creativity, exploration, and addressing technical debt also contributes to a feature factory environment. Display this vision prominently in your team space and reference it in all Scrum events.

Technical Review 213

Technical Review Software Review Underperforming Technical Team Sustainability 213

Scrum.org

FEBRUARY 28, 2022

We created 3 do-it-yourself workshops to support your Scrum team in answering these questions. All of the workshops include a step-by-step approach to use them and help you move in the right direction. The workshops are: Help Your Team Get Started With A Definition of Done. Where skills, tools, and technologies are missing.

SCRUM 215

SCRUM Technical Review Software Review Risk Management 215

Scrum.org

JANUARY 4, 2021

A good starting point would be working with the “Manifesto of Agile Software Development,” particularly ensuring that stakeholders understand that adapting to change over following a plan is paramount for the organization’s future success. Proven examples are user story mapping or product roadmap planning workshops. (It

SCRUM 253

SCRUM Technical Review Software Review Agile 253

Project Risk Coach

APRIL 9, 2018

Learn technical skills to accelerate your projects through requirements development How big of a deal are project requirements? The Project Management Institute says, “47% of unsuccessful projects fail to meet goals due to poor requirements management.” Requirements workshops. ” What are Project Requirements?

Software Review 207

Software Review Technical Review Underperforming Technical Team Risk Management 207

Rebel’s Guide to PM

OCTOBER 23, 2017

These days I’m doing a lot less technical project management and a lot more business-led project management and change management. It’s a fast way to collaborate in workshops as it acts like a whiteboard for note capture, plus you can save time writing up the meeting afterwards! MindManager.

Technical Review 280

Technical Review 2018 PMO Software Review 280

Leading Agile

NOVEMBER 18, 2021

This team of e Agile Transformation Coaches will consist of people focused on executive-level understanding and leadership, people that teach team-level technical practices, and everything in between. Technical Coach. The Technical Coach collaborates with the TL and EL to understand the Expedition Roadmap and the desired outcomes.

Technical Review 118

Technical Review Software Review Agile Lean 118

Scrum.org

FEBRUARY 16, 2021

Join us on March 9, 2021 , for a live virtual workshop to create actionable recommendations on how to deal with the outcome of a forensic Product Backlog analysis. Therefore, the first question any aspiring agile startup should answer for itself is simple: is it a sales-driven, product-driven, or tech-driven enterprise?

Agile 180

Agile Technical Review Software Review Underperforming Technical Team 180

Scrum.org

OCTOBER 12, 2020

The definition of done is a common understanding within the Scrum Team on what DONE means , and it evolves as the team learns more about the product and technical skills. 4th – Review Team capacity . Having sub-tasks like design, coding, writing test cases, functional testing and code reviews, etc.,

Planning 254

Planning Technical Review Development Team Review Software Review 254

Scrum.org

AUGUST 19, 2021

And what about the socio-technical skills of Developers? In this post, I summarize the findings from an academic peer-reviewed publication by Daniel Russo (2021), a professor at the University of Aalborg. management support, technical skills) while everything else is kept equal. What do we already know?

Agile 235

Agile Technical Review 2021 Influencer 235

Scrum.org

MARCH 22, 2021

Join more than 100 peers from May 27-29, 2021 , for the Virtual Agile Camp Berlin 2021, a non-profit live virtual Barcamp using open space technology principles and practices. Has the level of technical debt increased or decreased during the last Sprint? Scrum Master Interview Questions: How We Organized Questions and Answers.

SCRUM 235

SCRUM Underperforming Technical Team Development Team Review Technical Review 235

Scrum.org

JANUARY 9, 2023

The Scrum Master can encourage stakeholder participation in Scrum events, such as the sprint review and retrospective. What level of address technical debt do we need to address? Follow-up question : What about technical debt and available skills? Do we have all the tools necessary, and are we familiar with those?

ChatGPT 227

ChatGPT SCRUM Underperforming Technical Team Technical Review 227

Scrum.org

NOVEMBER 24, 2021

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). The Sprint Review is an excellent opportunity to engage in product discovery. rather than on your own”.

2014 233

2014 2008 Technical Review 2019 233

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. . How can you make a Scrum team more effective?

SCRUM 242

SCRUM Technical Review Influencer Software Review 242

Project Risk Coach

FEBRUARY 4, 2019

Susan, on the other hand, facilitated an early risk identification workshop. She periodically met with her team to review current risks and used additional techniques to identify new risks. In these risk review sessions, the team discussed the effectiveness of the risk responses and the risk management processes.

Controlling 199

Controlling Risk Technical Review Performance Measurement 199

NimbleWork

MARCH 10, 2024

Regular training, workshops, and knowledge sharing reinforce this mindset. Story Grooming Value Stream Product owners, technical & test leads follow “story grooming” value stream to make sure they take a 360-degree review of functional and non-functional requirements before delegating it for downstream implementation.

Engineering 105

Engineering Software Review Technical Review Executing 105

Scrum.org

JUNE 22, 2019

These teams were mostly focused on software development. That’s not going to be a technical perspective. Although I did try being a developer, I failed miserably… To be clear, whenever I write “developer” in this article, I mean everyone involved in writing software and building products. It’s about the outcome, not output.

Underperforming Technical Team 184

Underperforming Technical Team Technical Review Software Review Development Team Review 184

Rebel’s Guide to PM

JULY 1, 2024

Typical inputs could be pieces of information, raw materials, or the technical environment. That’s why plenty of projects start off with creating a high level process map, or at least reviewing the last time process mapping was done and ensuring that whatever business process flow was produced back then is still accurate for today’s project.

Lean 328

Lean Technical Review Software Review Manufacturing 328

Scrum.org

DECEMBER 16, 2019

Professional Scrum Master (PSM-I) workshop has a module that talks about the Definition of DONE (DoD) and Technical Debt. Specifically, when we talk about Product Development (considering the system/software/solution), the DoD consists of 3 main components: Business or Functional requirements. Technical Debt.

Development Team Review 203

Development Team Review Software Review Technical Review SCRUM 203

Scrum.org

MAY 31, 2022

When the rest of the team continues doing more Analysis and Coding tasks, this will overload the bottleneck even more. In our book we introduce a workshop to initialize the StarMap as well as other tips on how to work with this tool. No or little extra code review needed. Collective code ownership.

Software Review 205

Software Review Technical Review Agile Influencer 205

Scrum.org

AUGUST 17, 2020

Scrum has proven time and again to be the most popular framework for software development. Given that software is eating the world , a seasoned Scrum Master is nowadays in high demand. Though whatever the case, we can say for sure that Scrum is very popular in software development. TL; DR: Scrum Master Interview Questions (1).

SCRUM 234

SCRUM Technical Review Software Review Agile 234

ProjectManager.com

SEPTEMBER 26, 2018

Review inventory levels and production schedules for product availability. Continue professional and technical education, attending workshops, seminars, etc. ProjectManager.com is a cloud-based software that has real-time dashboards and online Gantt charts to monitor, report and schedule, respectively.

Technical Review 64

Technical Review Leadership Monitoring Executing 64

Rebel’s Guide to PM

FEBRUARY 28, 2022

Normally we’d think of that in terms of the technical skills they need to deliver the project, like taking a course in a programming language or brushing up their system maintenance skills. You are also responsible for your team, and making sure they have the skills required to do their jobs. Log the project risks on a risk log.

Risk Management 284

Risk Management Risk Technical Review 2015 284

Rebel’s Guide to PM

JANUARY 7, 2019

These past few years have seen an incredible evolution in the way software is built. In these next years, we’re going to see a new wave of what software can do with the growing capabilities of machine learning, artificial intelligence and data pipelines across enterprises. So I’ll offer you an additional tip for 2019. Robin Burk.

2019 292

2019 Technical Review PMO Consulting 292

Scrum.org

APRIL 11, 2019

Delivering working software is perceived as an IT responsibility instead of a Business-IT collaboration. Connect the dots by making reporting on market research data and customer feedback data a mandatory item of the Sprint Review. This will open up all code for all developers to understand and change. A single source of truth.

Underperforming Technical Team 180

Underperforming Technical Team SCRUM Development Team Review Software Review 180

Scrum.org

OCTOBER 19, 2022

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. A strength of such a review is that it allows for the identification of patterns across many studies. Journal of systems and software , 81 (6), 961–971.

Agile 225

Agile 2010 2013 2008 225

Scrum.org

JANUARY 17, 2023

Think twice if you still believe this technology is a fad or a toy. The technology your Scrum team has built over time is increasingly less reliable, and technical debt is notably increasing. If you still believe that underlying technology is a toy or fad, think again. Lo and behold, it worked very well.

ChatGPT 208

ChatGPT Underperforming Technical Team SCRUM Technical Review 208

Rebel’s Guide to PM

NOVEMBER 7, 2018

Typical inputs could be pieces of information, materials, or the technical environment. That’s why plenty of projects start off with mapping existing processes, or at least reviewing the last time process mapping was done and ensuring that whatever process flow was produced back then is still accurate for today’s project.

Technical Review 287

Technical Review Software Review Process Engineering 287

Scrum.org

APRIL 11, 2022

Otherwise, the Scrum team should invest in a workshop on writing better Product Backlog items.). Due to a lack of refinement, it is likely to leave a lot of value on the table. What technical debt? The Developers do not demand adequate time to tackle technical debt and bugs and preserve the quality standard of the product.

Technical Review 252

Technical Review SCRUM Lean Agile 252

NimbleWork

OCTOBER 21, 2024

Top 25 Project Management Influencers Elizabeth Harrin With over 20 years of experience as a seasoned project manager, Elizabeth Harrin has made a name for herself as both a project leader and an educator, lending her expertise to prominent technology companies.

2025 111

2025 Influencer Technical Review Underperforming Technical Team 111