Scrum is an agile framework for managing product development projects. It utilizes short "sprints" where self-organizing cross-functional teams work to deliver increments of a product. Scrum roles include the Product Owner who represents stakeholders, the Development Team who does the work, and the Scrum Master who facilitates the process. Scrum ceremonies like daily stand-ups, sprint reviews and retrospectives provide visibility and opportunities to inspect and adapt the process as needed.
Many organizations are using JIRA for issue tracking – incident, service request, problem and change management, as well as for project management. However, JIRA can also be used as a tool for test management.
Presentation was given on TAPOST 2012: http://www.itbaltic.com/en/conferences/tapost-2012/
The document discusses software testing concepts including:
1. It defines key terms related to software defects such as errors, defects, failures, and faults.
2. It outlines the different phases of software testing from component/unit testing to acceptance testing and discusses principles of good testability.
3. It provides guidance on writing test plans and cases, including reviewing requirements, identifying test suites, and transforming use cases into test cases.
ISO 29110 Software Quality Model For Software SMEsMoutasm Tamimi
ISO 29110 model in 2017
Systems and Software Life Cycle Profiles and Guidelines for Very Small Entities (VSEs) International Standards (IS) and Technical Reports (TR) are targeted at Very Small Entities (VSEs). A Very Small Entity (VSE) is an enterprise, an organization, a department or a project having up to 25 people. The ISO/IEC 29110 is a series of international standards entitled "Systems and Software Engineering — Lifecycle Profiles for Very Small Entities (VSEs)"
ISO/IEC 15504, also known as SPICE, is an international standard for software process assessment. It defines a framework for assessing processes based on a process reference model and capability levels. Processes are divided into categories and each process is assessed against attributes to determine its capability level on a scale of 0 to 5. ISO/IEC 15504 provides guidelines for conducting assessments through steps like planning, data collection, and reporting results. Assessors require training and experience to perform assessments competently. The standard can be used for both process improvement and determining a supplier's process capabilities.
Scrum is an agile framework for managing product development projects. It utilizes short "sprints" where self-organizing cross-functional teams work to deliver increments of a product. Scrum roles include the Product Owner who represents stakeholders, the Development Team who does the work, and the Scrum Master who facilitates the process. Scrum ceremonies like daily stand-ups, sprint reviews and retrospectives provide visibility and opportunities to inspect and adapt the process as needed.
Many organizations are using JIRA for issue tracking – incident, service request, problem and change management, as well as for project management. However, JIRA can also be used as a tool for test management.
Presentation was given on TAPOST 2012: http://www.itbaltic.com/en/conferences/tapost-2012/
The document discusses software testing concepts including:
1. It defines key terms related to software defects such as errors, defects, failures, and faults.
2. It outlines the different phases of software testing from component/unit testing to acceptance testing and discusses principles of good testability.
3. It provides guidance on writing test plans and cases, including reviewing requirements, identifying test suites, and transforming use cases into test cases.
ISO 29110 Software Quality Model For Software SMEsMoutasm Tamimi
ISO 29110 model in 2017
Systems and Software Life Cycle Profiles and Guidelines for Very Small Entities (VSEs) International Standards (IS) and Technical Reports (TR) are targeted at Very Small Entities (VSEs). A Very Small Entity (VSE) is an enterprise, an organization, a department or a project having up to 25 people. The ISO/IEC 29110 is a series of international standards entitled "Systems and Software Engineering — Lifecycle Profiles for Very Small Entities (VSEs)"
ISO/IEC 15504, also known as SPICE, is an international standard for software process assessment. It defines a framework for assessing processes based on a process reference model and capability levels. Processes are divided into categories and each process is assessed against attributes to determine its capability level on a scale of 0 to 5. ISO/IEC 15504 provides guidelines for conducting assessments through steps like planning, data collection, and reporting results. Assessors require training and experience to perform assessments competently. The standard can be used for both process improvement and determining a supplier's process capabilities.
Goals of the presentation:
* to analyze the AutomotiveSPICE process scopes and measurement purposes
* to discuss the measures that can be adopted in an Automotive project
* to propose a possible \'top metrics\' scope and boundary for SPICE-compliant projects
[See also www.automotive-spin.it]
A proposal for a new common process scope for AutomotiveSPICE: Six reasons fo...Luigi Buglione
The presentation introduced the rationale by six reasons why adding the MAN.6 process in an ISO/IEC 15504 assessment could bring several advantages to an organization, whatever the application domain
Mapping Automotive SPICE: Achieving Higher Maturity & Capability LevelsLuigi Buglione
As usual, when planning to improve a process, an organization needs to compare the current version (‘as-is’) with the new, desired one (‘to-be’). The possible content for such improvement comes from comparisons and mappings with similar processes kept from different sources. In the ICT arena such kind of studies are quite frequent but not always done for covering all models, for instance in the Automotive field. Again, often such comparisons have been done between not directly comparable elements (e.g. any management system standard as ISO 9001 is a requirement model, while maturity models such as CMMI or ISO/IEC 15504 represent process meta-models, with a different aim and contents). The aim of this presentation is to provide a new mapping between AutomotiveSPICE (A-SPICE) and the ISO 9001 norm for the Automotive sector (ISO/TS 16494:2009). This new mapping could be to provide tips for giving contents to ISO clauses but directly from A-SPICE, for more valuable improvement projects.
Automotive SPICE® 3.0 - What is new and what has changed?Dominik Strube
With our presentation "Automotive SPICE® 3.0 - What is new and what has changed?" you will know the changes implemented in the new version of Automotive SPICE® v3.0. This is provided free of charge.
This presentation has been created by leading intacsTM SPICE principal assessors. Please feel free to share this documentation among your colleagues, as long as the content is not altered.
This document provides an overview of ISO/IEC 15504 (SPICE) and its current and future directions. It discusses the parts and concepts of ISO/IEC 15504, including capability levels, process assessment models, organizational maturity, and standards-based and sector-based models. It also outlines the ISO study group revision from 2009-2011, the evolution and transition of SPICE, and the formation of the SPICE Academy.
This document provides instructions for installing and configuring authentication for Git. It outlines how to install Git on Linux, OS X, and Windows operating systems. It also describes how to generate SSH keys for authentication on Linux, OS X, and Windows. Finally, it explains how to set up the SSH configuration file and test the key connection.
The document discusses the structure and components of the New M-Culture system. It describes the core engine, use of themes and plugins for customization, and integration with other systems. Key elements include a system structure built on CodeIgniter, a core engine, themes and plugins for custom content, and integration with services for cultural information and analysis.
The document discusses architectural test case writing. It begins by covering software development methodologies like waterfall and iterative models. It then discusses software testing, particularly architectural testing. Key aspects of architectural test cases are described such as using quality attributes to derive scenarios and test cases. An example scenario and test case template are provided. The document emphasizes that architectural test cases should validate quality attributes and non-functional requirements.
This document provides an introduction to using Subversion for document version control. It discusses the advantages of version control like backup/restore, synchronization, and tracking changes. It defines common version control terms and concepts. It then demonstrates how to perform basic Subversion actions like checking out a file, adding a new file, updating files, committing changes, and viewing diffs between revisions. It also covers more advanced topics like branching and merging through examples.