Agile Pain Relief Notes from a Tool User
MARCH 12, 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.
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.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Agile Pain Relief Notes from a Tool User
MARCH 12, 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.
Evolution4all
APRIL 29, 2019
Blogs mostly focused on personal or collective reflections and opinions, while wikis are an open source and searchable knowledge base about various niches and topics. Despite their differences, both types of web-based collaboration software serve the purpose of collecting and collating information that may offer value to a community.
Evolution4all
APRIL 30, 2019
Now it can be a community of Product Owners looking for a new approach to work with their Scrum Teams or a network of Developers sharing their new scripts to automate their work. Without going extra technical with it, CoPs are self-organising learning bodies capable of growing the knowledge capital of your company.
Evolution4all
APRIL 26, 2019
The company has what it’s called “ engine high performance CoP ” which aim to develop and share technical knowledge among 150 car engineers. Just like a typical CoP, members meet and interact on a regular basis, discussing issues and collaborating to build a knowledge base on how to build more reliable and better-performing car engines.
Evolution4all
APRIL 30, 2019
In the long term, a systematic collection of knowledge should be built which members can easily access. This can be in the form of proceedings, wikis, knowledge-base, internal company blogs, and archives. As your company CoPs continuously grow and evolve, so is the knowledge capital of your company.
Expert insights. Personalized for you.
102 
Let's personalize your content