Remove Article Remove Conference Remove Process Remove Technical Review
article thumbnail

Everything You Need to Know About Release Managers

Rebel’s Guide to PM

It wasn’t until I worked in IT as a project manager that I had a lot of contact with the release management process. My software projects needed releasing, so we had to follow the formal process and engage with the release manager to make sure that the bug fixes and new features got pushed to the production environment in a controlled way.

article thumbnail

Industry, Product, and Technical Knowledge: What Makes a Project Manager an Expert?

Epicflow Blog

And in this publication, we discuss the role of industry, product, and technical knowledge in the work of a project manager. . Industry knowledge implies the understanding of the sector’s specificity, processes, regulations, job responsibilities, market trends, and things alike. . Production Processes.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

The Evolution of Project Management

The IIL Blog

and Cynthia Snyder Dionisio, MBA, PMP We have all attended project management workshops, conferences, and symposiums. We have read books and journal articles on various project management topics. First, the PM was expected to possess a command of technology rather than merely an understanding of technology.

Aerospace 147
article thumbnail

What’s the big deal about the Definition of Done in Scrum?

Scrum.org

Others may think a code review is needed before the work can be considered done. At the Sprint Review event, progress towards the Product Goal is discussed. Prevents the accumulation of additional technical debt. Technical Debt refers to Developers' decisions to trade quality for speed. Improves product quality.

article thumbnail

The Scrum Master Balancing Act

Scrum.org

This article explores the challenges faced by Scrum Masters in their balancing act and how they navigate through it to ensure effective team performance and continuous improvement. Each team operates within a unique context, encompassing factors like team size, domain, technology, culture, and the nature of the products they develop.

SCRUM 144
article thumbnail

Prioritization techniques for the Product Owner

Scrum.org

In this article, we will explore some complimentary practices which the Product Owner might use to as an input when deciding how to order the Product Backlog. The complimentary practices below can help bring clarity to your thought process and can be used to potentially involve stakeholders in the process as well.

article thumbnail

The Scrum Master Job (1): 4 Steps to Identify Suitable Employers or Clients

Scrum.org

Shall I notify you about articles like this one? 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. You can sign up here for the ‘Food for Agile Thought’ newsletter and join 29k other subscribers.

SCRUM 197