Agile Pain Relief Notes from a Tool User
MARCH 13, 2020
The Scrum Guide offers very limited guidance, suggesting 3-9 people per team (exclusive of ScrumMaster and Product Owner), without giving reasons or context for those numbers. While this is primarily about Scrum, the lessons are applicable for any work that is collaborative and knowledge-based. My Experience.
CIO
FEBRUARY 26, 2024
The early 2010’s practice of co-locating talent supercharged collaboration, but also limited organizations’ ability to scale with a workforce based in high-density, cost-prohibitive metros. with Scrum Masters and engineering teams in the alternative location. they were fully empowered to build the global product for all users.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Gorilla Logic
SEPTEMBER 11, 2020
Although there are many Agile certification bodies, the most recognized and highly regarded organizations (as of September 2020) include: • Scrum Alliance (founded in 2001) . Project Management Institute (founded in 1969) . • International Consortium of Agile (founded in 2010) . Product owner or product manager.
Cory Foy
MARCH 2, 2020
Recreating Scrum using Kanban and Explicit Policies. November 2010. September 2010. August 2010. April 2010. March 2010. February 2010. January 2010. Product Development. product management. Contact him today at foyc at cory foy dot com! Simple Design with Design Patterns.
LeanEssays
DECEMBER 23, 2010
“We’re really struggling with the Product Owner concept, and many of our Scrum teams just don’t feel very productive.” The company had several vertical markets, with a Scrum team of about ten people assigned to each market. Each market had a Product Manager, a traditional role found in most product companies.
LeanEssays
JULY 14, 2019
The most important findings in the book were: The development processes of high performing companies focused on fast time-to-market, excellent product quality, and high engineering productivity (i.e. Scrum [20] introduced iterations. Kanban [21] improved flow management by limiting work-in-process.
LeanEssays
JUNE 5, 2015
Thus lean software development might be considered a subset of lean product development; certainly the principles that underpin lean product development are the same principles that form the basis of lean software development. During its first decade, agile development moved from a radical idea to a mainstream practice.
Expert insights. Personalized for you.
117 
Let's personalize your content