Who is responsible for testing on agile teams? The answer is “Everybody”—and yet this is rarely the case. Often the testers write their test cases in isolation and execute them after development is finished. Developers write their code without talking to the testers except to understand how to reproduce the latest discovered defect. Product owners elaborate requirements in isolation and then hand them off to the team only to check back at the end of the sprint. Business analysts spend their time working on documents that have questionable usefulness. Join Cheezy Morgan as he paints a different picture. With the help of volunteers from the audience performing skits, Cheezy demonstrates practices that not only foster collaboration among all team members but also dramatically improve quality. These practices help teams achieve a better flow resulting in a more streamlined development effort. This new picture is a picture of teamwork and quality assurance.
A Research Study into DevOps Bottlenecks as presented at Codemash 2018Baruch Sadogursky
By Baruch Sadogursky
We asked the Fortune 500 software delivery leaders what holds them back. This talk is the analysis of their insights on what bottlenecks they encountered in their DevOps journey.
Software Metrics: Taking the Guesswork Out of Software ProjectsTechWell
Why bother with measurement and metrics? If you never use the data you collect, this is a valid question—and the answer is “Don’t bother, it’s a waste of time.” In that case, you’ll manage with opinions, personalities, and guesses—or even worse, misconceptions and misunderstandings. Based on his more than forty years of software and systems development experience, Ed Weller describes reasons for measurement, key measures in both traditional and agile environments, decisions enabled by measurement, and lessons learned from successful—and not so successful—measurement programs. Find out how to develop and maintain consistent data and valid measures so you can estimate reliably, deliver products with known quality, and have happy users and customers—the ultimate trailing indicator. Learn to manage projects dynamically with the support of current metrics and data from past projects to guide your management planning and control. Join Ed to explore how to invest in measurements that provide leading indicators to help you meet your company and customer goals.
Design for Testability: A Tutorial for Devs and TestersTechWell
Testability is the degree to which a system can be effectively and efficiently tested. This key software attribute indicates whether testing (and subsequent maintenance) will be easy and cheap—or difficult and expensive. In the worst case, a lack of testability means that some components of the system cannot be tested at all. Testability is not free; it must be explicitly designed into the system through adequate design for testability. Peter Zimmerer describes influencing factors (controllability, visibility, operability, stability, simplicity) and constraints (conflicting nonfunctional requirements, legacy code), and shares his experiences implementing and testing highly-testable software. Peter offers practical guidance on the key actions: (1) designing well-defined control and observation points in the architecture, and (2) specifying testability needs for test automation early. He shares creative and innovative approaches to overcome failures caused by deficiencies in testability. Peter presents a new, comprehensive strategy for testability design that can be implemented to gain the benefits in a cost-efficient manner.
Agile Success with Scrum: It’s All about the PeopleTechWell
This document summarizes an Agile conference session titled "Agile Success with Scrum: It’s All about the People" presented by Bob Hartman and Michael Vizdos. The session discussed why Scrum projects often fail according to surveys, with the top reason being issues related to people and culture. The presenters explored how teams often forget the human element of Agile frameworks. They also reviewed the Scrum values and emphasized the most important unspoken value is creating happiness among team members. Finally, the session proposed an approach for project success focusing on appreciating, protecting, and applauding team members to build respect, optimism, and pride.
Test Managers: How You Can Really Make a DifferenceTechWell
When leading a test team or working in an agile team, becoming a trusted advisor to other stakeholders is paramount. This requires three key skills: earning trust, giving advice, and building relationships. Join Julie Gardiner as she explores each of these skills, describing why and how a trusted advisor develops different “mindsets.” Julie shares a framework of “quick-wins” for test managers and team leaders who need to show the value of testing on projects. To help provide timely, relevant information to stakeholders, she shares seven powerful monitoring and predicting techniques. Julie demonstrates three objective measures showing how testing adds value to organizations. To make sure that everyone is on the same page, Julie urges managers to establish a foundation for testing through well-defined policy statements, agreed to and sanctioned by senior management. Receive a set of spreadsheets and utilities to support your activities as a test manager who really makes a difference.
Agile and CMMI: Yes, They Can Work TogetherTechWell
There is a common misconception that agile and CMMI cannot work together. CMMI is viewed as a documentation heavy, slow, process-driven model—the polar opposite of agile principles. The cost of documentation for an appraisal is viewed as another drawback. Join Ed Weller to see why a large organization chose to use the practices in the CMMI to complement agile, and a formal appraisal to improve and evaluate their performance. When mixing approaches that seem contradictory, the first step is to understand the benefits, drawbacks, and cost of each approach and then identify complementary additions. This includes myth busting the misperceptions about both agile and CMMI. The second step, using a formal CMMI appraisal to evaluate organizational performance, requires an understanding of the CMMI model that goes beyond a “checklist approach” requiring extensive documentation. Using lean principles, the appraisal team minimized “appraisal documentation” by using the day-to-day team output. Ed shows that agile and CMMI can be complementary due to executive leadership, lean implementation, and organization training, as demonstrated by a formal appraisal and business results.
Agile Program Management: Networks, Not HierarchiesTechWell
Johanna Rothman presented on "Agile Program Management: Networks, Not Hierarchies". She discussed organizing agile programs using small world networks of cross-functional feature teams rather than hierarchies. Programs should have short iterations and deliver working software frequently. Feature teams are autonomous but collaborate through communities, roadmaps and demos. Facilitation helps as programs scale.
Agile Redefines Global Economics: What Recent Data RevealsTechWell
Kent Beck, inventor of eXtreme Programming, defined agile success as delivering more useful functionality with fewer defects. Against that definition, early research revealed mixed success. Many organizations did not know how to measure and thus could not have “fact-based” conversations about productivity and cost. Some teams achieved faster delivery, but quality did not improve. Others found both. What factors made the difference? New benchmark analysis by QSM Associates reveals the latest productivity, time-to-market, quality, and cost patterns. As a result, we may be seeing a major shift in software economics made possible by the promises of agile. Michael Mah shares this latest research in the QSM SLIM industry database, which contains more than 10,000 completed projects—waterfall, agile, offshore, onshore—collected worldwide. Michael offers consulting tricks to accelerate your success. Learn how to derive your own measurements to inform your executive teams, quantify your successes, or spotlight areas that need help.
A Research Study into DevOps Bottlenecks as presented at Codemash 2018Baruch Sadogursky
By Baruch Sadogursky
We asked the Fortune 500 software delivery leaders what holds them back. This talk is the analysis of their insights on what bottlenecks they encountered in their DevOps journey.
Software Metrics: Taking the Guesswork Out of Software ProjectsTechWell
Why bother with measurement and metrics? If you never use the data you collect, this is a valid question—and the answer is “Don’t bother, it’s a waste of time.” In that case, you’ll manage with opinions, personalities, and guesses—or even worse, misconceptions and misunderstandings. Based on his more than forty years of software and systems development experience, Ed Weller describes reasons for measurement, key measures in both traditional and agile environments, decisions enabled by measurement, and lessons learned from successful—and not so successful—measurement programs. Find out how to develop and maintain consistent data and valid measures so you can estimate reliably, deliver products with known quality, and have happy users and customers—the ultimate trailing indicator. Learn to manage projects dynamically with the support of current metrics and data from past projects to guide your management planning and control. Join Ed to explore how to invest in measurements that provide leading indicators to help you meet your company and customer goals.
Design for Testability: A Tutorial for Devs and TestersTechWell
Testability is the degree to which a system can be effectively and efficiently tested. This key software attribute indicates whether testing (and subsequent maintenance) will be easy and cheap—or difficult and expensive. In the worst case, a lack of testability means that some components of the system cannot be tested at all. Testability is not free; it must be explicitly designed into the system through adequate design for testability. Peter Zimmerer describes influencing factors (controllability, visibility, operability, stability, simplicity) and constraints (conflicting nonfunctional requirements, legacy code), and shares his experiences implementing and testing highly-testable software. Peter offers practical guidance on the key actions: (1) designing well-defined control and observation points in the architecture, and (2) specifying testability needs for test automation early. He shares creative and innovative approaches to overcome failures caused by deficiencies in testability. Peter presents a new, comprehensive strategy for testability design that can be implemented to gain the benefits in a cost-efficient manner.
Agile Success with Scrum: It’s All about the PeopleTechWell
This document summarizes an Agile conference session titled "Agile Success with Scrum: It’s All about the People" presented by Bob Hartman and Michael Vizdos. The session discussed why Scrum projects often fail according to surveys, with the top reason being issues related to people and culture. The presenters explored how teams often forget the human element of Agile frameworks. They also reviewed the Scrum values and emphasized the most important unspoken value is creating happiness among team members. Finally, the session proposed an approach for project success focusing on appreciating, protecting, and applauding team members to build respect, optimism, and pride.
Test Managers: How You Can Really Make a DifferenceTechWell
When leading a test team or working in an agile team, becoming a trusted advisor to other stakeholders is paramount. This requires three key skills: earning trust, giving advice, and building relationships. Join Julie Gardiner as she explores each of these skills, describing why and how a trusted advisor develops different “mindsets.” Julie shares a framework of “quick-wins” for test managers and team leaders who need to show the value of testing on projects. To help provide timely, relevant information to stakeholders, she shares seven powerful monitoring and predicting techniques. Julie demonstrates three objective measures showing how testing adds value to organizations. To make sure that everyone is on the same page, Julie urges managers to establish a foundation for testing through well-defined policy statements, agreed to and sanctioned by senior management. Receive a set of spreadsheets and utilities to support your activities as a test manager who really makes a difference.
Agile and CMMI: Yes, They Can Work TogetherTechWell
There is a common misconception that agile and CMMI cannot work together. CMMI is viewed as a documentation heavy, slow, process-driven model—the polar opposite of agile principles. The cost of documentation for an appraisal is viewed as another drawback. Join Ed Weller to see why a large organization chose to use the practices in the CMMI to complement agile, and a formal appraisal to improve and evaluate their performance. When mixing approaches that seem contradictory, the first step is to understand the benefits, drawbacks, and cost of each approach and then identify complementary additions. This includes myth busting the misperceptions about both agile and CMMI. The second step, using a formal CMMI appraisal to evaluate organizational performance, requires an understanding of the CMMI model that goes beyond a “checklist approach” requiring extensive documentation. Using lean principles, the appraisal team minimized “appraisal documentation” by using the day-to-day team output. Ed shows that agile and CMMI can be complementary due to executive leadership, lean implementation, and organization training, as demonstrated by a formal appraisal and business results.
Agile Program Management: Networks, Not HierarchiesTechWell
Johanna Rothman presented on "Agile Program Management: Networks, Not Hierarchies". She discussed organizing agile programs using small world networks of cross-functional feature teams rather than hierarchies. Programs should have short iterations and deliver working software frequently. Feature teams are autonomous but collaborate through communities, roadmaps and demos. Facilitation helps as programs scale.
Agile Redefines Global Economics: What Recent Data RevealsTechWell
Kent Beck, inventor of eXtreme Programming, defined agile success as delivering more useful functionality with fewer defects. Against that definition, early research revealed mixed success. Many organizations did not know how to measure and thus could not have “fact-based” conversations about productivity and cost. Some teams achieved faster delivery, but quality did not improve. Others found both. What factors made the difference? New benchmark analysis by QSM Associates reveals the latest productivity, time-to-market, quality, and cost patterns. As a result, we may be seeing a major shift in software economics made possible by the promises of agile. Michael Mah shares this latest research in the QSM SLIM industry database, which contains more than 10,000 completed projects—waterfall, agile, offshore, onshore—collected worldwide. Michael offers consulting tricks to accelerate your success. Learn how to derive your own measurements to inform your executive teams, quantify your successes, or spotlight areas that need help.
Designing Your Team and Organization for InnovationTechWell
If innovation is not part of your team or organizational DNA, your company risks falling behind its competitors, losing market share, and demoralizing your best talent. And yet, you cannot create an innovative organization by simply saying “Be innovative” or adding it to the company values statement. Innovation requires a solid understanding of what motivates people and a deep examination of organizational structure, culture, and leadership styles—such as top-down project control or directive leadership—that may be barriers to innovation. Jim Elvidge explores a path to changing such an environment by improving team empowerment and creating an environment where it is safe to fail. Leaders championing this approach of “environment design” present people with a wider range of learning experiences, resulting in increased responsiveness to change, unleashed creativity, and greater job satisfaction. Learn how to use thinking and analysis tools—including double-loop learning and current reality trees—to find and remove your impediments to innovation.
The Google Hacking Database: A Key Resource to Exposing VulnerabilitiesTechWell
We all know the power of Google—or do we? Two types of people use Google: normal users like you and me, and the not-so-normal users—the hackers. What types of information can hackers collect from Google? How severe is the damage they can cause? Is there a way to circumvent this hacking? As a security tester, Kiran Karnad uses the GHDB (Google Hacking Database) to ensure their product will not be the next target for hackers. Kiran describes how to effectively use Google the way hackers do, using advanced operators, locating exploits and finding targets, network mapping, finding user names and passwords, and other secret stuff. Kiran provides a recipe of five simple security searches that work. Learn how to automate the Google Hacking Database using Python so security tests can be incorporated as a part of the SDLC for the next product you develop.
Influence Strategies for Software ProfessionalsTechWell
You’ve tried and tried to convince people of your position. You’ve laid out your logical arguments on impressive PowerPoint slides—but you are still not able to sway them. Cognitive scientists understand that the approach you are taking is rarely successful. Often you must speak to others’ subconscious motivators rather than their rational, analytic side. Linda Rising shares influence strategies that you can use to more effectively convince others to see things your way. These strategies take advantage of a number of hardwired traits: liking—we like people who are like us; reciprocity—we repay in kind; social proof—we follow the lead of others similar to us; consistency—we align ourselves with our previous commitments; authority—we defer to authority figures; and scarcity—we want more of something when there is less to be had. Join Linda to learn how to build on these traits as a way of bringing others to your side. Use this valuable toolkit in addition to the logical left-brain techniques on which we depend.
Each time a new feature is added to a product, developers need to consider the security risk implications, find ways to securely implement the function, and develop tests to confirm that the risk is gone or significantly lowered. Laurie Williams shares a Wideband Delphi practice called Protection Poker she's employed as a collaborative, interactive, and informal agile structure for "misuse case" development and threat modeling. Laurie shares the case study results of a software development team at RedHat that used Protection Poker to identify security risks, find ways to mitigate those risks, and increase security knowledge throughout the team. In this session, Laurie leads an interactive Protection Poker exercise in which you and other participants analyze the security risk of sample new features and learn to collaboratively think like an attacker. Participants will discuss implementation and testing strategies for the sample features to discover first hand the opportunities and challenges a security focus brings to development.
Tests and Requirements: Like Ham and Eggs, Sugar and Spice, Lucy and DesiTechWell
The practice of agile software development requires a clear understanding of business needs. Misunderstanding requirements causes waste, slipped schedules, and mistrust within the organization. Developers implement their perceived interpretation of requirements; testers test against their perceptions. Disagreement can arise about implementation defects, when the cause is really a disagreement about the requirement. Ken Pugh shows how acceptance tests decrease requirements misunderstandings by both developers and testers. A testable requirement provides a single source that serves as the analysis document, acceptance criteria, regression test suite, and progress tracker for any given feature. Explore the creation, evaluation, and use of testable requirements by the business and developers. Join Ken to examine how to transform requirements into stories, small units of work that have business value, small implementation effort, and easy-to-understand acceptance tests. Learn how testers and requirement elicitors can work together to create acceptance tests prior to implementation.
Governing Agile Teams: Disciplined Strategies to Increase Agile EffectivenessTechWell
Many organizations have successfully adopted agile on a subset of their projects, while, at the same time, struggled to do so across entire departments. A common challenge is the need to overhaul the IT governance strategy so that it will work with agile teams. This is a serious issue for governance bodies with little or no practical agile experience, particularly when experience shows that traditional governance strategies increase the risk of failure on agile projects. Scott Ambler introduces The Disciplined Agile Delivery framework for managing and monitoring enterprise agile teams. This framework goes beyond offering an IT governance strategy to provide advanced strategies such as development intelligence and the goal-question-metric measurement approach. Learn the do’s and don’ts of governing agile teams, how governance fits in and enhances the agile project lifecycle, how to measure agile teams, and most importantly, why teams should demand good governance.
Seven Keys to Navigating Your Agile Testing TransitionTechWell
So you’ve “gone agile” and have been relatively successful for a year or so. But how do you know how well you’re really doing? And how do you continuously improve your practices? And when things get rocky, how do you handle the challenges without reverting to old habits? You realize that the path to high-performance agile testing isn’t easy or quick. It also helps to have a guide. So consider this workshop your guide to ongoing, improved, and sustained high-performance. Join seasoned agile testing coach Bob Galen as he share lessons from his most successful agile testing transitions. You’ll explore actual team case studies for building team skills, embracing agile requirements, fostering customer interaction, building agile automation, driving business value, and testing at-scale stories of agile testing excellence. You’ll examine the mistakes, adjustments, and the successes—so you’ll learn how to react to real-world contexts. Leave with a better view of your team’s strengths, weaknesses, and where you need to focus to improve.
How to Jumpstart Enterprise Agile AdoptionTechWell
- Alan Padula presented on how to jumpstart enterprise agile adoption based on his experience leading Intuit Financial Services' (IFS) transformation to agile.
- IFS followed Kotter's 8-step change model, starting with establishing urgency and guiding teams, then getting the vision right and communicating it. They enabled action through extensive training, transition elements, and governance processes. Short-term wins and continuous improvement helped make the change stick.
- Key lessons included focusing on promoters over naysayers, allocating dedicated resources, investing in training and coaches, finding leaders to drive the change, and accepting it takes time for a mindset change.
Data Warehouse Testing: It’s All about the PlanningTechWell
Today’s data warehouses are complex and contain heterogeneous data from many different sources. Testing these warehouses is complex, requiring exceptional human and technical resources. So how do you achieve the desired testing success? Geoff Horne believes that it is through test planning that includes technical artifacts such as data models, business rules, data mapping documents, and data warehouse loading design logic. Wayne shares planning checklists, a test plan outline, concepts for data profiling, and methods for data verification. He demonstrates how to effectively create a test strategy to discover empty fields, missing records, truncated data, duplicate records, and incorrectly applied business rules—all of which can dramatically impact the usefulness of the data warehouse. Learn common pitfalls, which can cost your business hundreds of thousands of dollars or more, when test planning shortcuts are taken. If you work in an environment that often performs data warehouse testing without proper planning and technical skills, this session is for you.
Patterns of Automation: Simplify Your Test CodeTechWell
The document summarizes a presentation on patterns of automation for simplifying test code. It discusses reasons to automate testing like allowing exploration of different browsers, devices and security aspects. It presents patterns like specification by example, acceptance test driven development, and using page objects. It emphasizes keeping test code clean and not automating more than needed.
The document describes the services offered by 24Slides, an online presentation design company. They provide slide design and creation within 24 hours for various monthly subscription plans, starting at $10 per slide. They have a team of designers that create hundreds of thousands of slides each year for clients worldwide. The company aims to empower talent in emerging markets by investing profits into educating and providing benefits for their employees.
The document discusses gamification principles for designing games and motivating user behavior. It describes how games involve setting SMART goals, making actions explicit, providing clear feedback on progress. Games create a sense of mastery, progression and autonomy through increasing challenges. However, gamification applied to work must consider how game and work goals align. Understanding user motivations through personas is key to designing effective gamification. Feedback from target users should be used to refine the approach.
Many teams have a relatively easy time adopting the tactical aspects of agile methodologies. Usually a few classes, some tools introduction, and a bit of practice lead teams toward a fairly efficient and effective adoption. However, these teams often get “stuck” and begin to regress or simply start going through the motions—neither maximizing their agile performance nor delivering as much value as they could. Borrowing from his experience and lean software development methods, Bob Galen examines essential patterns—the thinking models of mature agile teams—so you can model them within your own teams. Along the way, you’ll examine patterns for large-scale emergent architecture, relentless refactoring, quality on all fronts, pervasive product owners, lean work queues, providing total transparency, saying No, and many more. Bob also explores why there is still the need for active and vocal leadership in defending, motivating, and holding agile teams accountable.
The document discusses focusing on and using one's talents and strengths. It emphasizes that everyone has natural talents that can be productively applied. When people use their strengths in their work and daily lives, they are more engaged, have better quality of life, and achieve more. The key is to identify one's talents and strengths and maximize them.
Django vs Laravel Which Backend Framework is Better & Why.pdfTemok IT Services
Choosing a web framework between Django vs Laravel is a challenge in web development. Web frameworks work like a skeleton on which you’ll develop or build your applications. Django and Laravel both are very important frameworks.
https://www.temok.com/blog/django-vs-laravel/
The document describes how a balanced team at Philosophie helped a 161-year-old accounting company innovate by leveraging agile practices. The team included designers, engineers, consultants, and others. Through collaborative exercises, user research, testing, and an inclusive development process, the team was able to build a minimum viable product in 6 weeks that gained user validation and client buy-in.
PowerPoint presentation on Agile software development and Scrum. First and foremost it´s not about tools or processes. It´s about the mindset needed to be successful in delivering valuable software to the customer
This document discusses how Agile has become dead due to common misinterpretations and misapplications of its principles. While Agile and Scrum were developed decades ago, many companies have lost sight of their original purpose to deliver early value to customers. Agile is often mistakenly equated with Scrum processes and tools rather than seen as a mindset. As a result, developers, customers, and stakeholders are unhappy and value is not being delivered. The document argues that for Agile to be revived, its focus must shift back to principles of individuals, interactions, and responding to change over rigid processes and metrics.
Yoast’s small seo guide to optimize your website small seo-guideLaura Curso
This document provides an overview of keyword research and strategy. It explains that keyword research involves coming up with an extensive list of keywords a company would like to rank for. This helps discover what search terms the target audience uses and what a company should aim to rank for. Proper keyword research is important because it identifies the specific terms the audience uses, rather than terms a company uses internally. Understanding the audience's keywords ensures a company optimizes for what people actually search.
This document provides an overview of keyword research and strategy. It explains that keyword research is important to understand the language your audience uses when searching so you can optimize your site for relevant terms. Keywords can be single words or multi-word phrases. The keyword strategy should include keywords that fit your site's topic to avoid disappointing users. Keyword research should be done regularly as markets and products evolve over time. Repeating the research ensures your keyword strategy stays up-to-date.
Yoast’s small seo guide to optimize your website communitymartas
This document provides an overview of keyword research and strategy. It explains that keyword research is important to understand the language your audience uses when searching so you can optimize your site accordingly. Keywords can be single words or keyphrases with multiple words. The keyword research process should be repeated regularly as products and markets evolve. A keyword strategy should ensure keywords fit the content on your site to avoid disappointing users. The document recommends various Yoast resources for further reading on keyword research best practices.
Yoast’s small seo guide to optimize your website small seo-guideMaría Alvaro
This document provides an overview of keyword research and strategy. It explains that keyword research is important to understand the language your audience uses when searching so you can optimize your site for relevant terms. Keywords can be single words or keyphrases with multiple words. The keyword research process should be repeated regularly as products and markets evolve. A good keyword strategy ensures the keywords fit your site so users find relevant information.
Designing Your Team and Organization for InnovationTechWell
If innovation is not part of your team or organizational DNA, your company risks falling behind its competitors, losing market share, and demoralizing your best talent. And yet, you cannot create an innovative organization by simply saying “Be innovative” or adding it to the company values statement. Innovation requires a solid understanding of what motivates people and a deep examination of organizational structure, culture, and leadership styles—such as top-down project control or directive leadership—that may be barriers to innovation. Jim Elvidge explores a path to changing such an environment by improving team empowerment and creating an environment where it is safe to fail. Leaders championing this approach of “environment design” present people with a wider range of learning experiences, resulting in increased responsiveness to change, unleashed creativity, and greater job satisfaction. Learn how to use thinking and analysis tools—including double-loop learning and current reality trees—to find and remove your impediments to innovation.
The Google Hacking Database: A Key Resource to Exposing VulnerabilitiesTechWell
We all know the power of Google—or do we? Two types of people use Google: normal users like you and me, and the not-so-normal users—the hackers. What types of information can hackers collect from Google? How severe is the damage they can cause? Is there a way to circumvent this hacking? As a security tester, Kiran Karnad uses the GHDB (Google Hacking Database) to ensure their product will not be the next target for hackers. Kiran describes how to effectively use Google the way hackers do, using advanced operators, locating exploits and finding targets, network mapping, finding user names and passwords, and other secret stuff. Kiran provides a recipe of five simple security searches that work. Learn how to automate the Google Hacking Database using Python so security tests can be incorporated as a part of the SDLC for the next product you develop.
Influence Strategies for Software ProfessionalsTechWell
You’ve tried and tried to convince people of your position. You’ve laid out your logical arguments on impressive PowerPoint slides—but you are still not able to sway them. Cognitive scientists understand that the approach you are taking is rarely successful. Often you must speak to others’ subconscious motivators rather than their rational, analytic side. Linda Rising shares influence strategies that you can use to more effectively convince others to see things your way. These strategies take advantage of a number of hardwired traits: liking—we like people who are like us; reciprocity—we repay in kind; social proof—we follow the lead of others similar to us; consistency—we align ourselves with our previous commitments; authority—we defer to authority figures; and scarcity—we want more of something when there is less to be had. Join Linda to learn how to build on these traits as a way of bringing others to your side. Use this valuable toolkit in addition to the logical left-brain techniques on which we depend.
Each time a new feature is added to a product, developers need to consider the security risk implications, find ways to securely implement the function, and develop tests to confirm that the risk is gone or significantly lowered. Laurie Williams shares a Wideband Delphi practice called Protection Poker she's employed as a collaborative, interactive, and informal agile structure for "misuse case" development and threat modeling. Laurie shares the case study results of a software development team at RedHat that used Protection Poker to identify security risks, find ways to mitigate those risks, and increase security knowledge throughout the team. In this session, Laurie leads an interactive Protection Poker exercise in which you and other participants analyze the security risk of sample new features and learn to collaboratively think like an attacker. Participants will discuss implementation and testing strategies for the sample features to discover first hand the opportunities and challenges a security focus brings to development.
Tests and Requirements: Like Ham and Eggs, Sugar and Spice, Lucy and DesiTechWell
The practice of agile software development requires a clear understanding of business needs. Misunderstanding requirements causes waste, slipped schedules, and mistrust within the organization. Developers implement their perceived interpretation of requirements; testers test against their perceptions. Disagreement can arise about implementation defects, when the cause is really a disagreement about the requirement. Ken Pugh shows how acceptance tests decrease requirements misunderstandings by both developers and testers. A testable requirement provides a single source that serves as the analysis document, acceptance criteria, regression test suite, and progress tracker for any given feature. Explore the creation, evaluation, and use of testable requirements by the business and developers. Join Ken to examine how to transform requirements into stories, small units of work that have business value, small implementation effort, and easy-to-understand acceptance tests. Learn how testers and requirement elicitors can work together to create acceptance tests prior to implementation.
Governing Agile Teams: Disciplined Strategies to Increase Agile EffectivenessTechWell
Many organizations have successfully adopted agile on a subset of their projects, while, at the same time, struggled to do so across entire departments. A common challenge is the need to overhaul the IT governance strategy so that it will work with agile teams. This is a serious issue for governance bodies with little or no practical agile experience, particularly when experience shows that traditional governance strategies increase the risk of failure on agile projects. Scott Ambler introduces The Disciplined Agile Delivery framework for managing and monitoring enterprise agile teams. This framework goes beyond offering an IT governance strategy to provide advanced strategies such as development intelligence and the goal-question-metric measurement approach. Learn the do’s and don’ts of governing agile teams, how governance fits in and enhances the agile project lifecycle, how to measure agile teams, and most importantly, why teams should demand good governance.
Seven Keys to Navigating Your Agile Testing TransitionTechWell
So you’ve “gone agile” and have been relatively successful for a year or so. But how do you know how well you’re really doing? And how do you continuously improve your practices? And when things get rocky, how do you handle the challenges without reverting to old habits? You realize that the path to high-performance agile testing isn’t easy or quick. It also helps to have a guide. So consider this workshop your guide to ongoing, improved, and sustained high-performance. Join seasoned agile testing coach Bob Galen as he share lessons from his most successful agile testing transitions. You’ll explore actual team case studies for building team skills, embracing agile requirements, fostering customer interaction, building agile automation, driving business value, and testing at-scale stories of agile testing excellence. You’ll examine the mistakes, adjustments, and the successes—so you’ll learn how to react to real-world contexts. Leave with a better view of your team’s strengths, weaknesses, and where you need to focus to improve.
How to Jumpstart Enterprise Agile AdoptionTechWell
- Alan Padula presented on how to jumpstart enterprise agile adoption based on his experience leading Intuit Financial Services' (IFS) transformation to agile.
- IFS followed Kotter's 8-step change model, starting with establishing urgency and guiding teams, then getting the vision right and communicating it. They enabled action through extensive training, transition elements, and governance processes. Short-term wins and continuous improvement helped make the change stick.
- Key lessons included focusing on promoters over naysayers, allocating dedicated resources, investing in training and coaches, finding leaders to drive the change, and accepting it takes time for a mindset change.
Data Warehouse Testing: It’s All about the PlanningTechWell
Today’s data warehouses are complex and contain heterogeneous data from many different sources. Testing these warehouses is complex, requiring exceptional human and technical resources. So how do you achieve the desired testing success? Geoff Horne believes that it is through test planning that includes technical artifacts such as data models, business rules, data mapping documents, and data warehouse loading design logic. Wayne shares planning checklists, a test plan outline, concepts for data profiling, and methods for data verification. He demonstrates how to effectively create a test strategy to discover empty fields, missing records, truncated data, duplicate records, and incorrectly applied business rules—all of which can dramatically impact the usefulness of the data warehouse. Learn common pitfalls, which can cost your business hundreds of thousands of dollars or more, when test planning shortcuts are taken. If you work in an environment that often performs data warehouse testing without proper planning and technical skills, this session is for you.
Patterns of Automation: Simplify Your Test CodeTechWell
The document summarizes a presentation on patterns of automation for simplifying test code. It discusses reasons to automate testing like allowing exploration of different browsers, devices and security aspects. It presents patterns like specification by example, acceptance test driven development, and using page objects. It emphasizes keeping test code clean and not automating more than needed.
The document describes the services offered by 24Slides, an online presentation design company. They provide slide design and creation within 24 hours for various monthly subscription plans, starting at $10 per slide. They have a team of designers that create hundreds of thousands of slides each year for clients worldwide. The company aims to empower talent in emerging markets by investing profits into educating and providing benefits for their employees.
The document discusses gamification principles for designing games and motivating user behavior. It describes how games involve setting SMART goals, making actions explicit, providing clear feedback on progress. Games create a sense of mastery, progression and autonomy through increasing challenges. However, gamification applied to work must consider how game and work goals align. Understanding user motivations through personas is key to designing effective gamification. Feedback from target users should be used to refine the approach.
Many teams have a relatively easy time adopting the tactical aspects of agile methodologies. Usually a few classes, some tools introduction, and a bit of practice lead teams toward a fairly efficient and effective adoption. However, these teams often get “stuck” and begin to regress or simply start going through the motions—neither maximizing their agile performance nor delivering as much value as they could. Borrowing from his experience and lean software development methods, Bob Galen examines essential patterns—the thinking models of mature agile teams—so you can model them within your own teams. Along the way, you’ll examine patterns for large-scale emergent architecture, relentless refactoring, quality on all fronts, pervasive product owners, lean work queues, providing total transparency, saying No, and many more. Bob also explores why there is still the need for active and vocal leadership in defending, motivating, and holding agile teams accountable.
The document discusses focusing on and using one's talents and strengths. It emphasizes that everyone has natural talents that can be productively applied. When people use their strengths in their work and daily lives, they are more engaged, have better quality of life, and achieve more. The key is to identify one's talents and strengths and maximize them.
Django vs Laravel Which Backend Framework is Better & Why.pdfTemok IT Services
Choosing a web framework between Django vs Laravel is a challenge in web development. Web frameworks work like a skeleton on which you’ll develop or build your applications. Django and Laravel both are very important frameworks.
https://www.temok.com/blog/django-vs-laravel/
The document describes how a balanced team at Philosophie helped a 161-year-old accounting company innovate by leveraging agile practices. The team included designers, engineers, consultants, and others. Through collaborative exercises, user research, testing, and an inclusive development process, the team was able to build a minimum viable product in 6 weeks that gained user validation and client buy-in.
PowerPoint presentation on Agile software development and Scrum. First and foremost it´s not about tools or processes. It´s about the mindset needed to be successful in delivering valuable software to the customer
This document discusses how Agile has become dead due to common misinterpretations and misapplications of its principles. While Agile and Scrum were developed decades ago, many companies have lost sight of their original purpose to deliver early value to customers. Agile is often mistakenly equated with Scrum processes and tools rather than seen as a mindset. As a result, developers, customers, and stakeholders are unhappy and value is not being delivered. The document argues that for Agile to be revived, its focus must shift back to principles of individuals, interactions, and responding to change over rigid processes and metrics.
Yoast’s small seo guide to optimize your website small seo-guideLaura Curso
This document provides an overview of keyword research and strategy. It explains that keyword research involves coming up with an extensive list of keywords a company would like to rank for. This helps discover what search terms the target audience uses and what a company should aim to rank for. Proper keyword research is important because it identifies the specific terms the audience uses, rather than terms a company uses internally. Understanding the audience's keywords ensures a company optimizes for what people actually search.
This document provides an overview of keyword research and strategy. It explains that keyword research is important to understand the language your audience uses when searching so you can optimize your site for relevant terms. Keywords can be single words or multi-word phrases. The keyword strategy should include keywords that fit your site's topic to avoid disappointing users. Keyword research should be done regularly as markets and products evolve over time. Repeating the research ensures your keyword strategy stays up-to-date.
Yoast’s small seo guide to optimize your website communitymartas
This document provides an overview of keyword research and strategy. It explains that keyword research is important to understand the language your audience uses when searching so you can optimize your site accordingly. Keywords can be single words or keyphrases with multiple words. The keyword research process should be repeated regularly as products and markets evolve. A keyword strategy should ensure keywords fit the content on your site to avoid disappointing users. The document recommends various Yoast resources for further reading on keyword research best practices.
Yoast’s small seo guide to optimize your website small seo-guideMaría Alvaro
This document provides an overview of keyword research and strategy. It explains that keyword research is important to understand the language your audience uses when searching so you can optimize your site for relevant terms. Keywords can be single words or keyphrases with multiple words. The keyword research process should be repeated regularly as products and markets evolve. A good keyword strategy ensures the keywords fit your site so users find relevant information.
This document discusses how Agile has become outdated and ineffective in many organizations. It argues that while Agile and Scrum were created with good intentions, most companies have lost sight of the original purpose and focus too much on processes rather than outcomes. As a result, developers, customers, and stakeholders are often unhappy. The document suggests companies need to refocus on principles like individuals, interactions, and responding to change rather than rigidly following practices. It questions common Agile practices like overreliance on tools, certifications, and the belief that Scrum alone is enough. The goal of Agile should be happy customers and developers, not self-promotion or following trends. Companies need to experiment more and apply Agile principles rather
The document discusses gamification within Oracle's Fusion Applications. It notes there are 6 flows across Customer Relationship Management, Human Capital Management, and Financials products. It also discusses challenges around gaining support for gamification within organizations and ensuring gamification focuses on business goals rather than being seen as just games. Finally, it proposes guidelines and testing approaches like focus groups to help refine gamification design.
On traditional projects, testers usually join the project after coding has started, or even later when coding is almost finished. Testers have no role in advising the project team early regarding quality issues but focus only on finding defects. They become accustomed to this style of working and adjust their mental processes accordingly. In agile, testers must collaborate closely with customers and programmers throughout the development lifecycle, where their focus changes from finding defects to preventing them. Janet Gregory shares ways to change the tester’s mindset from “How can I break the software?” to “How can I help deliver excellent software?”—a critical mental shift on agile projects. Another facet of the mind-set change is learning how to test early and incrementally. Janet uses interactive exercises and examples to help you understand how effective this mindset change is—and how you can apply it on your agile projects.
The document discusses Agile methodology and diagrams. Agile is described as a way to visualize information about users. Key aspects of Agile include product backlogs, sprint planning, sprint reviews and retrospectives, and iterative development with demonstrations and feedback.
This document discusses strategies for avoiding release anxiety when developing iOS apps. It recommends establishing thorough testing practices like UI testing on real APIs to catch errors before release. It also stresses the importance of communication within development teams through code reviews, review guidelines, and style guides to standardize code quality. Maintaining a robust CI/CD pipeline with Danger and other tools can help catch issues early and reduce risks of pushing broken changes. Overall, the document promotes practices that improve code quality, catch errors earlier, and foster collaboration to minimize risks during app releases.
Designing for cloud user experiences is the new customer imperative. These experiences must be simple. They must respond to new work styles in a Bring-Your-Own-Device environment. They must adapt to different form factors, different layouts, and even different gestures. Learn how the Oracle Applications User Experience team conducted research that drove the design of Oracle’s new simplified user interface strategy. Talk to one of the lead design strategists, Aylin Uysal, who is actively shaping what Oracle will be tackling next in cloud user experiences.
The document discusses continuous deployment and integration. It describes why these practices are important for building robust applications with a solid architecture. Continuous deployment allows for very fast iteration and quick feedback cycles through continuous testing and automated deployment and rollback. The cloud is well-suited for continuous deployment with its standardized and automated features. It outlines how many startups and companies like Codeship and Github are implementing these practices and what the future may hold with more automation and usage of staging environments. It provides tips for getting started with continuous deployment and integration testing.
Isabel Evans stopped drawing and painting after being told she was not very good at it, which led to a loss of confidence in her creative and professional abilities. However, she realized that attempting creative activities is important for cognitive and emotional development, and that making mistakes and learning from failures allows for growth. By reengaging with failure through art and with support from others, Isabel was able to regain confidence in her abilities and reboot her career. The document discusses different perspectives on failure and the importance of learning from mistakes.
Instill a DevOps Testing Culture in Your Team and Organization TechWell
The DevOps movement is here. Companies across many industries are breaking down siloed IT departments and federating them into product development teams. Testing and its practices are at the heart of these changes. Traditionally, IT organizations have been staffed with mostly manual testers and a limited number of automation and performance engineers. To keep pace with development in the new “you build it, you own it” environment, testing teams and individuals must develop new technical skills and even embrace coding to stay relevant and add greater value to the business. DevOps really starts with testing. Join Adam Auerbach as he explains what DevOps is and how it relates to testing. He describes how testing must change from top to bottom and how to access your own environment to identify improvement opportunities. Adam dives into practices like service virtualization, test data management, and continuous testing so you can understand where you are now and identify steps needed to instill a DevOps testing culture in your team and organization.
Test Design for Fully Automated Build ArchitectureTechWell
This document summarizes a half-day tutorial on test design for fully automated build architectures presented by Melissa Benua of mParticle at STAREAST 2018. The tutorial covered guiding principles for test design including prioritizing important and reliable tests, structuring automated pipelines around components, packages, and releases, and monitoring test results through code coverage, flaky test handling, and logging versus counters. It also included exercises mapping test cases to functional boundaries and categories of tests to pipeline stages.
System-Level Test Automation: Ensuring a Good StartTechWell
Many organizations invest a lot of effort in test automation at the system level but then have serious problems later on. As a leader, how can you ensure that your new automation efforts will get off to a good start? What can you do to ensure that your automation work provides continuing value? This tutorial covers both “theory” and “practice”. Dot Graham explains the critical issues for getting a good start, and Chris Loder describes his experiences in getting good automation started at a number of companies. The tutorial covers the most important management issues you must address for test automation success, particularly when you are new to automation, and how to choose the best approaches for your organization—no matter which automation tools you use. Focusing on system level testing, Dot and Chris explain how automation affects staffing, who should be responsible for which automation tasks, how managers can best support automation efforts to promote success, what you can realistically expect in benefits and how to report them. They explain—for non-techies—the key technical issues that can make or break your automation effort. Come away with your own clarified automation objectives, and a draft test automation strategy to use to plan your own system-level test automation.
Build Your Mobile App Quality and Test StrategyTechWell
Let’s build a mobile app quality and testing strategy together. Whether you have a web, hybrid, or native app, building a quality and testing strategy means (1) knowing what data and tools you have available to make agile decisions, (2) understanding your customers and your competitors, and (3) testing your app under real-world conditions. Jason Arbon guides you through the latest techniques, data, and tools to ensure the awesomeness of your mobile app quality and testing strategy. Leave this interactive session with a strategy for your very own app—or one you pretend to own. The information Jason shares is based on data from Appdiff’s next-gen mobile app testing platform, lessons from Applause/uTest’s crowd, text mining hundreds of millions of app store reviews, and in-depth discussions with top mobile app development teams.
Testing Transformation: The Art and Science for SuccessTechWell
Technologies, testing processes, and the role of the tester have evolved significantly in the past few years with the advent of agile, DevOps, and other new technologies. It is critical that we testing professionals evaluate ourselves and continue to add tangible value to our organizations. In your work, are you focused on the trivial or on real game changers? Jennifer Bonine describes critical elements that help you artfully blend people, process, and technology to create a synergistic relationship that adds value. Jennifer shares ideas on mastering politics, maneuvering core vs. context, and innovating your technology strategies and processes. She explores how new processes can be introduced in an organization, what the role of organizational culture is in determining the success of a project, and how you can know what tools will add value vs. simply adding overhead and complexity. Jennifer reviews critically needed tester skills and discusses a continual learning model to evolve your skills and stay relevant. This discussion can lead you to technologies, processes, and skills you can stake your career on.
We’ve all been there. We work incredibly hard to develop a feature and design tests based on written requirements. We build a detailed test plan that aligns the tests with the software and the documented business needs. And when we put the tests to the software, it all falls apart because the requirements were changed without informing everyone. Mary Thorn says help is at hand. Enter behavior-driven development (BDD), and Cucumber and SpecFlow, tools for running automated acceptance tests and facilitating BDD. Mary explores the nuances of Cucumber and SpecFlow, and shows you how to implement BDD and agile acceptance testing. By fostering collaboration for implementing active requirements via a common language and format, Cucumber and SpecFlow bridge the communication gap between business stakeholders and implementation teams. In this workshop, practice writing feature files with the best practices Mary has discovered over numerous implementations. If you experience developers not coding to requirements, testers not getting requirements updates, or customers who feel out of the loop and don’t get what they ask for, Mary has answers for you.
Develop WebDriver Automated Tests—and Keep Your SanityTechWell
Many teams go crazy because of brittle, high-maintenance automated test suites. Jim Holmes helps you understand how to create a flexible, maintainable, high-value suite of functional tests using Selenium WebDriver. Learn the basics of what to test, what not to test, and how to avoid overlapping with other types of testing. Jim includes both philosophical concepts and hands-on coding. Testers who haven't written code should not be intimidated! We'll pair you up to make sure you're successful. Learn to create practical tests dealing with advanced situations such as input validation, AJAX delays, and working with file downloads. Additionally, discover when you need to work together with developers to create a system that's more easily testable. This tutorial focuses primarily on automating web tests, but many of the same concepts can be applied to other UI environments. Demos and labs will be in C# and Java using WebDriver. Leave this tutorial having learned how to write high-value WebDriver tests—and stay sane while doing so.
DevOps is a cultural shift aimed at streamlining intergroup communication and improving operational efficiency for development and operations groups. Over time, inclusion of other IT groups under the DevOps umbrella has become the norm for many organizations. But even broadening the boundaries of DevOps, the conversation has been largely devoid of the business units’ place at the table. A common mistake organizations make while going through the DevOps transformation is drawing a line at the IT boundary. If that occurs, a larger, more inclusive silo within the organization is created, operating in an informational vacuum and causing operational inefficiency and goal misalignment. Sharing his experiences working on both sides of the fence, Leon Fayer describes the importance of including business units in order to align technology decisions with business goals. Leon discusses inclusion of business units in existing agile processes, benefits of cross-departmental monitoring, and a business-first approach to technology decisions.
Eliminate Cloud Waste with a Holistic DevOps StrategyTechWell
Chris Parlette maintains that renting infrastructure on demand is the most disruptive trend in IT in decades. In 2016, enterprises spent $23B on public cloud IaaS services. By 2020, that figure is expected to reach $65B. The public cloud is now used like a utility, and like any utility, there is waste. Who's responsible for optimizing the infrastructure and reducing wasted expenses? It’s DevOps. The excess expense, known as cloud waste, comprises several interrelated problems: services running when they don't need to be, improperly sized infrastructure, orphaned resources, and shadow IT. There are a few core tenets of DevOps—holistic thinking, no silos, rapid useful feedback, and automation—that can be applied to reducing your cloud waste. Join Chris to learn why you should include continuous cost optimization in your DevOps processes. Automate cost control, reduce your cloud expenses, and make your life easier.
Transform Test Organizations for the New World of DevOpsTechWell
With the recent emergence of DevOps across the industry, testing organizations are being challenged to transform themselves significantly within a short period of time to stay meaningful within their organizations. It’s not easy to plan and approach these changes considering the way testing organizations have remained structured for ages. These challenges start from foundational organizational structures and can cut across leadership influence, competencies, tools strategy, infrastructure, and other dimensions. Sumit Kumar shares his experience assisting various organizations to overcome these challenges using an organized DevOps enablement framework. The framework includes radical restructuring, turning the tools strategy upside down, a multidimensional workforce enablement supported by infrastructure changes, redeveloped collaborations models, and more. From his real world experiences Sumit shares tips for approaching this journey and explains the roadmap for testing organizations to transform themselves to lead the quality in DevOps.
The Fourth Constraint in Project Delivery—LeadershipTechWell
All too often, the triple constraints—time, cost, and quality—are bandied about as if they are the be-all, end-all. While they are important, leadership—the fourth and larger underpinning constraint—influences the first three. Statistics on project success and failure abound, and these measurements are usually taken against the triple constraints. According to the Project Management Institute, only 53 percent of projects are completed within budget, and only 49 percent are completed on time. If so many projects overrun budget and are late, we can’t really say, “Good, fast, or cheap—pick two.” Rob Burkett talks about leadership at every level of a team. He shares his insights and stories gleaned from his years of IT and project management experience. Rob speaks to some of the glaring difficulties in the workplace in general and some specifically related to IT delivery and project management. Leave with a clearer understanding of how to communicate with teams and team members, and gain a better understanding of how you can be a leader—up and down your organization.
Resolve the Contradiction of Specialists within Agile TeamsTechWell
As teams grow, organizations often draw a distinction between feature teams, which deliver the visible business value to the user, and component teams, which manage shared work. Steve Berczuk says that this distinction can help organizations be more productive and scale effectively, but he recognizes that not all shared work fits into this model. Some work is best handled by “specialists,” that is people with unique skills. Although teams composed entirely of T-shaped people is ideal, certain skills are hard to come by and are used irregularly across an organization. Since these specialists often need to work closely with teams, rather than working from their own backlog, they don’t fit into the component team model. The use of shared resources presents challenges to the agile planning model. Steve Berczuk shares how teams such as those providing infrastructure services and specialists can fit into a feature+component team model, and how variations such as embedding specialists in a scrum team can both present process challenges and add significant value to both the team and the larger organization.
Pin the Tail on the Metric: A Field-Tested Agile GameTechWell
Metrics don’t have to be a necessary evil. If done right, metrics can help guide us to make better forward-looking decisions, rather than being used for simply managing or monitoring. They can help us identify trade-offs between options for what to do next versus punitive or worse, purely managerial measures. Steve Martin won’t be giving the Top Ten List of field-tested metrics you should use. Instead, in this interactive mini-workshop, he leads you through the critical thinking necessary for you to determine what is right for you to measure. First, Steve explores why you want to measure something—whether it’s for a team, a portfolio, or even an agile transformation. Next, he provides multiple real-life metrics examples to help drive home concepts behind characteristics of good and bad metrics. Finally, Steve shows how to run his field-tested agile game—Pin the Tail on the Metric. Take back this activity to help you guide metrics conversations at your organization.
Agile Performance Holarchy (APH)—A Model for Scaling Agile TeamsTechWell
A hierarchy is an organizational network that has a top and a bottom, and where position is determined by rank, importance, and value. A holarchy is a network that has no top or bottom and where each person’s value derives from his ability, rather than position. As more companies seek the benefits of agile, leaders need to build and sustain delivery capability while scaling agile without introducing unnecessary process and overhead. The Agile Performance Holarchy (APH) is an empirical model for scaling and sustaining agility while continuing to deliver great products. Jeff Dalton designed the APH by drawing from lessons learned observing and assessing hundreds of agile companies and teams. The APH helps implement a holarchy—a system composed of interacting organizational units called holons—centered on a series of performance circles that embody the behaviors of high performing agile organizations. Jeff describes how APH provides guidelines in the areas of leadership, values, teaming, visioning, governing, building, supporting, and engaging within an all-agile organization. Join Jeff to see what the APH is all about and how you can use it in your team and organization.
A Business-First Approach to DevOps ImplementationTechWell
DevOps is a cultural shift aimed at streamlining intergroup communication and improving operational efficiency for development and operations groups. Over time, inclusion of other IT groups under the DevOps umbrella has become the norm for many organizations. But even broadening the boundaries of DevOps, the conversation has been largely devoid of the business units’ place at the table. A common mistake organizations make while going through the DevOps transformation is drawing a line at the IT boundary. If that occurs, a larger, more inclusive silo within the organization is created, operating in an informational vacuum and causing operational inefficiency and goal misalignment. Sharing his experiences working on both sides of the fence, Leon Fayer describes the importance of including business units in order to align technology decisions with business goals. Leon discusses inclusion of business units in existing agile processes, benefits of cross-departmental monitoring, and a business-first approach to technology decisions.
Databases in a Continuous Integration/Delivery ProcessTechWell
The document summarizes a presentation about including databases in a continuous integration/delivery process. It discusses treating database code like application code by placing it under version control and integrating databases into the DevOps software development pipeline. This allows databases to be built, tested, and released like other software through continuous integration, delivery, and deployment.
Mobile Testing: What—and What Not—to AutomateTechWell
Organizations are moving rapidly into mobile technology, which has significantly increased the demand for testing of mobile applications. David Dangs says testers naturally are turning to automation to help ease the workload, increase potential test coverage, and improve testing efficiency. But should you try to automate all things mobile? Unfortunately, the answer is not always clear. Mobile has its own set of complications, compounded by a wide variety of devices and OS platforms. Join David to learn what mobile testing activities are ripe for automation—and those items best left to manual efforts. He describes the various considerations for automating each type of mobile application: mobile web, native app, and hybrid applications. David also covers device-level testing, types of testing, available automation tools, and recommendations for automation effectiveness. Finally, based on his years of mobile testing experience, David provides some tips and tricks to approach mobile automation. Leave with a clear plan for automating your mobile applications.
Cultural Intelligence: A Key Skill for SuccessTechWell
Diversity is becoming the norm in everyday life. However, introducing global delivery models without a proper understanding of intercultural differences can lead to difficulty, frustration, and reduced productivity. Priyanka Sharma and Thena Barry say that in our diverse world, we need teams with people who can cross these boundaries, communicate effectively, and build the diverse networks necessary to avoid problems. We need to learn about cultural intelligence (CI) and cultural quotient (CQ). CI is the ability to relate and work effectively across cultures. CQ is the cognitive, motivational, and behavioral capacity to understand and respond to beliefs, values, attitudes, and behaviors of individuals and groups. Together, CI and CQ can help us build behavioral capacities that aid motivation, behavior, and productivity in teams as well as individuals. Priyanka and Thena show how to build a more culturally intelligent place with tools and techniques from Leading with Cultural Intelligence, as well as content from the Hofstede cultural model. In addition, they illustrate the model with real-life experiences and demonstrate how they adapted in similar circumstances.
Turn the Lights On: A Power Utility Company's Agile TransformationTechWell
Why would a century-old utility with no direct competitors take on the challenge of transforming its entire IT application organization to an agile methodology? In an increasingly interconnected world, the expectations of customers continue to evolve. From smart meters to smart phones, IoT is creating a crisis point for industries not accustomed to rapid change. Glen Morris explains that pizzas can be tracked by the minute and packages at every stop, and customers now expect this same customer service model should exist for all industries—including power. Glen examines how to create momentum and transform non-IT-focused industries to an agile model. If you are struggling with gaining traction in your pursuit of agile within your business, Glen gives you concrete, practical experiences to leverage in your pursuit. Finally, he communicates how to gain buy-in from business partners who have no idea or concern about agile or its methodologies. If your business partners look at you with amusement when you mention the need for a dedicated Product Owner, join Glen as he walks you through the approaches to overcoming agile skepticism.
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.
[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...Jason Yip
The typical problem in product engineering is not bad strategy, so much as “no strategy”. This leads to confusion, lack of motivation, and incoherent action. The next time you look for a strategy and find an empty space, instead of waiting for it to be filled, I will show you how to fill it in yourself. If you’re wrong, it forces a correction. If you’re right, it helps create focus. I’ll share how I’ve approached this in the past, both what works and lessons for what didn’t work so well.
The Microsoft 365 Migration Tutorial For Beginner.pptxoperationspcvita
This presentation will help you understand the power of Microsoft 365. However, we have mentioned every productivity app included in Office 365. Additionally, we have suggested the migration situation related to Office 365 and how we can help you.
You can also read: https://www.systoolsgroup.com/updates/office-365-tenant-to-tenant-migration-step-by-step-complete-guide/
Main news related to the CCS TSI 2023 (2023/1695)Jakub Marek
An English 🇬🇧 translation of a presentation to the speech I gave about the main changes brought by CCS TSI 2023 at the biggest Czech conference on Communications and signalling systems on Railways, which was held in Clarion Hotel Olomouc from 7th to 9th November 2023 (konferenceszt.cz). Attended by around 500 participants and 200 on-line followers.
The original Czech 🇨🇿 version of the presentation can be found here: https://www.slideshare.net/slideshow/hlavni-novinky-souvisejici-s-ccs-tsi-2023-2023-1695/269688092 .
The videorecording (in Czech) from the presentation is available here: https://youtu.be/WzjJWm4IyPk?si=SImb06tuXGb30BEH .
Programming Foundation Models with DSPy - Meetup SlidesZilliz
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
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.
Discover top-tier mobile app development services, offering innovative solutions for iOS and Android. Enhance your business with custom, user-friendly mobile applications.
How information systems are built or acquired puts information, which is what they should be about, in a secondary place. Our language adapted accordingly, and we no longer talk about information systems but applications. Applications evolved in a way to break data into diverse fragments, tightly coupled with applications and expensive to integrate. The result is technical debt, which is re-paid by taking even bigger "loans", resulting in an ever-increasing technical debt. Software engineering and procurement practices work in sync with market forces to maintain this trend. This talk demonstrates how natural this situation is. The question is: can something be done to reverse the trend?
Introduction of Cybersecurity with OSS at Code Europe 2024Hiroshi SHIBATA
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
"Choosing proper type of scaling", Olena SyrotaFwdays
Imagine an IoT processing system that is already quite mature and production-ready and for which client coverage is growing and scaling and performance aspects are life and death questions. The system has Redis, MongoDB, and stream processing based on ksqldb. In this talk, firstly, we will analyze scaling approaches and then select the proper ones for our system.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
What is an RPA CoE? Session 1 – CoE VisionDianaGray10
In the first session, we will review the organization's vision and how this has an impact on the COE Structure.
Topics covered:
• The role of a steering committee
• How do the organization’s priorities determine CoE Structure?
Speaker:
Chris Bolin, Senior Intelligent Automation Architect Anika Systems
Conversational agents, or chatbots, are increasingly used to access all sorts of services using natural language. While open-domain chatbots - like ChatGPT - can converse on any topic, task-oriented chatbots - the focus of this paper - are designed for specific tasks, like booking a flight, obtaining customer support, or setting an appointment. Like any other software, task-oriented chatbots need to be properly tested, usually by defining and executing test scenarios (i.e., sequences of user-chatbot interactions). However, there is currently a lack of methods to quantify the completeness and strength of such test scenarios, which can lead to low-quality tests, and hence to buggy chatbots.
To fill this gap, we propose adapting mutation testing (MuT) for task-oriented chatbots. To this end, we introduce a set of mutation operators that emulate faults in chatbot designs, an architecture that enables MuT on chatbots built using heterogeneous technologies, and a practical realisation as an Eclipse plugin. Moreover, we evaluate the applicability, effectiveness and efficiency of our approach on open-source chatbots, with promising results.
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.
1.
AW4
Session
6/5/2013 10:15 AM
"Agile Testing: A Team Sport"
Presented by:
Jeffrey Morgan
LeanDog
Brought to you by:
340 Corporate Way, Suite 300, Orange Park, FL 32073
888‐268‐8770 ∙ 904‐278‐0524 ∙ sqeinfo@sqe.com ∙ www.sqe.com
2. Jeff "Cheezy" Morgan
LeanDog
Chief technology officer and a cofounder of LeanDog, Jeff “Cheezy” Morgan has been
coaching teams on agile and lean techniques since 2004 with a focus on the engineering
practices. For the past three years Cheezy has experienced great success and recognition for
his work focused on helping teams adopt Acceptance Test-driven Development using
Cucumber. He has authored several popular Ruby gems used by software testers throughout
the world, teaches Cucumber classes and workshops, and is the author of the book,Cucumber
& Cheese: A Testers Workshop.
3. Agile Testing
It’s A Team Sport
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
1
Life is good
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
2
4. A Little Help
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
3
Stereotypes
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
4
16. Ouch!!!
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
7
Ouch!!!
That really hurt, Cheezy.
Tell us what we can do!
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
7
17. Team Workflow
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
i
M
ne
to
l es
ne
ne
to
to
s
s
ile
ile
M
M
i
M
ne
to
les
i
M
8
ne
to
les
Team Workflow
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
8
20. Value Stream
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
9
Value Stream
Good
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
9
21. Value Stream
Good
Bad
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
9
Testing Software
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
10
22. Tester
Developer
Project Ping Pong
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
11
Manual Testing (not ET)
1
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
12
23. Manual Testing (not ET)
1.5
1
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
12
Manual Testing (not ET)
2.2
1.5
1
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
12
24. Manual Testing (not ET)
6.4
5.3
4.0
3.0
2.2
1.5
1
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
Code
12
Test
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
13
25. Code
Test
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
13
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
13
Developer
Code
Test
Tester
26. Test Drive Code With Pair
Developer
Code
Test
Tester
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
13
Test Drive Code With Pair
Developer
Code
Test
Tester
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
13
27. Test Drive Code With Pair
Automate Acceptance Tests
Developer
Code
Test
Tester
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
13
Test Drive Code With Pair
Developer
Code
Test
Automate Acceptance Tests
Tester
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
13
28. Test Drive Code With Pair
Make Acceptance Tests Pass
Developer
Code
Test
Automate Acceptance Tests
Tester
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
13
Test Drive Code With Pair
Make Acceptance Tests Pass
Developer
Code
Test
Automate Acceptance Tests
Tester
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
13
29. Test Drive Code With Pair
Make Acceptance Tests Pass
Developer
Exploratory Testing
Code
Test
Automate Acceptance Tests
Tester
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
13
Test Drive Code With Pair
Make Acceptance Tests Pass
Developer
Code
Test
Automate Acceptance Tests
Exploratory Testing
Tester
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
13
30. Test Drive Code With Pair
Make Acceptance Tests Pass
Developer
Talk
Code
Test
Automate Acceptance Tests
Exploratory Testing
Tester
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
13
Test Drive Code With Pair
Make Acceptance Tests Pass
Developer
Code
Test
Talk
Automate Acceptance Tests
Exploratory Testing
Tester
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
13
31. Test Drive Code With Pair
Make Acceptance Tests Pass
Developer
Talk
Prevent Defects
Code
Test
Automate Acceptance Tests
Exploratory Testing
Tester
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
13
Test Drive Code With Pair
Make Acceptance Tests Pass
Developer
Code
Test
Talk
Prevent Defects
Automate Acceptance Tests
Exploratory Testing
Tester
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
13
39. Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
Ready
Product
Owner
Development
Developer
Review
16
Done
Tester
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
17
47. Product
Owner
Elaborate Stories
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
18
Product
Owner
Elaborate Stories
Deliver the software
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
18
48. Product
Owner
Elaborate Stories
Deliver the software
Decide what not to build
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
18
Deliver the Software
^
F
T>
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
19
49. Deliver the Software
X
^
F
T>
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
19
Deliver the Software
X
^
F
T>
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
19
50. Deliver the Software
X
^
F
T>
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
19
Deliver the Software
X
^
F
T>
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
19
51. Deliver the Software
X
^
F
T>
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
19
Pull Value Forward
^
V
T>
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
20
52. Pull Value Forward
^
V
T>
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
20
Pull Value Forward
^
V
T>
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
20
53. Pull Value Forward
^
V
T>
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
20
Pull Value Forward
^
V
T>
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
20
54. Pull Value Forward
$$$$
^
V
T>
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
20
What to build?
P1
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
21
55. What to build?
P1
F2
F1
F3
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
21
What to build?
P1
F2
F1
F1.1
F1.2
F2.1
F3
F2.2
F3.1
F3.2
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
21
56. What to build?
P1
200
700
F1
F1.1
F1.2
F2
F2.1
100
F2.2
F3
F3.1
F3.2
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
21
What to build?
P1
200
700
F1
F2
100
F3
F1.1
F1.2
F2.1
F2.2
F3.1
F3.2
50
150
300
400
70
30
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
21
58. Elaboration
Product
Owner
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
22
Elaboration
Product
Owner
Cannot do it alone!
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
22
59. Elaboration
Product
Owner
Cannot do it alone!
Tester
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
22
Elaboration
Product
Owner
Cannot do it alone!
Rich Specification
Tester
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
22
60. Elaboration
Product
Owner
Cannot do it alone!
Rich Specification
Tester
Developer
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
22
Elaboration
Product
Owner
Cannot do it alone!
Rich Specification
Tester
Developer
What’s Possible
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
22
69. Creation
Elaboration
Validation
WIP
Product
Owner
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
Creation
Elaboration
Validation
24
WIP
Product
Owner
Tester
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
24
71. Creation
Elaboration
Validation
WIP
e
iv
s n
s
re tio
g a
ro or
P b
la
E
Product
Owner
Tester
Developer
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
24
Management
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
25
72. $$$
Maximize ROI
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
26
Project Priority
P1
Team
P2
P3
P4
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
27
73. Project Priority
Team
P4
P3
P2
P1
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
27
What to build?
P1
200
700
F1
F2
100
F3
F1.1
F1.2
F2.1
F2.2
F3.1
F3.2
50
150
300
400
70
30
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
28
74. Scheduling Projects
P1
P2
F1
F2
F3
F1
F2
F3
200
700
100
800
175
25
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
29
Scheduling Projects
P1
P2
F1
F2
F3
F1
F2
F3
200
700
100
800
175
25
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
29
76. What does done mean?
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
30
Done Done is Evil
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
31
77. Thank You
cheezy@leandog.com
@chzy
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
32
http://leanpub.com/cucumber_and_cheese
Copyright 2013 LeanDog, Inc. All Rights Reserved. Do not copy or distribute without permission.
33