The document discusses the workflows for work items in Microsoft Team Foundation Server (TFS). It defines roles like manager, developer, quality control, and end user. It describes the workflows for user stories, bugs, and tasks. User stories flow from active to resolved to closed. Bugs are prioritized by priority and severity. They flow from new to resolved after being fixed. Tasks support sub-tasks for user stories and bugs. The document proposes improvements like using TFS for email notifications and clarifying statuses.
Shirly Ronen - Documenting an agile defectAgileSparks
This document discusses best practices for documenting defects in an agile environment. It recommends documenting defects at a "just enough" level based on the type of defect and stage in the process. More detailed documentation is needed the further removed the defect reporter is from the developer fixing it. Defects should be traced to user stories and functionality, not modules. The focus should be on functional quality and backlog progress over a big defects list. Short, just-in-time discussions replace big bug meetings.
Shirly Ronen - User story testing activitiesAgileSparks
The document discusses testing user stories throughout the development process from planning through deployment. It emphasizes testing early by writing automated unit tests during development. Testers work closely with developers to understand the approach and test in the development environment. This helps find defects early and prevent issues. The goal is to deliver working software through continuous testing, including acceptance criteria, exploratory testing, automation, and regression testing.
Shirly Ronen - rapid release flow and agile testing-asAgileSparks
This document describes a rapid agile release flow with three types of releases:
1. CR or production change requests that upload user stories daily to production for testing without releasing to customers.
2. A business release that takes all CRs and makes them available internally but not yet to customers.
3. A station-customer release that releases a group of features to customers after preparations like documentation.
It discusses splitting production from customer releases, freezing user stories and code at different stages, and performing various tests during the process.
This document summarizes a keynote presentation about IBM's quality management products and strategies. The presentation discusses real challenges faced by development teams, real results achieved by IBM products in 2008, and real insights into improving quality management. It provides an overview of IBM's quality management portfolio and roadmap for continued enhancements.
Evidence-based software process recovery uses data from software repositories to understand the actual development process used by a team. This allows comparison of the proposed process with the recovered process. Topic modeling of commits can identify developer topics like reliability, maintainability, and portability over time. Release patterns showing activity in source code, tests, builds and documentation near releases can also be recovered. Process recovery provides an objective view of the actual development process.
How to go beyond traditional Scrum principles and scale to globally distributed teams with Continuous Delivery and Subversion. Presented by Andy Singleton of Assembla and Scott Rudenstein of WANdisco. Presented Nov. 15, 2012. 30 minutes.
The document discusses design for reliability (DFR) topics including the need for DFR, the DFR process, terminology, Weibull plotting, system reliability, DFR testing, and accelerated testing. It provides details on the DFR process, common reliability terminology such as reliability, failure rate, mean time to failure, and the bathtub curve. It also explains the exponential distribution and Weibull plotting, which are important reliability analysis tools.
Shirly Ronen - Documenting an agile defectAgileSparks
This document discusses best practices for documenting defects in an agile environment. It recommends documenting defects at a "just enough" level based on the type of defect and stage in the process. More detailed documentation is needed the further removed the defect reporter is from the developer fixing it. Defects should be traced to user stories and functionality, not modules. The focus should be on functional quality and backlog progress over a big defects list. Short, just-in-time discussions replace big bug meetings.
Shirly Ronen - User story testing activitiesAgileSparks
The document discusses testing user stories throughout the development process from planning through deployment. It emphasizes testing early by writing automated unit tests during development. Testers work closely with developers to understand the approach and test in the development environment. This helps find defects early and prevent issues. The goal is to deliver working software through continuous testing, including acceptance criteria, exploratory testing, automation, and regression testing.
Shirly Ronen - rapid release flow and agile testing-asAgileSparks
This document describes a rapid agile release flow with three types of releases:
1. CR or production change requests that upload user stories daily to production for testing without releasing to customers.
2. A business release that takes all CRs and makes them available internally but not yet to customers.
3. A station-customer release that releases a group of features to customers after preparations like documentation.
It discusses splitting production from customer releases, freezing user stories and code at different stages, and performing various tests during the process.
This document summarizes a keynote presentation about IBM's quality management products and strategies. The presentation discusses real challenges faced by development teams, real results achieved by IBM products in 2008, and real insights into improving quality management. It provides an overview of IBM's quality management portfolio and roadmap for continued enhancements.
Evidence-based software process recovery uses data from software repositories to understand the actual development process used by a team. This allows comparison of the proposed process with the recovered process. Topic modeling of commits can identify developer topics like reliability, maintainability, and portability over time. Release patterns showing activity in source code, tests, builds and documentation near releases can also be recovered. Process recovery provides an objective view of the actual development process.
How to go beyond traditional Scrum principles and scale to globally distributed teams with Continuous Delivery and Subversion. Presented by Andy Singleton of Assembla and Scott Rudenstein of WANdisco. Presented Nov. 15, 2012. 30 minutes.
The document discusses design for reliability (DFR) topics including the need for DFR, the DFR process, terminology, Weibull plotting, system reliability, DFR testing, and accelerated testing. It provides details on the DFR process, common reliability terminology such as reliability, failure rate, mean time to failure, and the bathtub curve. It also explains the exponential distribution and Weibull plotting, which are important reliability analysis tools.
Creator: Joel Champagne, President of CodeX Enterprises
This presentation covers various issues associated with SQL unit testing. We’ll look at end solutions in demo form using Visual Studio 2010 and other third party tools.
You'll learn:
* The value of pursuing SQL testing, early and continually in the development cycle
* Capabilities in Visual Studio 2010 to support SQL unit testing
* Capabilities in other tools to support SQL unit testing
San Jose Selenium Meetup 22 Mar 2012: The Restless Are Getting NativeDante Briones
Are you wondering how to write automated tests for your shiny new iOS application? Is it even possible? Maybe you're sick of manually running the same test scenarios over and over and over… are you developing blisters on your fingertips?
In his talk, Dante Briones--Principal Consultant for Cochiva--will give a broad overview of the automated testing tools currently available for iOS, and share some hard-won secrets of iOS app test automation using NativeDriver -- an implementation of the WebDriver API that can drive *native* applications running on iOS or Android. You'll see how to integrate NativeDriver into your iOS app, allowing you to write functional tests in Java. You'll learn how to execute those tests at the command line and how to integrate those tests into a continuous integration tool like Jenkins. You'll hear lots of tips about how to improve your chances for a successful adoption of a functional testing suite.
Parasoft Concerto A complete ALM platform that ensures quality software can b...Engineering Software Lab
Parasoft Concerto is a complete software development management platform that ensures quality software can be produced consistently and efficiently–in any language.
By integrating policy-driven project management with Parasoft Test's quality lifecycle management as well as Parasoft Virtualize's dev/test environment management, Parasoft Concerto ensures predictable project outcomes while driving unprecedented levels of productivity and application quality.
Releasing fast code - The DevOps approachMichael Kopp
Agile makes you Develop faster, DevOps also makes you Deploy faster but how do you make your Application faster?
Many currently used Performance Management practices don’t work anymore as they are too time consuming. It takes a new approach to track performance in Continuous Integration, get more value out of Load Testing and leverage production data for performance optimization.
We will show you real world examples on how the new DevOps approach can work.
THE FUTURE OF LEED ENERGY MODELING IS HERE!! IES VE-Navigator for ASHRA E 90.1gautamsauraj
The document describes a new tool called VE-Navigator for ASHRAE 90.1 that was designed to streamline and speed up the LEED energy calculation and submission process. It allows users to automatically create baseline models, size HVAC systems, run simulations, and generate reports formatted for submission. According to testimonials, it reduces the time to complete ASHRAE 90.1 PRM calculations by 45% and enables more accurate modeling with less human error. The tool is part of a suite of performance analysis software that can also analyze other LEED credits and is available for trial in December 2010.
Scaling Continuous Integration Practices to Teams with Parallel DevelopmentIBM UrbanCode Products
Slides from an Urbancode and Accurev joint webinar: http://www.accurev.com/webinar/20120119-Scaling-CI-Parallel-Development
Continuous integration is simple with a single development team. But when software projects grow to multiple teams and dependencies, continuous integration loses effectiveness due to parallel projects, varying release schedules, and differing cadences between teams. As a result, many teams unknowingly lose the benefits of continuous integration, and therefore suffer from a lack of feedback and poor quality.
In this webinar, UrbanCode’s Eric Minick and AccuRev’s Chris Lucca will explain how to:
- Scale continuous integration builds across multiple development teams working on parallel projects
- Share only code that has passed continuous integration from other teams to avoid broken builds and confusion
- Automate the configuration of your test environment to handle fluid projects done in parallel
The document discusses test-driven PL/SQL development and best practices for error management. It covers defining requirements, writing unit tests, handling exceptions, and logging errors consistently. Key aspects include using pre-defined exception types and handlers, avoiding direct error raising/handling in application code, and following standards for error messaging.
App Dynamics & SOASTA Testing & Monitoring Converge, March 2012SOASTA
Dan Bartow, VP Performance Engineering, SOASTA and Steve Burton, Technology Evangelist, AppDynamics discuss the convergence of two traditionally separate domains and also demo testing and troubleshooting with CloudTest & AppDynamics.
1) The document discusses software testing strategies including improving test design, automation, understanding development processes, and leveraging APIs.
2) It also discusses tactics for team development including understanding customer pains, resolving issues, and contributing to forums and documentation.
3) Finally, it outlines processes for pre-integration testing including expectations for success/failure emails and general product qualification testing.
The document discusses Nicolas De Loof's background and experience in the Java and open source software communities. It then provides an overview of what a software factory is and lists its typical components. The document discusses choosing Git and Maven as version control and build tools respectively, and Jenkins as the automation and continuous integration tool. It then discusses using a platform-as-a-service model rather than on-premises containers to host the software factory components.
The document describes Unosquare's delivery centers located across the United States and Mexico, which provide services such as software development, QA testing, and project management using agile methodologies and tools. It highlights benefits like lower costs, ease of collaboration due to proximity, and cultural similarities that make working with the Mexico delivery center attractive. Sample metrics are also provided showing the company's testing capabilities.
The document discusses STMicroelectronics' deployment of functional qualification methodologies using Certitude mutation analysis. It outlines ST's initial engagement with Certess in 2004 and how they have expanded usage of the technology to now cover 80% of ST's IPs. The document also provides details on ST's functional qualification methodology, sharing of best practices, detection strategies used, and two case studies on measuring quality of third-party IPs and detecting issues in a video codec design.
This document provides an overview of test design and management concepts in the context of an IFDK reference product. It discusses different testing levels including unit, integration, system and acceptance testing. It describes the V-model for verification and validation. Requirements, test cases, test automation, and regression testing are also covered. Various testing techniques like black box, white box, code coverage and stubs are explained. The importance of test design and documentation is emphasized for effective testing.
Software can impact many aspects of society and is found almost everywhere. Common problems in software development include projects not fulfilling customer needs, being difficult to extend and improve, lacking documentation, and having poor quality. Software engineering aims to produce software on time, reliably, and completely by applying a systematic and disciplined approach.
These are the slides from my talk at the LESS 2011 conference in Stockholm, Sweden.
Product Ownership is a multi-faceted responsibility that demands a broad set of perspectives combined with deep product and domain knowledge. Effective product ownership requires both an internal and an external perspective. The challenges are amplified for large complex organizations developing large complex products and systems. In different organizations, engineering, product management, user experience and other functional groups can all lay claim to the role with some legitimacy.This talk will describe the challenges of understanding product ownership in large organizations, and of filling the product owner role effectively. We present different models for filling the product owner role, including single product owner, proxy product owner, and product owner teams.
Blue Monitor Systems is an employee-owned company dedicated to delivering high-quality creative, technical, and scientific services worldwide. The company encourages employees to think like owners and contribute to social well-being. Blue Monitor uses an iterative "Zero Time" method combining Agile and traditional approaches for medium and large projects. This includes continuous integration, test-driven development, and matrix project teams with specialists in design, engineering, testing, and operations.
Introducing Obsidian Software and RAVEN-GCS for PowerPCDVClub
Obsidian Software introduces RAVEN-GCS, a random test generator tool for processor verification that automatically generates assembly instructions to stimulate a microprocessor design, is customizable for any architecture, and helps reduce verification time and effort by focusing engineers on failing tests rather than creating directed test cases.
Tomas Riha presented on the principles and benefits of continuous delivery. Continuous delivery aims to have applications always ready for release through a highly automated process of continuous integration, testing, and deployment. It emphasizes automating all parts of the release process, building quality in from the start, and having all team members share responsibility for releases. Frequent releases allow for faster feedback and reduce risks from large code changes. Continuous delivery helps enable test-driven development and improves the ability to verify features continuously.
This document discusses agile defect management, distinguishing between functional defects found during testing of a specific user story, and regression defects found during broader testing. Functional defects are fixed immediately or approved as open, and a user story cannot be completed until its defects are addressed. Regression defects are prioritized in the product backlog. The goal is to finish user stories' functionality first before addressing other defects based on priority.
Creator: Joel Champagne, President of CodeX Enterprises
This presentation covers various issues associated with SQL unit testing. We’ll look at end solutions in demo form using Visual Studio 2010 and other third party tools.
You'll learn:
* The value of pursuing SQL testing, early and continually in the development cycle
* Capabilities in Visual Studio 2010 to support SQL unit testing
* Capabilities in other tools to support SQL unit testing
San Jose Selenium Meetup 22 Mar 2012: The Restless Are Getting NativeDante Briones
Are you wondering how to write automated tests for your shiny new iOS application? Is it even possible? Maybe you're sick of manually running the same test scenarios over and over and over… are you developing blisters on your fingertips?
In his talk, Dante Briones--Principal Consultant for Cochiva--will give a broad overview of the automated testing tools currently available for iOS, and share some hard-won secrets of iOS app test automation using NativeDriver -- an implementation of the WebDriver API that can drive *native* applications running on iOS or Android. You'll see how to integrate NativeDriver into your iOS app, allowing you to write functional tests in Java. You'll learn how to execute those tests at the command line and how to integrate those tests into a continuous integration tool like Jenkins. You'll hear lots of tips about how to improve your chances for a successful adoption of a functional testing suite.
Parasoft Concerto A complete ALM platform that ensures quality software can b...Engineering Software Lab
Parasoft Concerto is a complete software development management platform that ensures quality software can be produced consistently and efficiently–in any language.
By integrating policy-driven project management with Parasoft Test's quality lifecycle management as well as Parasoft Virtualize's dev/test environment management, Parasoft Concerto ensures predictable project outcomes while driving unprecedented levels of productivity and application quality.
Releasing fast code - The DevOps approachMichael Kopp
Agile makes you Develop faster, DevOps also makes you Deploy faster but how do you make your Application faster?
Many currently used Performance Management practices don’t work anymore as they are too time consuming. It takes a new approach to track performance in Continuous Integration, get more value out of Load Testing and leverage production data for performance optimization.
We will show you real world examples on how the new DevOps approach can work.
THE FUTURE OF LEED ENERGY MODELING IS HERE!! IES VE-Navigator for ASHRA E 90.1gautamsauraj
The document describes a new tool called VE-Navigator for ASHRAE 90.1 that was designed to streamline and speed up the LEED energy calculation and submission process. It allows users to automatically create baseline models, size HVAC systems, run simulations, and generate reports formatted for submission. According to testimonials, it reduces the time to complete ASHRAE 90.1 PRM calculations by 45% and enables more accurate modeling with less human error. The tool is part of a suite of performance analysis software that can also analyze other LEED credits and is available for trial in December 2010.
Scaling Continuous Integration Practices to Teams with Parallel DevelopmentIBM UrbanCode Products
Slides from an Urbancode and Accurev joint webinar: http://www.accurev.com/webinar/20120119-Scaling-CI-Parallel-Development
Continuous integration is simple with a single development team. But when software projects grow to multiple teams and dependencies, continuous integration loses effectiveness due to parallel projects, varying release schedules, and differing cadences between teams. As a result, many teams unknowingly lose the benefits of continuous integration, and therefore suffer from a lack of feedback and poor quality.
In this webinar, UrbanCode’s Eric Minick and AccuRev’s Chris Lucca will explain how to:
- Scale continuous integration builds across multiple development teams working on parallel projects
- Share only code that has passed continuous integration from other teams to avoid broken builds and confusion
- Automate the configuration of your test environment to handle fluid projects done in parallel
The document discusses test-driven PL/SQL development and best practices for error management. It covers defining requirements, writing unit tests, handling exceptions, and logging errors consistently. Key aspects include using pre-defined exception types and handlers, avoiding direct error raising/handling in application code, and following standards for error messaging.
App Dynamics & SOASTA Testing & Monitoring Converge, March 2012SOASTA
Dan Bartow, VP Performance Engineering, SOASTA and Steve Burton, Technology Evangelist, AppDynamics discuss the convergence of two traditionally separate domains and also demo testing and troubleshooting with CloudTest & AppDynamics.
1) The document discusses software testing strategies including improving test design, automation, understanding development processes, and leveraging APIs.
2) It also discusses tactics for team development including understanding customer pains, resolving issues, and contributing to forums and documentation.
3) Finally, it outlines processes for pre-integration testing including expectations for success/failure emails and general product qualification testing.
The document discusses Nicolas De Loof's background and experience in the Java and open source software communities. It then provides an overview of what a software factory is and lists its typical components. The document discusses choosing Git and Maven as version control and build tools respectively, and Jenkins as the automation and continuous integration tool. It then discusses using a platform-as-a-service model rather than on-premises containers to host the software factory components.
The document describes Unosquare's delivery centers located across the United States and Mexico, which provide services such as software development, QA testing, and project management using agile methodologies and tools. It highlights benefits like lower costs, ease of collaboration due to proximity, and cultural similarities that make working with the Mexico delivery center attractive. Sample metrics are also provided showing the company's testing capabilities.
The document discusses STMicroelectronics' deployment of functional qualification methodologies using Certitude mutation analysis. It outlines ST's initial engagement with Certess in 2004 and how they have expanded usage of the technology to now cover 80% of ST's IPs. The document also provides details on ST's functional qualification methodology, sharing of best practices, detection strategies used, and two case studies on measuring quality of third-party IPs and detecting issues in a video codec design.
This document provides an overview of test design and management concepts in the context of an IFDK reference product. It discusses different testing levels including unit, integration, system and acceptance testing. It describes the V-model for verification and validation. Requirements, test cases, test automation, and regression testing are also covered. Various testing techniques like black box, white box, code coverage and stubs are explained. The importance of test design and documentation is emphasized for effective testing.
Software can impact many aspects of society and is found almost everywhere. Common problems in software development include projects not fulfilling customer needs, being difficult to extend and improve, lacking documentation, and having poor quality. Software engineering aims to produce software on time, reliably, and completely by applying a systematic and disciplined approach.
These are the slides from my talk at the LESS 2011 conference in Stockholm, Sweden.
Product Ownership is a multi-faceted responsibility that demands a broad set of perspectives combined with deep product and domain knowledge. Effective product ownership requires both an internal and an external perspective. The challenges are amplified for large complex organizations developing large complex products and systems. In different organizations, engineering, product management, user experience and other functional groups can all lay claim to the role with some legitimacy.This talk will describe the challenges of understanding product ownership in large organizations, and of filling the product owner role effectively. We present different models for filling the product owner role, including single product owner, proxy product owner, and product owner teams.
Blue Monitor Systems is an employee-owned company dedicated to delivering high-quality creative, technical, and scientific services worldwide. The company encourages employees to think like owners and contribute to social well-being. Blue Monitor uses an iterative "Zero Time" method combining Agile and traditional approaches for medium and large projects. This includes continuous integration, test-driven development, and matrix project teams with specialists in design, engineering, testing, and operations.
Introducing Obsidian Software and RAVEN-GCS for PowerPCDVClub
Obsidian Software introduces RAVEN-GCS, a random test generator tool for processor verification that automatically generates assembly instructions to stimulate a microprocessor design, is customizable for any architecture, and helps reduce verification time and effort by focusing engineers on failing tests rather than creating directed test cases.
Tomas Riha presented on the principles and benefits of continuous delivery. Continuous delivery aims to have applications always ready for release through a highly automated process of continuous integration, testing, and deployment. It emphasizes automating all parts of the release process, building quality in from the start, and having all team members share responsibility for releases. Frequent releases allow for faster feedback and reduce risks from large code changes. Continuous delivery helps enable test-driven development and improves the ability to verify features continuously.
This document discusses agile defect management, distinguishing between functional defects found during testing of a specific user story, and regression defects found during broader testing. Functional defects are fixed immediately or approved as open, and a user story cannot be completed until its defects are addressed. Regression defects are prioritized in the product backlog. The goal is to finish user stories' functionality first before addressing other defects based on priority.
BugRaptors provide Software testing is entirely about finding defects in applications, right? Apparently, this can be considered as the principal goal of all the QA practices. However, all the defects diverge from each other. It cannot be stated if some are more important than others, yet it’s possible to locate and fix them all.
The document describes a new integrated development and testing lifecycle model implemented by a team. The key aspects of the new model include:
1) Breaking down the team silos by having developers involved in all QA activities and the sole tester organizing the entire team.
2) Adopting a new V-model that integrates development and testing rather than using waterfall or iterative waterfall.
3) Requiring representation of requirements using test cases, test-driven development, peer code reviews, continuous integration/testing, and user acceptance testing each iteration to achieve two "quality gates."
4) This new approach resulted in fewer bugs found by the client during testing compared to their previous method.
The document provides guidance on best practices for bug filing and management. It discusses how to write high-quality bug reports that are reproducible by developers. It emphasizes the importance of thoroughly documenting steps to reproduce issues and providing all relevant information. The document also covers defect tracking metrics and how they can be used to assess testing progress and product quality.
Agile Software Development in Practice - A Developer PerspectiveWee Witthawaskul
This document provides an overview of agile software development practices from a developer perspective. It recommends adopting agile practices to increase productivity and recommends Scrum and XP as agile frameworks. It describes common agile practices like user stories, daily standups, iteration planning, testing practices like TDD, mocks and continuous integration to automate testing.
The document describes the typical lifecycle of a software bug, from when it is first reported as a new bug to when it is eventually closed once fixed. The lifecycle involves the bug changing states as it is reviewed, assigned to a developer, tested after a fix is applied, and finally closed once fully resolved. The document also outlines the different levels of severity a bug can be classified as, from critical bugs that prevent testing to minor cosmetic bugs, and provides an example of a bug report template.
The document discusses defect reporting and tracking. It defines a software bug and explains that once a tester identifies a defect, they generate a formal defect report. The report includes information like a unique ID, project name, summary, steps to reproduce, actual and expected results. A bug goes through different statuses in its lifecycle from new to closed. Developers analyze and fix bugs, while testers verify fixes and may reopen bugs. Bug tracking systems help teams manage large numbers of defects by keeping track of key details for each bug report.
Just uploaded this for someone but i see that animations are broken. The slide is also not that usefull currently as it requires some more explanations.
- Engage is a service that delivers new online business capabilities rapidly in response to changing market conditions through an innovation environment and process.
- It employs an iterative development approach using prototypes, user reviews, and testing to deliver tangible, usable results within weeks rather than abstract long-term plans.
- The Engage platform provides visibility into the project plan, risks, code quality, testing coverage and results to help manage the innovation process.
Continuous Delivery refers to the process of releasing high quality software quickly and with confidence through the use of build, test and deployment automation. By applying Lean techniques to the development, test and deployment of software, waste is reduced and staff are freed up to work on more important tasks. By following a continuous delivery model, release cycles shift from a matter of months to weeks or days.
In this presentation, we will look at the key tools and processes involved in transitioning from a manual culture to one that embraces automation. We will look at real world examples, including the tools and architectural components. We will discuss organizational impacts, including the dramatic improvements in morale as team delivery commitments are met more easily through automation.
Eswaranand is a software test lead with over 8 years of experience defining and executing functional, performance, and automation test strategies across various domains. He has a bachelor's degree in information technology and an MBA in human resources. Currently working as a software test advisor/lead/consultant at Dell, his responsibilities include requirement analysis, test case preparation, automation script creation, and managing a testing team. He has extensive experience in various roles testing applications for healthcare, finance, e-commerce, and other domains.
1. The document discusses software quality and reliability in engineering. It defines quality as software being bug-free, on time, meeting requirements, and maintainable. Reliability is the probability of failure-free operation over time in a given environment.
2. Ensuring quality involves preventing and detecting faults during all phases of the software development life cycle from requirements to testing. The V-model helps achieve quality by involving testers early on.
3. Reliability focuses on avoiding faults during design and detecting problems during all phases through techniques like fault tolerance, forecasting, and measuring metrics like MTBF.
The presentation discusses moving from a reactive test-focused approach to quality to a proactive quality engineering approach. It outlines a phased approach to preventing bugs, beginning with clarifying requirements, ensuring designs are testable, and inspecting code. It encourages learning from past bugs to identify process improvements. Attendees are challenged to pick one action like documenting a requirement or reviewing code to start implementing quality practices. Effective test case and bug management processes are also highlighted.
The Zen of Scrum document provides an overview of Scrum and its key concepts. It summarizes problems with traditional software development approaches and how Agile and Scrum aim to address these issues. The document outlines Scrum roles like the Product Owner, Development Team, and Scrum Master. It also describes Scrum ceremonies and artifacts like Sprints, the Product Backlog, Sprint Backlog, Daily Scrums, Sprint Reviews, and Retrospectives which aim to manage complexity through transparency, inspection, and adaptation. The document notes some hot issues with scaling Scrum and results organizations have seen from adopting Scrum practices.
Defects identified during testing are documented, including a heading, detailed description, status (new, in progress, resolved, etc.), priority (normal, high, urgent, immediate), assignee, test case code if applicable, BRD ID, frequency (always, sometimes, once), severity (critical, major, minor), date closed, and optional attachments. The documentation contains information to help developers understand and resolve the defect.
The document provides an overview of JIRA concepts including projects, issues, statuses, resolutions, and priorities. A project contains a collection of issues and has a name and key. Issues represent bugs, epics, improvements, features, stories, and tasks. Statuses track an issue's stage from open to in progress, resolved, and closed. Resolutions indicate how an issue was addressed like fixed, won't fix, or duplicate. Priorities denote an issue's importance from blocker to critical, major, minor, and trivial.
The document discusses remote teams and remote management. It defines traditional, remote, and virtual teams. Traditional teams are co-located while remote teams have members in different locations but the same manager. Virtual teams have members reporting to different managers. Remote management is important for business success but faces challenges like complicated communication across time zones and cultures. Effective remote management requires the right tools, processes, and focus on people through clear goals, communication, and addressing issues immediately.
This document discusses motivating quality control staff through addressing non-adequate work assignments, unrealistic expectations, ownership of work, and data-driven metrics. It suggests feeling important through developing test cases and code, having an environment that tracks bug detection trends and workloads, and addressing performance issues over time to maintain peak performance levels. The overall message is that motivation is key to skills and performance for quality control employees.
This document discusses how to motivate quality control (QC) workers. It suggests showing metrics trends over time to demonstrate the impact of QC work. These may include test case, user story, and bug trends as well as bug detection percentages. Building communication between QC and business stakeholders is also recommended. The document notes potential motivators such as challenges, isolation from development teams, and seeing the results of one's work. However, it acknowledges that developers and testers may have different perspectives on who "owns" testing of specific features.
This document discusses the importance of quality control and software testing. It provides examples of costly failures that occurred when proper testing was not conducted, such as a Mercury spacecraft going off course and costing $384 million, and an ambulance service problem in London that resulted in loss of lives. The document defines a tester as a skilled professional involved in testing components or systems to ensure quality. It emphasizes that testing is necessary to avoid serious issues and save costs.
The Pomodoro Technique is a time management method that uses a timer to break down work into intervals, traditionally 25 minutes in length, separated by short breaks. It was developed in the 1980s by Francesco Cirillo as a student to help him focus on tasks and manage distractions. The technique involves using a timer to track intervals of work and breaks, focusing on one task at a time without distractions. It has been shown to help improve productivity and manage stress through planned breaks and task prioritization.
This document provides an overview of the ISTQB CTAL Test Manager certification. It discusses key topics that will be covered on the exam, including test processes and tools, testing in the software development life cycle, test planning, test control, and assessing development and test processes. The author aims to present 90% of the information directly from the ISTQB syllabus and provides some of their own insights. References and resources are also included to aid further study.
This document discusses the Far Manager file manager software. It provides examples of how Far Manager allows quick file system navigation, text editing capabilities, an integrated command line, process management, archiving functionality, and network browsing. Shortcuts for many of Far Manager's features are presented. The document concludes that while Far Manager is a useful tool, the user decides which features meet their needs.
The document describes a QA dashboard (QAD) that was implemented for a real software project. The QAD provides structure and visibility into key project metrics through various boards and reports accessible via JIRA and Confluence. It is intended to help address common project issues like poor planning, communication, task distribution, and risk visibility by centralizing important testing and quality metrics.
Digital Marketing Trends in 2024 | Guide for Staying AheadWask
https://www.wask.co/ebooks/digital-marketing-trends-in-2024
Feeling lost in the digital marketing whirlwind of 2024? Technology is changing, consumer habits are evolving, and staying ahead of the curve feels like a never-ending pursuit. This e-book is your compass. Dive into actionable insights to handle the complexities of modern marketing. From hyper-personalization to the power of user-generated content, learn how to build long-term relationships with your audience and unlock the secrets to success in the ever-shifting digital landscape.
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdfChart Kalyan
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.
This presentation provides valuable insights into effective cost-saving techniques on AWS. Learn how to optimize your AWS resources by rightsizing, increasing elasticity, picking the right storage class, and choosing the best pricing model. Additionally, discover essential governance mechanisms to ensure continuous cost efficiency. Whether you are new to AWS or an experienced user, this presentation provides clear and practical tips to help you reduce your cloud costs and get the most out of your budget.
Trusted Execution Environment for Decentralized Process MiningLucaBarbaro3
Presentation of the paper "Trusted Execution Environment for Decentralized Process Mining" given during the CAiSE 2024 Conference in Cyprus on June 7, 2024.
HCL Notes and Domino License Cost Reduction in the World of DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slackshyamraj55
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
Digital Banking in the Cloud: How Citizens Bank Unlocked Their MainframePrecisely
Inconsistent user experience and siloed data, high costs, and changing customer expectations – Citizens Bank was experiencing these challenges while it was attempting to deliver a superior digital banking experience for its clients. Its core banking applications run on the mainframe and Citizens was using legacy utilities to get the critical mainframe data to feed customer-facing channels, like call centers, web, and mobile. Ultimately, this led to higher operating costs (MIPS), delayed response times, and longer time to market.
Ever-changing customer expectations demand more modern digital experiences, and the bank needed to find a solution that could provide real-time data to its customer channels with low latency and operating costs. Join this session to learn how Citizens is leveraging Precisely to replicate mainframe data to its customer channels and deliver on their “modern digital bank” experiences.
Skybuffer AI: Advanced Conversational and Generative AI Solution on SAP Busin...Tatiana Kojar
Skybuffer AI, built on the robust SAP Business Technology Platform (SAP BTP), is the latest and most advanced version of our AI development, reaffirming our commitment to delivering top-tier AI solutions. Skybuffer AI harnesses all the innovative capabilities of the SAP BTP in the AI domain, from Conversational AI to cutting-edge Generative AI and Retrieval-Augmented Generation (RAG). It also helps SAP customers safeguard their investments into SAP Conversational AI and ensure a seamless, one-click transition to SAP Business AI.
With Skybuffer AI, various AI models can be integrated into a single communication channel such as Microsoft Teams. This integration empowers business users with insights drawn from SAP backend systems, enterprise documents, and the expansive knowledge of Generative AI. And the best part of it is that it is all managed through our intuitive no-code Action Server interface, requiring no extensive coding knowledge and making the advanced AI accessible to more users.
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on integration of Salesforce with Bonterra Impact Management.
Interested in deploying an integration with Salesforce for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Generating privacy-protected synthetic data using Secludy and MilvusZilliz
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
FREE A4 Cyber Security Awareness Posters-Social Engineering part 3Data Hops
Free A4 downloadable and printable Cyber Security, Social Engineering Safety and security Training Posters . Promote security awareness in the home or workplace. Lock them Out From training providers datahops.com
leewayhertz.com-AI in predictive maintenance Use cases technologies benefits ...alexjohnson7307
Predictive maintenance is a proactive approach that anticipates equipment failures before they happen. At the forefront of this innovative strategy is Artificial Intelligence (AI), which brings unprecedented precision and efficiency. AI in predictive maintenance is transforming industries by reducing downtime, minimizing costs, and enhancing productivity.
A Comprehensive Guide to DeFi Development Services in 2024Intelisync
DeFi represents a paradigm shift in the financial industry. Instead of relying on traditional, centralized institutions like banks, DeFi leverages blockchain technology to create a decentralized network of financial services. This means that financial transactions can occur directly between parties, without intermediaries, using smart contracts on platforms like Ethereum.
In 2024, we are witnessing an explosion of new DeFi projects and protocols, each pushing the boundaries of what’s possible in finance.
In summary, DeFi in 2024 is not just a trend; it’s a revolution that democratizes finance, enhances security and transparency, and fosters continuous innovation. As we proceed through this presentation, we'll explore the various components and services of DeFi in detail, shedding light on how they are transforming the financial landscape.
At Intelisync, we specialize in providing comprehensive DeFi development services tailored to meet the unique needs of our clients. From smart contract development to dApp creation and security audits, we ensure that your DeFi project is built with innovation, security, and scalability in mind. Trust Intelisync to guide you through the intricate landscape of decentralized finance and unlock the full potential of blockchain technology.
Ready to take your DeFi project to the next level? Partner with Intelisync for expert DeFi development services today!
Building Production Ready Search Pipelines with Spark and MilvusZilliz
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/temporal-event-neural-networks-a-more-efficient-alternative-to-the-transformer-a-presentation-from-brainchip/
Chris Jones, Director of Product Management at BrainChip , presents the “Temporal Event Neural Networks: A More Efficient Alternative to the Transformer” tutorial at the May 2024 Embedded Vision Summit.
The expansion of AI services necessitates enhanced computational capabilities on edge devices. Temporal Event Neural Networks (TENNs), developed by BrainChip, represent a novel and highly efficient state-space network. TENNs demonstrate exceptional proficiency in handling multi-dimensional streaming data, facilitating advancements in object detection, action recognition, speech enhancement and language model/sequence generation. Through the utilization of polynomial-based continuous convolutions, TENNs streamline models, expedite training processes and significantly diminish memory requirements, achieving notable reductions of up to 50x in parameters and 5,000x in energy consumption compared to prevailing methodologies like transformers.
Integration with BrainChip’s Akida neuromorphic hardware IP further enhances TENNs’ capabilities, enabling the realization of highly capable, portable and passively cooled edge devices. This presentation delves into the technical innovations underlying TENNs, presents real-world benchmarks, and elucidates how this cutting-edge approach is positioned to revolutionize edge AI across diverse applications.
4. Agenda
Roles
Email Notifications
Work Item Types
User Story Workflow
Prioritizing Bugs
Bug Workflow
Task Workflow
Q&A
5. Roles
Manager/Admin – unlimited permissions
DEV – Developer
– Create Tasks (Create Bugs, Create User Stories)
– Resolve Bugs, User Stories
– Close Tasks
QC – Quality Control Engineer
– Create Bugs, Tasks (Create User Stories)
– Close Bugs, User Stories, Tasks
– Reopen Bugs, User Stories Tasks
USER – End User Representative
– Create Problem Reports
– Close Problem Reports
– Reopen Problem Reports
6. Email Notifications
We need email notifications each time a work item is being moved through the workflow to quickly know what to
do and don’t bother one another with stupid questions like: “Are you done with the story, so I can test?”,
“Have you done with testing, how it went?”.
We need to use the tool we have for that – TFS.
DEV QC
– Active US/Bug has been assigned – Active US/Bug has been moved to
to. (New, Reopened, Edited). Resolved and Assigned to.
– Worked on US/Bug has been – Worked on US/Bug has been
closed. closed.
7. Work Item Types
User Story
- one or more sentences in the everyday or business language of the end user that
captures what the user wants to achieve. Before a user story is to be implemented,
an appropriate acceptance procedure must be written by the customer to ensure by
testing or otherwise determine whether the goals of the user story have been
fulfilled.
Bug
- a program defect, which is usually found and described as a failure (deviation
between actual and expected behavior). Usually filed by QA.
Task
- an activity that needs to be accomplished within a defined period of time. Is usually
a sub-item of a Bug, User Story
Problem Report
– an unverified report, usually filed by PM or user. After positive verification a bug
report is created. Bug report changes are automatically reflected in the problem
report
8. User Story Workflow
Active (New)
Assign Unassign Email to
(Admin) (Admin) DEV
Rejected/Out of Scope/ Abandoned
Active (assigned)
(QC, Admin, DEV)
Code complete and unit tests pass
Build is available for QC
(DEV)
Acceptance tests fail*
(QC)
Resolved
Assign Unassign Email to QC
(DEV) (DEV)
Resolved (assigned)
Acceptance Closed in
tests pass Error Reintroduced in
(QC) (QC) Scope/Closed in Error
(QC)
Closed
Email to
DEV & QC
involved
9. Acceptance tests fail
At least:
1 * Critical Issue OR
1 * High Issue OR
N * Medium Issues, where N is too many
10. Prioritizing Bugs
Priority (When it should be fixed?) Severity (What it affects?)
The level of (business) importance assigned The degree of impact that a defect has on
to an item, e.g. defect. the development or operation of a
component or system.
Priority Description Defined By Severity Description Example Defined
By
1 The bug is Critical Bug Reporter 1 (Critical) An Absolute Blocker. Unable to Start or Bug
for business Use Application. Reporter
needs. Must be Crash.
fixed ASAP
2 (High) Serious Failure. Direct Unable to Create Bug
2 Very important Bug Reporter argument against the new row. Unable to Reporter
issue to be fixed Acceptance Criteria edit existing rows.
Data loss.
3 Highly appreciated Bug Reporter
3 (Medium) Regular bug. Affects very few Keyboard shortcuts Bug
to have
of potential users. Not do not work. Reporter
blocking anything Validation missing
4 Nice to have Bug Reporter
4 (Low) Minor issue, not affecting Cosmetic UI issues, Bug
anyone at all, just annoying grammar errors Reporter
11. Prioritizing Items
Stack Rank (What you shall work on first)
-is the traditional method Product Owners use to rank/prioritize their product backlog items.
The lower the stack rank the higher the priority the work item is
12. Bug Workflow
Active (New)
Assign Unassign Email to
(QC) (QC) DEV
As Designed/Cannot Reproduce/
Active (assigned)
Deferred/Duplicate/Obsolete
(DEV) Fixed
(DEV)
Not fixed/Test Failed
(QC)
Resolved
Assign Unassign Email to QC
(DEV) (DEV)
Resolved (assigned)
Email to Verified
DEV & QC (QC)
involved Regression/Reactivated
(QC)
Closed
14. What we still lack?
WHO IS DOING WHAT AT THE MOMENT
?
IS THE FIX/NEW CODE AVAILABLE FOR ME TO TEST
15. (Proposed) Bug Workflow
Active (assigned)
Email to
Start Work Stop Work DEV
(DEV) (DEV)
As Designed/Cannot Reproduce/
In Progress
Deferred/Duplicate/Obsolete
Fixed Email to QC
(DEV)
(Work done by DEV)
(DEV)
Not fixed/Test Failed
(QC)
Pending Build
Build Available Email to QC
(TFS)
Resolved (assigned)
Verified Email to
(QC) DEV & QC
involved Regression/Reactivated
(QC)
Closed
16. Summary
We need Work Item STATES for following the right
Development Process. Email notifications provide immediate
heads up
17. Summary
Each particular state means some work needs to be done by
relevant department:
– An Item mustn’t be RESOLVED if there some known
developer work still needs to be done. Existing Critical
bugs are the case
– An Item mustn’t be CLOSED if QC has something to test
18. Summary
The only reason a Work Item is not being transferred to the
next state – is progress on it. If you are done with it,
immediately move it forward with the STATE
20. Summary
Do not hesitate to put comments in the History section for
cases there are not relevant REASON as well as for other
cases
21. Q&A
Q: What if I have a reason, which is not included in the Reason Dropdown?
A: Feel free to select the most suitable one and put your comments in the History field. Don’t be miserly
for comments.
Q: (DEV) What if I want to pass to QC non-finished Story to test?
A: Fire away! But don’t make it RESOLVED. QC won’t file bugs – only inform you about the Smoke Test
results. It’s your deal. Beneficial for close collaboration. Should not be a common practice.
Q: (DEV) When shall I make an Item RESOLVED?
A: When you complete all the work on it, and (theoretically) it should go on Production, if no critical
bugs. Also when QC is able to access the test object.
Q: (QC) What if I found S1/S2 issue, and developer is asking me not to reopen the Story for several
minutes, the fix is being prepared?
A: Go for it, but if you really going to have the fixed build in 1-2 hours. If it lasts longer – reopen the
Item with the issue linked.
Q: (ANYONE) Would like to introduce new feature.
A: Make a list of. Come up with the proposal in the Status Meetings. Introduce “Improvement Iteration”
Q: Parent -> Child Stories in the Backlog
A: TODO