This document discusses the importance of writing good requirements in project management, detailing quality characteristics and criteria for effective requirements. It provides examples of poor requirements and offers strategies for improving them, such as using templates and adhering to established standards. Additionally, it emphasizes the significance of avoiding redundancy, inconsistency, and ensuring proper structure in work products.
The document outlines the process of building a test strategy, detailing its essential components such as context, stakeholders, goals, and the various activities involved in testing. It emphasizes the importance of tests in achieving organizational objectives and includes references to numerous testing artifacts and standards. Additionally, it provides a structure for managing testing processes, including risk analysis, test planning, and evaluation metrics.
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 the evolving role of business analysts (BAs) in the context of agile methodologies and digital transformation, highlighting the need for a multidisciplinary approach and the integration of various competencies. It critiques traditional BAs responsibilities and emphasizes the importance of delivering value, adapting to market expectations, and overcoming challenges in communication between business and technology. The piece underscores the shift towards a more agile, rapid developmental process that enhances team dynamics and stakeholder engagement.
The document discusses the transformation of quality management in the context of agile methodologies, highlighting the challenges of integrating traditional quality management approaches with agile practices. It outlines issues related to project scope, work efficiency, and communication within agile teams, and suggests that quality management and agile can coexist effectively. The author emphasizes the importance of a modern quality management strategy that supports a multidisciplinary and value-driven process.
Traceability - ways to ensure better management and consistency_HUSTEFKAROLINA ZMITROWICZ
油
The document discusses the importance of traceability in managing complexity within projects, emphasizing the need for understanding information requirements, relationships between artifacts, and proper structuring. It highlights various aspects such as change impact analysis, coverage analysis, and the maintenance of traceability over time. The key to effective traceability lies in aligning business goals, requirements, and test cases throughout the project lifecycle.
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
Simple Ways of Planning, Designing and Testing Usability of a Software Produc...KAROLINA ZMITROWICZ
油
The document discusses the importance of usability in software design, emphasizing that a product must be user-friendly to be effective. It outlines strategies for planning, designing, and testing usability, including user involvement and iterative design methods. Additionally, it highlights the significance of understanding user needs and measuring usability through various methods and tools.
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.
Business awareness of testers and the quality of testing KAROLINA ZMITROWICZ
油
The document discusses the essential skills needed to be an effective tester, emphasizing the importance of both technical knowledge and soft skills, such as communication and negotiation. It highlights the necessity for testers to understand business requirements, as poorly documented or inconsistent requirements can lead to costly errors in software development. Solutions include collaborating with business analysts and involving customers in the testing process to ensure the development of the right product.
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
Simple Ways of Planning, Designing and Testing Usability of a Software Produc...KAROLINA ZMITROWICZ
油
The document discusses the importance of usability in software design, emphasizing that a product must be user-friendly to be effective. It outlines strategies for planning, designing, and testing usability, including user involvement and iterative design methods. Additionally, it highlights the significance of understanding user needs and measuring usability through various methods and tools.
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.
Business awareness of testers and the quality of testing KAROLINA ZMITROWICZ
油
The document discusses the essential skills needed to be an effective tester, emphasizing the importance of both technical knowledge and soft skills, such as communication and negotiation. It highlights the necessity for testers to understand business requirements, as poorly documented or inconsistent requirements can lead to costly errors in software development. Solutions include collaborating with business analysts and involving customers in the testing process to ensure the development of the right product.
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
Szkoy G坦wnej Handlowej
Alumni PWC Business Coaching Diploma
Absolwentka Studium Trener坦w Grupowych
Laboratorium Psychoedukacji przy SWPS
Mentorka Sieci Przedsibiorczych Kobiet
Prezeska IIBA Poland Chapter
Jedna z pierwszych os坦b w Polsce, kt坦ra
uzyskaa certy鍖kacj IIBA
Dumna posiadaczka certy鍖kat坦w: ECBA,
CCBA, CBAP, AAC, CPOA, CBDA
3. Kim jestem?
Absolwentka ZUT
Analityk biznesowy i mened甜er jakoci z
zawodu i zamiowania
Wykadowca akademicki
Autorka kilku ksi甜ek i licznych publikacji
Obecna funkcja: czonek zarzdu IREB
(International Requirements Engineering
Board)
Penia funkcje:
Prezes zarzdu SJSI
Prezes zarzdu ISTQB
Lider grup roboczych IREB oraz TMMi w
SJSI
Czonek 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