Scrum.org
SEPTEMBER 23, 2019
The first article of this series will address the Scrum Master engagement with the Development Team. Scrum Master Engagement with the Development Team. Following this layout, there are three main scenarios for the Scrum Master’s support of the team: The Co-located, Stable Scrum Team Scenario.
Scrum.org
APRIL 7, 2022
The professional literature around fluid teaming tends to conceptualize it as a necessary response to the reality that no team is actually stable. Team cognition is similar in the sense that the entire team can be thought of as a body, where each member (the limbs) has to learn how to coordinate their work effectively to move forward.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Planio
MAY 22, 2023
Review your product backlog and rank features 5. Release too often, and you risk overwhelming your users. For example, when Airbnb launched in 2008, its product vision might have been: “In 5 years, Airbnb will be the more affordable and enjoyable way to plan a trip.” Consider your organization’s release capability (i.e.,
MPUG
MARCH 28, 2021
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.
Herding Cats
APRIL 16, 2019
Business, Technical, Systems, Risk, and Project Management Briefings and Presentations. Risk Management (#RM). The following material comes from conferences, workshop, materials developed for clients. Business, Technical, Systems, Risk, and Project Management. Table of Contents (Click the Name to go to Section).
Agilemania
MARCH 22, 2021
With traditional plans, you’ll always have the risk of delayed product delivery. Although introduced in 1986 by Hirotaka Takeuchi and Ikujiro Nonaka through paper, they published (New New Product Development Game) and followed by agile manifesto in 2001. Reviews and approvals. Agile success rates are 1.5X Low involvement.
Teamweek
JUNE 25, 2020
Asana was founded in 2008 by ex-Google and ex-Facebook engineers with the aim to make team collaboration better. Most creative team managers are neither trained, not need to be. Here’s a review from SoftwareAdvice that sums up the frustration that teams have Asana. Particularly, for small teams.
Expert insights. Personalized for you.
135 
Let's personalize your content