Anyone writing, editing, or managing any type of communications for a living is feeling the crunch. There is less time to create and edit; more types and formats of content; more apps, software, and systems to learn. And we expect quality, accuracy, and consistency from ourselves because we take pride in our work. This session discussed how to address a multitude of modern dilemmas with a relatively old-school hack: a checklist.
This session was about how using a comprehensive checklist created and updated for a specific communication task can help you differentiate workflows, systems, and activities; spell out style and formatting details, track your progress, document metrics, and give you a sense of completion and peace of mind.
Using Checklists to Increase Consistency and Productivity in Communication TasksKelly Schrank, MA, ELS
The document discusses how using checklists can increase consistency and productivity for communication tasks, outlining the benefits of checklists and providing a step-by-step process for creating effective checklists, including choosing a task, writing out the steps, adding specifics, testing the checklist, and ensuring it is revised as needed. Checklists are recommended for tasks that are repeated, have many details or steps, or where consistency is important.
This document discusses project estimation and how estimates become more accurate over time as more details are known. It notes that initial estimates can be off by a factor of 4x due to lack of details and complexity. Using agile methodology, estimates are revised each sprint or iteration as the project progresses to account for learnings and ensure deviations are addressed.
Agile software development practices continue to dominate organizations and user experience research and strategy are more necessary than ever, but incorporating research doesn’t always jive with the established practices of Agile. Many of us are still at a loss for making research happen in Agile settings.
This session will cover recommendations for setting up the logistics to best facilitate research and specific tips to plan, run, and analyze research effectively within an Agile environment.
The document discusses the problems with using rollups to track progress on multi-team projects. Rollups hide valuable information about individual team and program progress. They can inaccurately forecast completion dates and set incorrect expectations. The document recommends tracking each team's progress separately without masking data and correlating program objectives with project progress to provide better visibility.
San Francisco Selenium Meetup held 04-Aug-2009 at Twitter HQSauce Labs
Results of a survey of San Francisco Selenium Meetup user experiences with and practices using Selenium. Bear in mind the survey was given to users attending a workshop on improving Selenium script creation and maintenance efficiency, so their chief issue, "test brittleness" may relate to their choice to attend this talk.
Kanban method: The Practices aren't the PointJonathan Hansen
Capping our 10-month series on the Kanban Method; in this presentation we discuss that the Practices of the Kanban Method are a means, not an end.
The true end goal: enabling efficient flow of high value, high quality work.
Wenn KI die Zukunft des Testens ist, dann zeige ich Ihnen wie. Es gibt unzählige Automatisierungstools, aber dank hoher Erstellungs- und Wartungsaufwände ist GUI-basiertes Testen immer noch eine mehrheitlich manuelle Aufgabe (entsprechend der Testpyramide). Dabei macht Testen mittlerweile 30% des Gesamtaufwandes eines Softwareprojektes aus! Da ein Fehler im Auge des Betrachters liegt, ist es für eine KI schwer einen Fehler als solchen zu erkennen. Deshalb kann KI heute noch keine Tests automatisieren. Aber was, wenn es eine Möglichkeit gäbe dieses Problem zu umgehen? Ich zeige Ihnen, wie man heute eine KI trainieren und nutzen kann, um nicht nur technische Fehler zu finden, sonder automatisch Tests zu automatisieren! Besuchen Sie die Zukunft des Testens, und sehen Sie wie KI uns helfen kann Software besser zu machen.
The Whole Team Approach to Quality in Continuous Deliverylisacrispin
Lisa shares her teams' experiences with making a team commitment to quality and learning ways to build it in and fit all testing activities into continuous delivery.
Using Checklists to Increase Consistency and Productivity in Communication TasksKelly Schrank, MA, ELS
The document discusses how using checklists can increase consistency and productivity for communication tasks, outlining the benefits of checklists and providing a step-by-step process for creating effective checklists, including choosing a task, writing out the steps, adding specifics, testing the checklist, and ensuring it is revised as needed. Checklists are recommended for tasks that are repeated, have many details or steps, or where consistency is important.
This document discusses project estimation and how estimates become more accurate over time as more details are known. It notes that initial estimates can be off by a factor of 4x due to lack of details and complexity. Using agile methodology, estimates are revised each sprint or iteration as the project progresses to account for learnings and ensure deviations are addressed.
Agile software development practices continue to dominate organizations and user experience research and strategy are more necessary than ever, but incorporating research doesn’t always jive with the established practices of Agile. Many of us are still at a loss for making research happen in Agile settings.
This session will cover recommendations for setting up the logistics to best facilitate research and specific tips to plan, run, and analyze research effectively within an Agile environment.
The document discusses the problems with using rollups to track progress on multi-team projects. Rollups hide valuable information about individual team and program progress. They can inaccurately forecast completion dates and set incorrect expectations. The document recommends tracking each team's progress separately without masking data and correlating program objectives with project progress to provide better visibility.
San Francisco Selenium Meetup held 04-Aug-2009 at Twitter HQSauce Labs
Results of a survey of San Francisco Selenium Meetup user experiences with and practices using Selenium. Bear in mind the survey was given to users attending a workshop on improving Selenium script creation and maintenance efficiency, so their chief issue, "test brittleness" may relate to their choice to attend this talk.
Kanban method: The Practices aren't the PointJonathan Hansen
Capping our 10-month series on the Kanban Method; in this presentation we discuss that the Practices of the Kanban Method are a means, not an end.
The true end goal: enabling efficient flow of high value, high quality work.
Wenn KI die Zukunft des Testens ist, dann zeige ich Ihnen wie. Es gibt unzählige Automatisierungstools, aber dank hoher Erstellungs- und Wartungsaufwände ist GUI-basiertes Testen immer noch eine mehrheitlich manuelle Aufgabe (entsprechend der Testpyramide). Dabei macht Testen mittlerweile 30% des Gesamtaufwandes eines Softwareprojektes aus! Da ein Fehler im Auge des Betrachters liegt, ist es für eine KI schwer einen Fehler als solchen zu erkennen. Deshalb kann KI heute noch keine Tests automatisieren. Aber was, wenn es eine Möglichkeit gäbe dieses Problem zu umgehen? Ich zeige Ihnen, wie man heute eine KI trainieren und nutzen kann, um nicht nur technische Fehler zu finden, sonder automatisch Tests zu automatisieren! Besuchen Sie die Zukunft des Testens, und sehen Sie wie KI uns helfen kann Software besser zu machen.
The Whole Team Approach to Quality in Continuous Deliverylisacrispin
Lisa shares her teams' experiences with making a team commitment to quality and learning ways to build it in and fit all testing activities into continuous delivery.
Get testing bottlenecks out of your pipelineslisacrispin
When teams move towards continuous delivery and deployment, how do they manage the manual stages in their deployment pipeline? This talk gives some techniques to visualize pipelines, identify bottlenecks, find ways to remove them.
The document discusses project management for litigation matters. It defines project management as planning, organizing, and managing resources to successfully complete specific goals and objectives. A project is a finite endeavor undertaken to create a unique product or service. The five stages of a project are to define, plan, execute, monitor, and review the project. Tips are provided around each stage, such as being clear about roles and responsibilities, communicating often, and reviewing tasks and goals. Project management involves identifying goals and issues, assessing resources and risks, planning tasks and timelines, communicating updates, and reviewing progress and outcomes.
1. Have a list of stories before sprint planning and break each story into tasks no more than 2 days long. This ensures everyone is on the same page during planning and tasks are easy to track.
2. Do small "demos" of test results to teammates, gathering feedback to improve testing. This spreads knowledge and increases quality and fun.
3. Continue tracking progress and checking improvements during retrospectives to increase productivity, quality and happiness.
4. Consider microservices architecture to clean the automation framework and decrease test time by reducing pre-conditions.
The document summarizes a presentation by Theresa Neate and Bharat Sangekar on agile testing and shifting quality to the left. Some key points:
- Theresa and Bharat discuss the mindset of agile testing and shifting quality earlier in the development process.
- Bharat explains how testers can take an adaptive role and test at different depths, providing an example of shifting testing left.
- They emphasize building quality into code through techniques like test-driven development and addressing technical debt earlier rather than later.
- The presentation concludes that testing responsibilities belong to the whole team, not just testers, and quality analysis is more important than assurance alone.
Let's drop the tester labels such as "functional tester", "system integration tester", "automation tester", etc. More and more teams are cross-functional and team members are required to be poly-skilled. If you are testing you can and should be involved in the full SDLC, which should include deployments and infrastructure. Just like there is application code, there is infrastructure code, which needs testing too. So where do you fit in? How can you remain relevant and helpful in the DevOps world?
Estimates are difficult but important for planning software projects. The document discusses common challenges with estimates like vague requirements, optimism bias, and unexpected dependencies. It also presents several case studies where estimates failed due to vague requirements, pressure to provide estimates quickly, or pre-estimating everything without proper analysis. Overall the document suggests that accurate estimates require well-defined requirements, considering dependencies and risks, and not feeling pressure to provide estimates before the team is ready.
Using Checklists to Increase Consistency and Productivity in Communication TasksKelly Schrank, MA, ELS
The document discusses using checklists to increase consistency and productivity. It recommends creating checklists for repeated tasks, processes with many details, frequently changing systems, and tasks where metrics need to be tracked. The process of creating an effective checklist involves choosing a task, performing the task while writing down each step, adding specifics and order to the steps, including tracking items, and testing and revising the checklist. Good checklists provide confidence that a task is complete and catch any errors.
The document discusses project quality management. It defines project quality management as continually measuring quality and taking corrective action until desired quality is achieved. This helps control costs, establish standards, and lower risks of failure. Effective quality management depends on planning, assurance, and control processes. Planning identifies quality goals and standards. Assurance provides evidence activities meet expectations. Control identifies and corrects problems to ensure standards compliance. Tools like matrices and diagrams can aid the three processes. Quality management software allows tracking quality aspects in one place. Techniques like total quality management, Six Sigma, and ISO certification aim to deliver high quality products and services.
The document outlines metrics for testing processes, projects, and products. It includes an agenda for a two-day workshop covering why metrics are important, how to define metrics, and different types of metrics. Process metrics measure the software testing process and can indicate effectiveness, efficiency, and areas for improvement. Examples of process metrics given are defect detection effectiveness, defect acceptance rate, defect rejection rate, and defect closure period. The document provides details on how to develop good process metrics using a top-down, goal-driven approach.
Test analysis & design good practices@TDT Iasi 17Oct2013Tabăra de Testare
The document discusses test analysis and design best practices. It covers defining test objectives, analyzing test items to identify conditions, designing test cases using various techniques, and ensuring traceability between requirements and test cases. Good practices for writing effective test cases are also presented, such as using a standardized naming convention and writing steps that verify a single testing idea. The importance of analysis and design in translating requirements into testable items prior to execution is emphasized.
Measuring for team effectiveness (with Reecetech)Mark Barber
The document discusses measuring team effectiveness through metrics. It provides examples of good and bad metrics, focusing on metrics that measure building the right thing, building the thing right, and building the thing in a sustainable way. Good metrics are developed by the team to improve performance and focus on important areas for improvement. The document also discusses measuring cycle time, engagement, production incidents, and other metrics to understand progress, eliminate waste, and ensure team health and quality.
Code campiasi qa-in-agile-projects-ana-figher-embarcaderoCodecamp Romania
This document discusses quality assurance and testing in agile projects. It defines key terms like quality assurance, quality control, and testing. It then explains how traditional testing practices have evolved with agile methodologies like Scrum. Quality is a team effort in agile, with all members sharing ownership. Testing focuses on providing effort estimates, exploratory testing, and continuous feedback in each sprint. Metrics are used to measure success and ensure a quality focused culture.
Implementing a Test Dashboard to Boost QualityTechWell
You are responsible for addressing quality problems that are plaguing your product and having an adverse impact on the business. Have you been challenged to provide a simple mechanism for quantifying and tracking key performance indicators selected by your organization. The ultimate goal is an approach that will enable the cross-functional team to identify problem areas so they can take corrective action. Where do you start? Attend this session to learn how you can develop a quantifiable approach to assessing testing effectiveness and addressing quality. Scott Acker shows you a solution he developed, deployed, and managed to effectively leverage various types of data to support analyzing, tracking, and reporting changes in testing and quality over time. Discover how to drive communication and collaboration improvements across the entire cross-functional team and boost quality efforts.
Pin the tail on the metric v01 2016 octSteven Martin
This presentation takes a different approach to metrics. Instead of listing the Top 10 field-tested metrics, we first talk about goals as prerequisites for metrics. Next, we discuss characteristics of good and bad metrics. We end with walking through an activity called “Pin the Tail on the Metric,” a technique to facilitate the critical thinking needed to determine what types of metrics can help your organization discuss trade-offs, options, and ultimately make better forward-looking decisions.
The document provides guidelines for conducting a project health check when a project is not meeting its goals. It outlines indicators of troubled projects, such as lack of documentation and cost/schedule issues. The guidelines describe a 5-step process to implement a health check: 1) define a charter, 2) outline an assessment plan, 3) conduct the check, 4) present a report, and 5) implement an approved plan. The health check evaluates project management, governance, and identifies priority areas for improvement.
This document outlines a project proposal template that uses a 5W2H (five W's and two H's) method to structure the key elements of a project. The 5W2H sections are What, Why, When, Where, Who, How, and How Much. The document provides examples and descriptions for how to complete each section of the 5W2H template to define the objectives, resources, activities, timeline, and solutions for a proposed project in a clear and concise manner.
This document discusses using Google's Attribute-Component-Capability (ACC) model approach to help balance test efforts. The key points are:
1) The ACC model involves listing a product's attributes, breaking it into technical components, and categorizing capabilities. This provides an overview of test needs across the entire product.
2) Complexity, frequency of use, and user impact are assigned scores to capabilities. This determines relative "testing needs".
3) The ACC items, scores, and needs are tracked in a tool like Excel linked to a tool like TFS. This provides instant visibility into where more testing is required based on risk.
Разработка эффективной тестовой стратегии, Антон СеменченкоCOMAQA.BY
The document discusses strategies for effective testing. It recommends defining a testing mission, analyzing the project context and scope, and creating a test strategy that addresses risks and goals. An effective test strategy helps ensure quality, mitigate risks, and determine test coverage, approaches, and processes. It also recommends defining metrics and success criteria to measure the value of the testing efforts. Automated testing should be considered based on its ability to potentially save time and money, though its ROI must be analyzed and stability concerns addressed.
Why You Don't Want to be a Tester; an agile discussionBrett Tramposh
"Why You Don't Want to be a Tester" focuses on a common discussion we are having among Quality Assurance and Software Testing professionals, especially as it relates to operating as part of an agile team.
In a recent discussion at the Software QA User Group in Portland Oregon, Brett used these slides to foster conversation and to promote the idea that each person should be proactive in their approach to not allow their role to simply become a tester. Solid QA practices are needed more today than ever as we move fast and raise the bar on quality and continually add to our tool belt!
The document discusses challenges faced by companies with both in-house and outsourced software testing. It introduces predictive analytics as a solution to address common challenges like managing multiple releases and tools, measuring productivity, and generating customized reports. Predictive analytics uses models to analyze test data and predict issues, risks, delays and determine how to optimize testing. Integrating predictive analytics into a testing framework can help reduce costs, improve quality and make better decisions.
Lean Business Analysis and UX Runway - Natalie WarnertNatalie Warnert
How to integrate BAs and UX in a Agile/Lean environment to create an MVP to learn while reducing potential waste. Presented at Lviv IT Arena, 2015 in Lviv, Ukraine by Natalie Warnert, October 3, 2015
www.nataliewarnert.com
Lean Business Analysis and UX Runway: Managing Value by Reducing Waste (Natal...IT Arena
The document discusses how business analysts and UX professionals can collaborate effectively in an Agile environment through a process called the "Analyst and UX Runway". This process involves business analysts and UX professionals working together throughout the product development lifecycle from initial planning through execution and review, with the goal of continuously delivering value to customers through short iterations of planning, development and feedback. The Analyst and UX Runway approach aims to balance upfront planning with flexibility to incorporate frequent customer feedback.
Get testing bottlenecks out of your pipelineslisacrispin
When teams move towards continuous delivery and deployment, how do they manage the manual stages in their deployment pipeline? This talk gives some techniques to visualize pipelines, identify bottlenecks, find ways to remove them.
The document discusses project management for litigation matters. It defines project management as planning, organizing, and managing resources to successfully complete specific goals and objectives. A project is a finite endeavor undertaken to create a unique product or service. The five stages of a project are to define, plan, execute, monitor, and review the project. Tips are provided around each stage, such as being clear about roles and responsibilities, communicating often, and reviewing tasks and goals. Project management involves identifying goals and issues, assessing resources and risks, planning tasks and timelines, communicating updates, and reviewing progress and outcomes.
1. Have a list of stories before sprint planning and break each story into tasks no more than 2 days long. This ensures everyone is on the same page during planning and tasks are easy to track.
2. Do small "demos" of test results to teammates, gathering feedback to improve testing. This spreads knowledge and increases quality and fun.
3. Continue tracking progress and checking improvements during retrospectives to increase productivity, quality and happiness.
4. Consider microservices architecture to clean the automation framework and decrease test time by reducing pre-conditions.
The document summarizes a presentation by Theresa Neate and Bharat Sangekar on agile testing and shifting quality to the left. Some key points:
- Theresa and Bharat discuss the mindset of agile testing and shifting quality earlier in the development process.
- Bharat explains how testers can take an adaptive role and test at different depths, providing an example of shifting testing left.
- They emphasize building quality into code through techniques like test-driven development and addressing technical debt earlier rather than later.
- The presentation concludes that testing responsibilities belong to the whole team, not just testers, and quality analysis is more important than assurance alone.
Let's drop the tester labels such as "functional tester", "system integration tester", "automation tester", etc. More and more teams are cross-functional and team members are required to be poly-skilled. If you are testing you can and should be involved in the full SDLC, which should include deployments and infrastructure. Just like there is application code, there is infrastructure code, which needs testing too. So where do you fit in? How can you remain relevant and helpful in the DevOps world?
Estimates are difficult but important for planning software projects. The document discusses common challenges with estimates like vague requirements, optimism bias, and unexpected dependencies. It also presents several case studies where estimates failed due to vague requirements, pressure to provide estimates quickly, or pre-estimating everything without proper analysis. Overall the document suggests that accurate estimates require well-defined requirements, considering dependencies and risks, and not feeling pressure to provide estimates before the team is ready.
Using Checklists to Increase Consistency and Productivity in Communication TasksKelly Schrank, MA, ELS
The document discusses using checklists to increase consistency and productivity. It recommends creating checklists for repeated tasks, processes with many details, frequently changing systems, and tasks where metrics need to be tracked. The process of creating an effective checklist involves choosing a task, performing the task while writing down each step, adding specifics and order to the steps, including tracking items, and testing and revising the checklist. Good checklists provide confidence that a task is complete and catch any errors.
The document discusses project quality management. It defines project quality management as continually measuring quality and taking corrective action until desired quality is achieved. This helps control costs, establish standards, and lower risks of failure. Effective quality management depends on planning, assurance, and control processes. Planning identifies quality goals and standards. Assurance provides evidence activities meet expectations. Control identifies and corrects problems to ensure standards compliance. Tools like matrices and diagrams can aid the three processes. Quality management software allows tracking quality aspects in one place. Techniques like total quality management, Six Sigma, and ISO certification aim to deliver high quality products and services.
The document outlines metrics for testing processes, projects, and products. It includes an agenda for a two-day workshop covering why metrics are important, how to define metrics, and different types of metrics. Process metrics measure the software testing process and can indicate effectiveness, efficiency, and areas for improvement. Examples of process metrics given are defect detection effectiveness, defect acceptance rate, defect rejection rate, and defect closure period. The document provides details on how to develop good process metrics using a top-down, goal-driven approach.
Test analysis & design good practices@TDT Iasi 17Oct2013Tabăra de Testare
The document discusses test analysis and design best practices. It covers defining test objectives, analyzing test items to identify conditions, designing test cases using various techniques, and ensuring traceability between requirements and test cases. Good practices for writing effective test cases are also presented, such as using a standardized naming convention and writing steps that verify a single testing idea. The importance of analysis and design in translating requirements into testable items prior to execution is emphasized.
Measuring for team effectiveness (with Reecetech)Mark Barber
The document discusses measuring team effectiveness through metrics. It provides examples of good and bad metrics, focusing on metrics that measure building the right thing, building the thing right, and building the thing in a sustainable way. Good metrics are developed by the team to improve performance and focus on important areas for improvement. The document also discusses measuring cycle time, engagement, production incidents, and other metrics to understand progress, eliminate waste, and ensure team health and quality.
Code campiasi qa-in-agile-projects-ana-figher-embarcaderoCodecamp Romania
This document discusses quality assurance and testing in agile projects. It defines key terms like quality assurance, quality control, and testing. It then explains how traditional testing practices have evolved with agile methodologies like Scrum. Quality is a team effort in agile, with all members sharing ownership. Testing focuses on providing effort estimates, exploratory testing, and continuous feedback in each sprint. Metrics are used to measure success and ensure a quality focused culture.
Implementing a Test Dashboard to Boost QualityTechWell
You are responsible for addressing quality problems that are plaguing your product and having an adverse impact on the business. Have you been challenged to provide a simple mechanism for quantifying and tracking key performance indicators selected by your organization. The ultimate goal is an approach that will enable the cross-functional team to identify problem areas so they can take corrective action. Where do you start? Attend this session to learn how you can develop a quantifiable approach to assessing testing effectiveness and addressing quality. Scott Acker shows you a solution he developed, deployed, and managed to effectively leverage various types of data to support analyzing, tracking, and reporting changes in testing and quality over time. Discover how to drive communication and collaboration improvements across the entire cross-functional team and boost quality efforts.
Pin the tail on the metric v01 2016 octSteven Martin
This presentation takes a different approach to metrics. Instead of listing the Top 10 field-tested metrics, we first talk about goals as prerequisites for metrics. Next, we discuss characteristics of good and bad metrics. We end with walking through an activity called “Pin the Tail on the Metric,” a technique to facilitate the critical thinking needed to determine what types of metrics can help your organization discuss trade-offs, options, and ultimately make better forward-looking decisions.
The document provides guidelines for conducting a project health check when a project is not meeting its goals. It outlines indicators of troubled projects, such as lack of documentation and cost/schedule issues. The guidelines describe a 5-step process to implement a health check: 1) define a charter, 2) outline an assessment plan, 3) conduct the check, 4) present a report, and 5) implement an approved plan. The health check evaluates project management, governance, and identifies priority areas for improvement.
This document outlines a project proposal template that uses a 5W2H (five W's and two H's) method to structure the key elements of a project. The 5W2H sections are What, Why, When, Where, Who, How, and How Much. The document provides examples and descriptions for how to complete each section of the 5W2H template to define the objectives, resources, activities, timeline, and solutions for a proposed project in a clear and concise manner.
This document discusses using Google's Attribute-Component-Capability (ACC) model approach to help balance test efforts. The key points are:
1) The ACC model involves listing a product's attributes, breaking it into technical components, and categorizing capabilities. This provides an overview of test needs across the entire product.
2) Complexity, frequency of use, and user impact are assigned scores to capabilities. This determines relative "testing needs".
3) The ACC items, scores, and needs are tracked in a tool like Excel linked to a tool like TFS. This provides instant visibility into where more testing is required based on risk.
Разработка эффективной тестовой стратегии, Антон СеменченкоCOMAQA.BY
The document discusses strategies for effective testing. It recommends defining a testing mission, analyzing the project context and scope, and creating a test strategy that addresses risks and goals. An effective test strategy helps ensure quality, mitigate risks, and determine test coverage, approaches, and processes. It also recommends defining metrics and success criteria to measure the value of the testing efforts. Automated testing should be considered based on its ability to potentially save time and money, though its ROI must be analyzed and stability concerns addressed.
Why You Don't Want to be a Tester; an agile discussionBrett Tramposh
"Why You Don't Want to be a Tester" focuses on a common discussion we are having among Quality Assurance and Software Testing professionals, especially as it relates to operating as part of an agile team.
In a recent discussion at the Software QA User Group in Portland Oregon, Brett used these slides to foster conversation and to promote the idea that each person should be proactive in their approach to not allow their role to simply become a tester. Solid QA practices are needed more today than ever as we move fast and raise the bar on quality and continually add to our tool belt!
The document discusses challenges faced by companies with both in-house and outsourced software testing. It introduces predictive analytics as a solution to address common challenges like managing multiple releases and tools, measuring productivity, and generating customized reports. Predictive analytics uses models to analyze test data and predict issues, risks, delays and determine how to optimize testing. Integrating predictive analytics into a testing framework can help reduce costs, improve quality and make better decisions.
Lean Business Analysis and UX Runway - Natalie WarnertNatalie Warnert
How to integrate BAs and UX in a Agile/Lean environment to create an MVP to learn while reducing potential waste. Presented at Lviv IT Arena, 2015 in Lviv, Ukraine by Natalie Warnert, October 3, 2015
www.nataliewarnert.com
Lean Business Analysis and UX Runway: Managing Value by Reducing Waste (Natal...IT Arena
The document discusses how business analysts and UX professionals can collaborate effectively in an Agile environment through a process called the "Analyst and UX Runway". This process involves business analysts and UX professionals working together throughout the product development lifecycle from initial planning through execution and review, with the goal of continuously delivering value to customers through short iterations of planning, development and feedback. The Analyst and UX Runway approach aims to balance upfront planning with flexibility to incorporate frequent customer feedback.
DV 2016: Building a Culture of Testing and OptimizationTealium
This document discusses building a culture of testing and optimization. It outlines key steps to create an effective test and learn organization, including defining roles like sponsors, ideators, executors and analyzers. It emphasizes the importance of developing a testing plan, conducting regular testing meetings, and standardizing the testing process. The overall message is that organizations should start with basic testing to establish processes and not panic if early tests show no significant results, as the goal is to learn through testing.
This document discusses managing quality on projects. It explains that quality should be defined by end users, not those doing the work. It also outlines the three main stages of managing project quality: 1) Planning and defining quality by establishing standards upfront, 2) Undertaking quality assurance to meet the plan, and 3) Controlling quality throughout the project by monitoring and testing. Quality management aims to satisfy user needs and prevent defects. A quality plan should engage stakeholders and describe how quality requirements will be achieved.
This document discusses measuring team effectiveness through metrics focused on outcomes rather than outputs. It provides examples of metrics that measure building the right thing, building the thing right, and building in a sustainable way. Specific metrics discussed include activation rate, cycle time, flow, waste elimination, release confidence, team health, quality and incident response times. The document emphasizes using metrics for improvement and having responsible conversations about the data.
The document provides an overview of building a quality testing framework. It discusses setting goals, defining a vision and timeline, establishing processes and roadmaps, gaining acceptance, and making improvements. Key aspects include test planning, case design, defect management, metrics, involvement of QA early, and continuous improvement. The overall message is that quality assurance principles applied throughout the development and testing process can help prevent bugs and ensure high quality work.
Similar to Using Checklists to Increase Productiviity and Consistency in Publication Tasks - Spectrum 2018 (20)
This document provides tips and tools to enhance productivity as an editor in Microsoft Word. It discusses Word add-ins, keyboard shortcuts, the quick access toolbar, editing tools tab, auto correct list, spell check dictionaries, navigation pane, find and replace features using wildcards and macros, and creating editing checklists. The document encourages editors to customize their Word experience through these various tools to work more efficiently and consistently.
Expanding your toolbox to make yourself a more productive editor schrankKelly Schrank, MA, ELS
The document discusses various tools in Microsoft Word that can help editors improve productivity. It covers Word add-ins, keyboard shortcuts, the quick access toolbar, the editing tools tab, auto correct lists, custom dictionaries, the navigation pane, find and replace features including wildcards and macros, and editing checklists. The presentation provides examples and instructions for customizing and utilizing these various Word tools to streamline editing workflows.
This document discusses networking myths and provides tips for introverts on how to network effectively. Some common myths are that everyone likes networking and are naturally good at it, when in reality most people find it difficult and an acquired skill. The document recommends choosing networking events carefully, preparing by rehearsing questions and answers, focusing on others by acting as a host to feel more comfortable, and following up after to build real connections and reap the benefits of networking. Introverts can find networking draining but can form deeper connections by having quality conversations with a few people. With practice and the right approach, anyone can learn to network successfully.
Microlearning involves short learning events that focus on a narrow topic or concept. It is characterized by brevity, with lessons typically lasting less than 5 minutes. Microlearning content can take various forms, including presentations, activities, games, videos, and quizzes. It is designed to quickly close a small knowledge or skill gap. Learners prefer microlearning because it allows them to learn topics in short bursts and keep their attention through varied content and interactivity.
This document discusses effective communication strategies with coworkers. It notes that while technical communicators often advise knowing your audience, this is rarely applied to internal communications. It explores factors like media richness theory and cultural preferences that influence communication choices. Media richness theory states richer mediums like face-to-face are best for complex topics that could be misunderstood. However, individual and cultural preferences must also be considered. The document recommends determining communication preferences through discussion and trial-and-error with coworkers.
Handouts for the Leadership Program at the Society for Technical Communication Summit 2015
Regional Conference roundtable, presented by Jessica Rineer and Kelly Schrank
The document provides tips for editing one's own writing. It recommends reading work on a computer and in print to identify paragraphs, sentences, and words that are too long. Editing involves breaking up long paragraphs, simplifying complex sentences, and replacing verbose words to improve the overall flow and readability of a document.
Bringing the benefits of stc to work kelly schrank stc summit 2012Kelly Schrank, MA, ELS
This document discusses the benefits of a new software product called ExampleSoft. ExampleSoft is an all-in-one business management tool that allows users to track finances, inventory, customers and more from a single dashboard. It aims to make managing small businesses easier by consolidating important functions into one integrated system.
Joyce M Sullivan, Founder & CEO of SocMediaFin, Inc. shares her "Five Questions - The Story of You", "Reflections - What Matters to You?" and "The Three Circle Exercise" to guide those evaluating what their next move may be in their careers.
Success is often not achievable without facing and overcoming obstacles along the way. To reach our goals and achieve success, it is important to understand and resolve the obstacles that come in our way.
In this article, we will discuss the various obstacles that hinder success, strategies to overcome them, and examples of individuals who have successfully surmounted their obstacles.
We recently hosted the much-anticipated Community Skill Builders Workshop during our June online meeting. This event was a culmination of six months of listening to your feedback and crafting solutions to better support your PMI journey. Here’s a look back at what happened and the exciting developments that emerged from our collaborative efforts.
A Gathering of Minds
We were thrilled to see a diverse group of attendees, including local certified PMI trainers and both new and experienced members eager to contribute their perspectives. The workshop was structured into three dynamic discussion sessions, each led by our dedicated membership advocates.
Key Takeaways and Future Directions
The insights and feedback gathered from these discussions were invaluable. Here are some of the key takeaways and the steps we are taking to address them:
• Enhanced Resource Accessibility: We are working on a new, user-friendly resource page that will make it easier for members to access training materials and real-world application guides.
• Structured Mentorship Program: Plans are underway to launch a mentorship program that will connect members with experienced professionals for guidance and support.
• Increased Networking Opportunities: Expect to see more frequent and varied networking events, both virtual and in-person, to help you build connections and foster a sense of community.
Moving Forward
We are committed to turning your feedback into actionable solutions that enhance your PMI journey. This workshop was just the beginning. By actively participating and sharing your experiences, you have helped shape the future of our Chapter’s offerings.
Thank you to everyone who attended and contributed to the success of the Community Skill Builders Workshop. Your engagement and enthusiasm are what make our Chapter strong and vibrant. Stay tuned for updates on the new initiatives and opportunities to get involved. Together, we are building a community that supports and empowers each other on our PMI journeys.
Stay connected, stay engaged, and let’s continue to grow together!
About PMI Silver Spring Chapter
We are a branch of the Project Management Institute. We offer a platform for project management professionals in Silver Spring, MD, and the DC/Baltimore metro area. Monthly meetings facilitate networking, knowledge sharing, and professional development. For more, visit pmissc.org.
A Guide to a Winning Interview June 2024Bruce Bennett
This webinar is an in-depth review of the interview process. Preparation is a key element to acing an interview. Learn the best approaches from the initial phone screen to the face-to-face meeting with the hiring manager. You will hear great answers to several standard questions, including the dreaded “Tell Me About Yourself”.
Learnings from Successful Jobs SearchersBruce Bennett
Are you interested to know what actions help in a job search? This webinar is the summary of several individuals who discussed their job search journey for others to follow. You will learn there are common actions that helped them succeed in their quest for gainful employment.
In the intricate tapestry of life, connections serve as the vibrant threads that weave together opportunities, experiences, and growth. Whether in personal or professional spheres, the ability to forge meaningful connections opens doors to a multitude of possibilities, propelling individuals toward success and fulfillment.
Eirini is an HR professional with strong passion for technology and semiconductors industry in particular. She started her career as a software recruiter in 2012, and developed an interest for business development, talent enablement and innovation which later got her setting up the concept of Software Community Management in ASML, and to Developer Relations today. She holds a bachelor degree in Lifelong Learning and an MBA specialised in Strategic Human Resources Management. She is a world citizen, having grown up in Greece, she studied and kickstarted her career in The Netherlands and can currently be found in Santa Clara, CA.
Using Checklists to Increase Productiviity and Consistency in Publication Tasks - Spectrum 2018
1. Using Checklists to Increase
Productivity and Consistency in
Publication Tasks
Kelly Schrank
@headbookworm headbookworm@gmail.com
2. #stc_spectrum
Agenda
Introduction
Types of Tasks
Elements of a Good Checklist
Benefits of a Good Checklist
How Do You Know You Have Good Checklists?
Questions? Testimonies?
3. #stc_spectrum
Introduction
• The Checklist Manifesto by Atul Gawande
• Popular tool in workplaces
Surgery checklists save lives
Aviation checklists are essential components in cockpits
Construction checklists keep large scale projects on time and
safe
4. #stc_spectrum
Introduction
• The Checklist Specialist
• Advocate for a special kind of checklist
Create them for your use
Test and rework to get it right, then update and change as
needed
Create them for editing tasks, writing projects, social media
work
5. #stc_spectrum
What Types of Tasks Need Checklists?
Multiple repeated tasks
Processes with lots of details
Processes with a lot of steps
Tasks within systems that change frequently
Docs with styles that change frequently
Similar tasks that have small details that are different
Tasks where you want to track metrics
6. #stc_spectrum
Elements of a Good Checklist
Be Specific
Don’t just say, “Check headings” on an editing
checklist
Say,
7. #stc_spectrum
Elements of a Good Checklist
Spell it out
Don’t just say, “Post event to Twitter” on a social media
checklist
Say,
• “Write a 280-word post with details of the event that
includes the following:
• Date
• Time
• Speaker
• Topic
• Location
• Address
• Ticket prices
• Day ticket sales close
8. #stc_spectrum
Elements of a Good Checklist
Provide every action step-by-step
Don’t brainstorm what needs to be done on a sheet
of paper and call that a checklist
List what needs to be done in the optimal order for it to be
done efficiently and correctly
Test, revise, test
9. #stc_spectrum
Elements of a Good Checklist
Add tracking items
Start and stop times
Due date
Level of difficulty
10. #stc_spectrum
Benefits of a Good Checklist
Using Checklists to Increase Productivity and
Consistency in Publication Tasks
11. #stc_spectrum
How Do You Know you Have Good Checklists?
When you have piece of mind when working on
something
When you start a new type of project and you feel lost
without a checklist
When you are confident you have completed a project
because you have checked everything off on your
checklist
12. #stc_spectrum
How Do You Know You Have Good Checklists?
When you find an error your editing checklist told you to
look for
When you almost forgot to post to that third social
media site until the checklist told you to post to it
When you are asked for metrics for how to do a future
project and you can confidently give an estimate
because you have the data in your checklists
14. #stc_spectrum
Resources
Gawande, Atul. The Checklist Manifesto: How to Get
Things Right. New York: Henry Holt & Company, 2010.
Rizzo, Paula. Listful Thinking: Using Lists to be More
Productive, Highly Successful and Less Stressed. New
York: Start Midnight, LLC. 2014.
Schrank, Kelly. “Using Editing Checklists for More
Efficient Editing.” AMWA Journal, 2013:164-166.
15. #stc_spectrum
Kelly Schrank
Contract Technical Writer and Medical Editor
@headbookworm
headbookworm@gmail.com
https://www.linkedin.com/in/kellyschrank/
https://headbookworm.com/
Thank You for Attending!
For a deeper dive, attend my STC webinar on May 9:
Using Checklists to Increase Consistency and Productivity
in Communications Tasks
Editor's Notes
As I said in my description for this session, this is an old school hack, a paper checklist, and you can use it for a variety of writing and editing tasks. I’ve got a lot to cover, so let’s get started.
Just to give you an idea of what we’ll cover in this short session…
I’ll provide an introduction to the types of checklists I use and some of my research into checklists for work tasks
I’ll offer some suggestions for the types of tasks that benefit the most from checklists
I’ll talk about the elements of a good checklist according to me for the way I use them to be more productive and consistent in my writing and editing tasks
I will preach the benefits of a good checklist, again, according to me, and the way that I use them
I’ll answer the question, How you do you know you have good checklists?
Then, if we have time, I welcome questions about how you can become a checklist specialist or testimonials about the joys and life-saving properties of checklists for those who already consider themselves checklist specialists.
Lots of people like checklists.
They have TO DO lists for daily tasks, packing lists for travel. Atul Gawande wrote a whole book on how checklists are used in a variety of industries to save lives, fly planes, and manage large-scale constructions projects.
I highly recommend this book; I have a resources slide with this and a couple of other resources on it.
A couple of takeaways from this book that I want to offer up for you up front
Mental fatigue is real….Gawande talks about this, but it also came up in another book I have in the resources, “It takes mental work to keep things filed and stored and organized in your brain. And I think we underestimate how taxing it is to think.” From a psychotherapist and psychiatrist. Do you want to spend your brain energy trying to remember something silly? Or using it to analyze data or rewrite a tough concept?
If you could be more efficient and productive, produce better quality work with less energy and feel better about it, why wouldn’t you? Gawande talks about how people think using a checklist is beneath them, they are too smart for that, they don’t need it. Maybe you don’t need it on your good days, when you’ve gotten enough sleep, have no interruptions, and are in a great mood, but what about those days when one of those things, or all of those things are off? The checklist is there for you, to make you be your better self, every day.
I am a self-proclaimed checklist specialist, and I have the cards to prove it!
I specialize in checklists for writing and editing tasks, just the type of stuff we do because I have experienced the benefits of a good checklist first hand and with the team I used to manage. But I have some particular requirements for good checklists, and I have listed some of them here….
First of all, these checklists are for you to use, so I can’t tell you what they should look like, and your boss shouldn’t be creating them for you, you need to create them for you. For teams, you can create one for the team if there is a task you all do and you need to be consistent in how you do them, but you have to work on the checklists together so they work for all of you. A checklist shouldn’t be punitive or a necessary evil…it’s a tool in your toolbox to do your job better, with less strife and more peace of mind.
You should be updating them and changing them as you job or the task changes, unless of course, you work never changes….but I don’t know anyone who has been able to do the same job the same way for years…there is always a new system, or a new task, or you learn that you were doing something wrong that you want to correct. There is always change….
Generally, you can create them for editing tasks, which is what I was using them for initially and where I have a lot of experience with them, but you can use them for writing tasks, or publication tasks, or social media work. For example, if you have certain types of documents, you edit or write, or if you create and publish social media content…any type of repeated task is a good candidate for a checklist. Let’s talk more about the types of tasks…
In my experience, tasks that are similar and repeated regularly are good candidates for a checklist.
For instance, as a medical editor, I would edit standard responses every day. I had to access the docs in systems that changed over the 8 years I worked there…we used 3 or 4 different systems, and there would be always be updates or changes to the processes or systems. Documenting the steps in the checklists helped me remember the latest process and requirements and perform the steps more efficiently without second-guessing myself.
The checklist also documented current style and formatting details, so I could be sure I was up to date with the latest style guide, something else that was always changing and evolving. Checking items off the checklist as I went along allowed me to start and stop an editing task without forgetting where I was and losing time duplicating my efforts.
So let’s get into the elements of a good checklist…forget what you’ve seen in editing or writing textbooks that are helping newbies learn what technical writing or editing are…most of you are professionals and need better tools.
I’ve seen many checklists that are generic, Check the headings. When you’re editing multiple clients with different styles with a tight deadline, this isn’t helpful. Notate and show what the headings should look like, so you know at a glance how they should look.
If you have multiple clients for similar types of documents, as I do, you will get confused about which client needs which header or which abbreviation they use. You will forget if you checked that item for this document or the other one…I am telling you this from experience.
Don’t just assume that you’ll remember all the steps in the process of the tasks, or the exact style items, write it all down.
And be sure to group like activities together when possible on your checklist….the goal is efficiency, so grouping all your find and replace tasks together, for example, is more efficient and when you clean up your document , you can focus on more important details.
Similar to the previous slide, spell everything out…step by step, like a procedure for yourself.
Are there items you are afraid you will forget, or that you have forgotten when doing a task in the past? Write it down. The checklist is there for you.
This is one I struggle with…there are a lot of steps to publicizing an event, and I only do it once a month for the chapter…but some things have to be done in a specific order, like you can’t include a link to the event if it is not created in EventBrite first, and for other things, it helps if you do it in a specific order, like writing the LinkedIn post, which can be longer, then stealing text from it to post to Twitter, which has shorter character limits. And how do you keep track of the character limits or the image requirements of the different platforms. You can put that all on a checklist, so you don’t forget.
You can also use the sheet to track little details specific to a task in case there are things that cropped up that were not on the checklist. I find this sometimes with new therapeutic area or products for the pharmaceutical editing I do. I have some common terms in the checklist and many more in the style guide, but with a new product or indication for a product, there may be a word I have never seen before, and if I go to the trouble of looking it up in a reference to find out what’s the proper way to use the word, and then I run across it again, I can go back to my last checklist for that product or indication and find out what I did last time.
Keeping your checklists up to date can be a challenge, but it will be there when you need it.
Expanding on the need for step-by-step actions…
This is not a one and done. Sure, you can brainstorm what needs to be done for a particular task, but don’t call that a checklist. Get it all down on paper, rearrange it until it seems to make sense. Then test it with a real task, and edit it as you go. When you are done with the task, update the checklist, print it out and test it again. You are not stuck with your original sequence of steps…try something new if some of the steps don’t seem to be working. Test it ,update it, then test it again.
Writing all of the steps down is where you get the productivity benefits of a checklist…anyone ever get interrupted in the middle of a task? Oh, me neither, but if you did, and you had it marked on the checklist where you stopped, then you would know where to start back up again, without having to think about, oh, where was I? Did I do this step yet? Have you ever forgotten something because you thought you had done it? Have you ever starting doing something to a document, like checking the headings or finding an abbreviation that’s often spelled wrong, then realized, wait I already did this.? Again, this is where the checklist helps.
Length of document
Author, team, or topic
When you use paper checklists and keep them, they allow you to more easily remember what was going on with a particular tasks if asked about it later. And if you didn’t have time to check or do everything in your checklist, you will have a note of it and your tracking information may show why (rush, long document, troublesome author).
So let’s get back to the point of the talk….how do checklists make you more productive? How do they make you more consistent? I’ve touched on it throughout, but I’ll try to be more explicit.
I think that using an updated, detailed checklist for a particular task makes me more productive because it keeps me on task, allows me to stop and start back up with less loss of focus and certainly less worry, and it allows me to track metrics and accurately estimate future projects. It’s a nice motivational tool, too. You get to see your progress as you go, and if you do have good metrics, you’ll be able to better estimate how much longer the task will take.
Going through the process of establishing what needs to be done, organizing my tasks for optimal efficiency, and being able to follow a set list of items that I check off as I go allowed me to be more consistent in my editing, writing, and publication-type tasks. As an editor, especially, this ability to be consistent has been invaluable, but I think it’s helpful for lots of other tasks.
Because I have a lot to do in a short amount of time, because I value quality and consistency in the materials I edit and write, I like knowing I have done my best and the checklist documents all of that.
The title of my talk doesn’t mention “peace of mind” but picking up where you left off with confidence is sometimes priceless. There are always interruptions, distractions, “Off days.”
I’m an experienced professional. I know what to do when I get a project. But as an experienced professional, who is good at what I do, like many of you, I also end up with a lot of projects. In my last position, I had many different types of projects, different clients, different systems, different types of work. Having a checklist for many of the tasks helped me keep them all straight and know where I am with any of them at any one time.
Have you ever had a project or document drag on until you were sick of it? You just want it off your plate…how do you know if you have done enough? Sometimes checklist can help you know you have done enough, that it’s ready to move off your plate.
The first one has happened to me more times that I care to mention…you get caught up in a messy document and there is so much to fix that you forget to check something. Sometimes, it is something small, but other times, it’s important, like misspelling the product name or headings with typos.
The second one has happened, and I have people here to prove it, who have caught it for me, because I was not using a checklist and just shooting from the hip.
As I am growing my freelance business, the metrics have become really important. I have the metrics from when I edited a certain type of document for multiple clients where I used to work, and now I am gathering them for new clients who want to know, well, how much is this going to cost me or how long will this take.
I will also post this to Slide Share and if you look at my Slide Share page, you’ll see an infographic, How to Create an Editing Checklist that might be helpful. They’ll both be on my website at some point as well.
Thank you everyone for attending. Feel free to contact me with questions…I’m pretty accessible. I also have some business cards up here….