Presentation discussed during the IREB roundtable How to Write good Requirements with Sylwia Kopczyńska and Karolina Zmitrowicz, moderation Stan Buhne.
During the roundtable we had a lively discussion with Requirements Engineering experts Karolina and Sylwia, who gave many insightful points on how to write good requirements. Some points that were discussed included the importance of writing good requirements, their quality criteria and which are most common, examples for good and bad requirements, and standards for requirements specification.
Recording available on YouTube https://youtu.be/m_JFdblX4KU
The document discusses improving testing organizations through adopting the Test Maturity Model Integration (TMMI). It notes that organizations often struggle with issues like poor communication, lack of work standards, and quality problems. The TMMI model provides a structured framework of process areas and practices that can help build an effective testing approach. The case study describes how one organization used TMMI at levels 2-4 to implement tools like Confluence and JIRA, establish a knowledge base, and define requirements, test cases, and reporting processes. Adopting the TMMI model helped solve their challenges and build better quality.
The document discusses quality assurance for requirements in agile projects. It covers characteristics of good user stories, acceptance criteria, and quality gates. User stories should follow INVEST criteria - be independent, negotiable, valuable, estimable, small, and testable. Acceptance criteria and scenarios define when a story is complete. Quality gates ensure requirements and stories meet definitions of ready and done before development and release. Reviews like backlog grooming and three amigos meetings aid quality.
Presentation discussed during the IREB roundtable How to Write good Requirements with Sylwia Kopczyńska and Karolina Zmitrowicz, moderation Stan Buhne.
During the roundtable we had a lively discussion with Requirements Engineering experts Karolina and Sylwia, who gave many insightful points on how to write good requirements. Some points that were discussed included the importance of writing good requirements, their quality criteria and which are most common, examples for good and bad requirements, and standards for requirements specification.
Recording available on YouTube https://youtu.be/m_JFdblX4KU
The document discusses improving testing organizations through adopting the Test Maturity Model Integration (TMMI). It notes that organizations often struggle with issues like poor communication, lack of work standards, and quality problems. The TMMI model provides a structured framework of process areas and practices that can help build an effective testing approach. The case study describes how one organization used TMMI at levels 2-4 to implement tools like Confluence and JIRA, establish a knowledge base, and define requirements, test cases, and reporting processes. Adopting the TMMI model helped solve their challenges and build better quality.
The document discusses quality assurance for requirements in agile projects. It covers characteristics of good user stories, acceptance criteria, and quality gates. User stories should follow INVEST criteria - be independent, negotiable, valuable, estimable, small, and testable. Acceptance criteria and scenarios define when a story is complete. Quality gates ensure requirements and stories meet definitions of ready and done before development and release. Reviews like backlog grooming and three amigos meetings aid quality.
About modeling, good modeling and methods of modeling allowing to ensure complete, consistend and usable information model. Presented originally at http://requirements.org.pl/seminaria2017/modelarskie.html
Kilka słów o zarządzaniu jakością - od planowania, po optymalizację/Few information about quality management - starting from planning, to optimization.
Simple Ways of Planning, Designing and Testing Usability of a Software Produc...KAROLINA ZMITROWICZ
Originally presented at QS-Tag 2016
https://www.qs-tag.de/en/abstracts/tag-1/simple-ways-of-planning-designing-and-testing-usability-of-a-software-product/
The document discusses the importance of usability engineering and designing for usability from the beginning. It provides definitions of usability and outlines the key steps in the usability engineering process, including concept planning, understanding needs, requirements analysis, and design/development. Throughout each step, it emphasizes applying best practices like user research, prototyping, and usability testing to prevent usability problems and ensure products are easy to use.
Minimize the project risk - build good business requirementsKAROLINA ZMITROWICZ
The document discusses the importance of writing good business requirements for minimizing project risk. It notes that the real problems with many IT projects stem from a lack of proper analysis and preparation, with requirements often not clearly defined or tied to business goals and values. The document provides guidance on best practices for writing business requirements, including quantifying requirements, focusing on stakeholder needs and system qualities rather than just functions, ensuring "rich specification" that provides important background context for each requirement, and carrying out quality control checks of requirements.
About modeling, good modeling and methods of modeling allowing to ensure complete, consistend and usable information model. Presented originally at http://requirements.org.pl/seminaria2017/modelarskie.html
Kilka słów o zarządzaniu jakością - od planowania, po optymalizację/Few information about quality management - starting from planning, to optimization.
Simple Ways of Planning, Designing and Testing Usability of a Software Produc...KAROLINA ZMITROWICZ
Originally presented at QS-Tag 2016
https://www.qs-tag.de/en/abstracts/tag-1/simple-ways-of-planning-designing-and-testing-usability-of-a-software-product/
The document discusses the importance of usability engineering and designing for usability from the beginning. It provides definitions of usability and outlines the key steps in the usability engineering process, including concept planning, understanding needs, requirements analysis, and design/development. Throughout each step, it emphasizes applying best practices like user research, prototyping, and usability testing to prevent usability problems and ensure products are easy to use.
Minimize the project risk - build good business requirementsKAROLINA ZMITROWICZ
The document discusses the importance of writing good business requirements for minimizing project risk. It notes that the real problems with many IT projects stem from a lack of proper analysis and preparation, with requirements often not clearly defined or tied to business goals and values. The document provides guidance on best practices for writing business requirements, including quantifying requirements, focusing on stakeholder needs and system qualities rather than just functions, ensuring "rich specification" that provides important background context for each requirement, and carrying out quality control checks of requirements.
2. Kim jestem?
● Absolwentka Politechniki Warszawskiej i
Szkoły Głównej Handlowej
● Alumni PWC Business Coaching Diploma
● Absolwentka Studium Trenerów Grupowych
Laboratorium Psychoedukacji przy SWPS
● Mentorka Sieci Przedsiębiorczych Kobiet
● Prezeska IIBA Poland Chapter
● Jedna z pierwszych osób w Polsce, która
uzyskała certyfikację IIBA
● Dumna posiadaczka certyfikatów: ECBA,
CCBA, CBAP, AAC, CPOA, CBDA
3. Kim jestem?
● Absolwentka ZUT
● Analityk biznesowy i menedżer jakości z
zawodu i zamiłowania
● Wykładowca akademicki
● Autorka kilku książek i licznych publikacji
● Obecna funkcja: członek zarządu IREB
(International Requirements Engineering
Board)
● Pełniła funkcje:
○ Prezes zarządu SJSI
○ Prezes zarządu ISTQB
○ Lider grup roboczych IREB oraz TMMi w
SJSI
○ Członek grup roboczych w Ministerstwie
Cyfryzacji
7. IREB
Who IREB is
IREB, the International Requirements Engineering
Board, a non-profit organization, is the provider of
the CPRE (Certified Professional for Requirements
Engineering) certification scheme. The board
consists of leading RE representatives, who come
from science, research, industry and consulting.
The IREB association is composed of
● Full Members,
● Associate Members,
● Honorary Members.
Articles of Association IREB e. V.
Deeplink: https://www.ireb.org/en/downloads/#articles-of-association