CoPs | Glossary

Definition:

CoPs stands for Communities of Practice, an organised groups of people who share common interest in a particular domain or area creating an opportunity to learn from each other to develop personally and professionally.

Here learning occurs in social context that emerge and evolve when people having common goals interact as they strive towards their goals. This concept is credited to Jean Lave and Etienne Webger, who referred to the communities of practitioners where newcomers would enter and attempt to learn the sociocultural practices of the community. These practices were associated with knowledge management as people begun to see them as ways of developing social capital, nurturing new knowledge, stimulating innovation or sharing existing tacit knowledge within an organisation which is accepted as a part of organisational development.

CoPs plays a crucial part in scaling agility, and this makes it a part of SAFe framework. CoPs are highly organic, informal networks designed specifically for efficient knowledge sharing and exploration across teams, trains and the entire organisation. Role based Communities of Practices to name a few are PO/PMs, Scrum Master’s, Developers, UX Designers or Systems Engineers CoPs.

 

Further Reading:

https://en.wikipedia.org/wiki/Community_of_practice
http://www.innovativelearning.com/teaching/communities_of_practice.html
https://www.scaledagileframework.com/communities-of-practice/

Built-In Quality | Glossary

Definition:

Built-in quality is one of the SAFe Core Values, it is a core principle of the Lean-Agile Mindset.

Edwards Deming states “Inspection does not improve the quality, nor guarantee quality. Inspection is too late. The quality, good or bad, is already in the product. Quality cannot be inspected into a product or service; it must be built into it.”

Lean manufacturing companies have quality build in their process, preventing unnecessary rework and waste generation. In essence, this practice is the pillar of controlling variables within a process, securing quality not passing on poor quality and checking every piece. Software, hardware also ensures that each solution, at every increment, meets appropriate quality standards throughout the development. One of the Agile Principles says on quality “Continuous attention to technical excellence and good design enhances agility” which ensures that the solutions built are high in quality, can rapidly adapt to change and are architected for testing, deployment and recovery.

Product qualities such as expandability, flexibility, integrity, interoperability, maintainability, portability, reusability, resilience and usability in general cannot be inspected or tested. They must be “designed in” brought in early phases of development during requirement capture, analysis, architecting and design. This induce “Built-in Quality” during design process weighed against user’s needs in a iterative feedback loop.

Further Reading:

Book: Quality is Free: The Art of Making Quality Certain by Philip B. Crosby
https://www.scaledagileframework.com/built-in-quality/
http://agilemanifesto.org/principles.html
http://www.qsm.com/quality1.pdf