Remove 2011 Remove Development Team Review Remove Presentation Remove Process
article thumbnail

A Beginner’s Guide to Scrum Ceremonies

ProjectManager.com

Scrum ceremonies are meetings that are unique to scrum teams. Scrum ceremonies ensure that everyone (the scrum master, product owner and development team) is in-sync. A sprint employs four different scrum ceremonies to ensure proper execution: sprint planning, daily scrum, sprint review and sprint retrospective.

SCRUM 203
article thumbnail

In-Depth: How To Create Better Work Agreements For Your Team

Scrum.org

Work agreements are basically team-agreed expectations on how you will behave, interact and deal with certain scenarios. Some find the process of creating them “childish” or “a waste of time”. Note that we’re using functional job titles here for clarity; not all companies use them, and the Scrum Guide only talks about “developers”.

2004 230
Insiders

Sign Up for our Newsletter

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

article thumbnail

Scrum Methodology: Roles, Events & Artifacts

ProjectManager.com

The scrum methodology was developed as a response to rigid project management approaches such as the waterfall method, which didn’t adapt to the needs of agile product and software development teams. For this purpose it defines three roles, a scrum master, a product owner and a development team, made up of several team members.

SCRUM 338
article thumbnail

My Journey as a Scrum Master

Scrum.org

The ultimate corporate Application & Process Management path, or so I thought. Negotiating with suppliers, managing expectations of stakeholders, checking the progress with the developers, dealing with management. To challenge myself even further, I signed up for doing a presentation at Scrum Day London. Scrum Master & Trainer.

SCRUM 117
article thumbnail

The Project Communication Plan

MPUG

The legal department gets involved only to work on contracts or to review documents for legal issues. For example, vendors, suppliers, partners, and the project managers who work for them can belong to your core team. For example, sales and marketing might want to know what the product features are and when it’ll be ready to sell.

article thumbnail

In-Depth: Stable Or Fluid Teams? What Does The Science Say?

Scrum.org

The need for fluid teams. The notion of fluid teams has been around for a long time, mostly in aviation, healthcare, and the armed forces. Bushe and Chu (2011) identify seven situations that drive the use of fluid teaming in those environments: High turnover among employees, leading to changes in teams. Bradley et.

article thumbnail

Kanban to manage Complex/ Quick Moving Situations

Digite

Also, we have quite diverse roles in the team (i.e., In the usual Scrum process, the P.O. Starting in 2007 when we moved from being a waterfall shop to 2011 when we adopted Kanban, we have ourselves mastered a number of challenges that the question above presents. Dev Lane for the main dev activity.