Non-Pathological Software Metrics

•

0 likes•272 views

As semi-scientific software professionals, we like the idea of measuring our work. In some cases, our bosses like the idea much more than we do. Yet, meaningful software development metrics are notoriously challenging to define, and many people have given up trying because metrics often incentivize pathological behaviors. Since you get what you measure, most metrics lead development teams to optimize numeric proxies for success rather than the goals these proxies were intended to represent. Mindful of the pitfalls of quantifying knowledge work, Stephen Frein examines some typical software development metrics and why measuring them tends to be harmful. Then he recommends alternate metrics—such as “truck number”—that give software development teams a chance to engage in meaningful measurement with a lower risk of harmful side effects. If you want or need to measure your team’s success without ruining it, join Stephen for helpful advice.

Technology

BT4
Session
6/6/2013 10:15 AM

"Non-Pathological Software Metrics"

Presented by:
Stephen Frein
Comcast Cable

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

Stephen Frein
Comcast

Stephen Frein is a software development manager at Comcast, where his team creates tools
for process automation and quality assurance. As an adjunct professor at Drexel University, he
delivers soporific lectures on database development and IT management. Stephen has been
leading development teams for fifteen years, and occasionally does it well, mostly by dint of
accidents he cannot reliably replicate. He has presented at previous conferences by sneaking
into unused rooms and deceiving the unsuspecting. Stephen enjoys polluting the hive mind
via frein.com and writing vapid, self-deprecating bios.

Non Pathological
Non-Pathological
Software Metrics
Stephen Frein
Comcast
C
t
http://www.frein.com
stephen.frein@gmail.com

About Me

Context Matters
Metrics can do harm.

Be careful of what
B
f l f h
you incentivize.

Why Measure?

Clarity
Objectivity

Authority

You can't do that.
Quit it.
Stop it.
-- Joel Spolsky
We have no way of reasonably
W h
f
bl
measuring productivity.
-- Martin Fowler

You get what you measure.
Is that h t
I th t what you want?
t?

LOC
Lines of Code

More is Better!

public Cost calculateShipmentCost(Order someOrder) {
Cost shipCost = new Cost(0);
if (someOrder.getTotalCost() < 25) { shipCost.setCost(10); }
else { shipCost.setCost(5); }
return shipCost;
9 LOC
}
public Cost calculateTotalCost(Order someOrder) {
return someOrder.getTotalCost().add(
calculateShipmentCost(someOrder).getCost() );
}
public Cost calculateReturnRefund(Order someOrder) {
// only half of shipping costs get refunded
return someOrder.getTotalCost().add(
calculateShipmentCost(someOrder).getCost()/2) );
}

public Cost calculateTotalCost(Order someOrder) {
Cost shipCost = new Cost(0);
if (someOrder.getTotalCost() < 25) { shipCost.setCost(10); }
else { shipCost.setCost(5.00); }
return someOrder.getTotalCost().add(
shipCost.getCost()
shipCost getCost() );
}
public Cost calculateReturnRefund(Order someOrder) {
Cost shipCost = new Cost(0);
if (someOrder.getTotalCost() < 25) { shipCost.setCost(10); }
else { shipCost.setCost(5.00); }
p
(
)
// only half of shipping costs get refunded
return someOrder.getTotalCost().add(
shipCost.getCost()/2 );
}

10 LOC

Trade-offs
Maintainability

“Productivity”
Productivity

Change Incentives

Economics
Drive Behavior

Goodhart’s Law
Don’t make a measure

into a target.

Guess when …

<sarcasm>

This never would have happened if
we were using
</sarcasm>

story points.
i

Predicting the Future

“Ideal”

Metrics that focus on a proxy often
cause pathological
PROXY

behaviors.
GOAL

The proxy loses its connection
to the intended goal.

What to do?

Balance
Test Cases Per Hour

Defects Per Test Case

Stealth

Metrics I’ve Tried

Truck Number
How many
y
people can get
hit by a truck
before the
project is in big
trouble?

Customer Satisfaction
What do your
customers think
of your product?

Recommended:
o
o
o
o

Short
Sh rt
Simple
Anonymous
Comment box

Viewers also liked

Of course we know what customers want, right? Product owners have the roadmap. Sales teams know what sells. Support talks to customers every day. So if we really know what our customers want, why is 65 percent of all software functionality rarely or never used? Why aren’t our customers delighted with the products we ship? Stop guessing what customers want and start delivering it! Tom Gimpel discusses the challenges of feature prioritization and determining what your clients really want and what they really need—and why they’re not the same thing. Learn how you can employ the KANO prioritization model to delight your customers by giving them functionality they value without the fluff they won’t use. Learn what’s wrong with most feedback surveys and build your delivery process to maximize customer satisfaction. Take away valuable tools for prioritization including an Excel-based scoring model that actually chooses the “best” possible combination of features that you can ship.

Your Agile Prioritization Process Is Probably Wrong

TechWell

Every large software project is unique—each with its own complex array of challenges. When projects get into trouble, however, they often exhibit similar patterns, and succumb to risks that could have been anticipated and prevented—or detected sooner and managed better. Common responses to the problems—blaming, deferring action, or outright denial—only make things worse. Payson Hall reviews a dozen patterns he has observed over and over again on troubled projects during his thirty-year career: trouble with subcontractors, challenges with project sponsors, friction within the team, perils of interfacing with adjacent systems, issues with data cleansing and conversion, and more. Payson shares the tools he uses to help identify the symptoms of common risks, reduce the likelihood of risks occurring, facilitate early detection of problems, and establish a foundation for helpful responses when problems arise. This session is designed for project managers, team leaders, project sponsors, and anyone responsible for building or rolling out large enterprise systems.

Twelve Risks to Enterprise Software Projects—And What to Do about Them

TechWell

In both agile and traditional projects, keyword-driven testing has proven to be a powerful way to attain a high level of automation—when it is done correctly. Many testing organizations use keyword testing but aren’t realizing the full benefits of scalability and maintainability that are essential to keep up with the demands of testing today’s software. Hans Buwalda outlines how you can meet what he calls the 5 percent challenges—automating 95 percent of your tests with no more than 5 percent of your total testing effort—using the proven, keyword-driven test method he uses. Hans discusses how keywords relate to other automation techniques like scripting and data-driven testing. The information and real-world application Hans presents enables you to attain a very high level of automation with the lowest possible effort.

Introducing Keyword-driven Test Automation

TechWell

Innovation is a word tossed around frequently in organizations today. The standard cliché is “Do more with less.” People and teams want to be innovative but often struggle with how to define, prioritize, implement, and track their innovation efforts. Jennifer Bonine shares the "Innovation Types" model to give you new tools to evolve and expand your innovation capabilities. Find out if your innovation ideas and efforts match your team and company goals. Learn how to classify your innovation and improvement efforts as core (to the business) or context (essential but non-revenue generating). WIth this data, you can better decide how much of your effort should being spent on core versus context activities. Take away new tools for classifying innovation and mapping your activities and your team’s priorities to their importance and value. With Jennifer’s guidance you’ll evolve and expand your innovation capabilities on the spot.

Innovation Thinking: Evolve and Expand Your Capabilities

TechWell

Observation is an important research technique when we are designing solutions to delight users. Some kinds of information that may make the difference between an acceptable solution and a delightful one can only be obtained by observing users in their native environment. Observing users is much more than simply sitting and watching them work. We observe with a purpose in mind and use all our senses—not just sight—when doing an observation. Geri Winters describes several different observation techniques including observing the environment, silent observation of someone performing a task, cognitive walkthrough with a user, and observing while doing. After explaining when and why you might use each technique, she leads you through a series of exercises designed to practice the techniques. Geri uses stories from real projects to illustrate the importance of observation in the user’s native environment and provides references to resources for further study.

Observation: The Key to a Great User Experience

TechWell

Even today, to the detriment of agile success, most organizational cultures remain delivery date-driven—resulting in delivery teams that are not focused on creating value for the customer. So how can we redirect stakeholders, the business, and the project team to concentrate on delivering the greatest value rather than simply meeting dates? Pollyanna Pixton describes the tools she has used in collaboration sessions to help participants begin the process of adopting customer-centric agile methods. These tools include laying out an end-to-end customer journey, forming reusable decision filters to help prioritize backlogs, converting features into actionable user stories, and developing a solid process for making group decisions and communicating those decisions. Pollyanna shares questions that product owners and managers can use to define the problem while making sure they don't solve the problem. After all, that is the responsibility of the delivery team.

Leading the Creation of an Agile Culture

TechWell

Agile is now mainstream, but many companies continue to struggle. When agile is adopted, common issues occur in every organization: getting people to try agile, selling agile to management, learning how to do efficient standup meetings, fitting planning into a short window, and running effective retrospectives. When you add in scaling issues, different development styles, and outsourcing, your simple agile adoption just gets more difficult. In this highly interactive (no slides) introductory-to-intermediate session, Brian Button presents the tools you need to get started and be successful with agile. Using Scrum to manage the session, you will learn the value of prioritization and how to do it, why timeboxing works, how to create a release plan using team velocity, and more. As you are learning these techniques, Brian answers your questions to help ensure your successful agile adoption. Get started on the path to success with agile in this immersive experience.

Getting Started with Agile: An Experiential Workshop

TechWell

Remember the old days when software engineering teams used to tune software until it passed quality gates, gave golden bits to marketing, and finally threw a big release party? The world was simple, and writing code that worked according to a specification was enough to be a star developer. Viktor Veis says that world has changed. Software now often dials back home to record information about its usage and health. This telemetry flows back to engineering teams who are accountable for making sense out of this data. This is a fundamental shift in the software engineer role. Teams who can leverage data-driven engineering will delight customers by learning more about customers than they know about themselves. Teams who ignore data-driven engineering will continue based on assumptions and eventually lose competitive nerve. Join Viktor to learn how to start data-driven engineering today. Discover a practical approach that sometimes deviates from classical data science but is easy to learn and apply.

Data-Driven Software Engineering for Agile Teams

TechWell

As IT systems increase in both scale and complexity, delivering quality applications becomes more challenging. In addition to creating and executing test scenarios, testers need to create and maintain the test data that enables test execution. Test data management (TDM) creates and processes data in test environments using business knowledge and technology. Test data is created based on requirements provided from consumers. With TDM in your software delivery process, teams dependent on data can focus on creating and executing test scenarios instead of having to provision the data to run these tests. Shaheer Mohammed and Jatinder Singh present a case study that recaps the successful creation of a TDM team. They review what worked well, share lessons learned along the way, touch on the challenges of managing protected data in the health-care industry, and discuss innovative tools and processes that enabled their success.

Test Data Management: A Healthcare Industry Case Study

TechWell

Data warehouses have become a popular mechanism for collecting, organizing, and making information readily available for strategic decision making. The ability to review historical trends and monitor near real-time operational data has become a key competitive advantage for many organizations. Yet the methods for assuring the quality of these valuable assets are quite different from those of transactional systems. Ensuring that the appropriate testing is performed is a major challenge for many enterprises. Geoff Horne has led a number of data warehouse testing projects in both the telecommunications and ERP sectors. Join Geoff as he shares his approaches and experiences, focusing on the key “uniques” of data warehouse testing including methods for assuring data completeness, monitoring data transformations, and measuring quality. He also explores the opportunities for test automation as part of the data warehouse process, describing how it can be harnessed to streamline and minimize overhead.

Testing the Data Warehouse

TechWell

Viewers also liked (10)

Your Agile Prioritization Process Is Probably Wrong

Twelve Risks to Enterprise Software Projects—And What to Do about Them

Introducing Keyword-driven Test Automation

Innovation Thinking: Evolve and Expand Your Capabilities

Observation: The Key to a Great User Experience

Leading the Creation of an Agile Culture

Getting Started with Agile: An Experiential Workshop

Data-Driven Software Engineering for Agile Teams

Test Data Management: A Healthcare Industry Case Study

Testing the Data Warehouse

Similar to Non-Pathological Software Metrics

maxbox starter72 multilanguage coding

Max Kleiner

(ThoughtWorks Away Day 2009) one or two things you may not know about typesys...

Phil Calçado

As400 session or device error

aminem_mp

Supersize me

dominion

Desafios do Profissionalismo Ágil

Victor Hugo Germano

Loops

Kamran

ROOT Cause Analysis RCA Workshop maint.ppt

Madan Karki

Advanced Visual Studio 2005 Tools For Office Programming And Deployment

David Truxall

Spring 2014 CSCI 111 Final exam � of �1 6 1. (2 points) Flip over this test. On the back of this test write your name in the upper, left-hand corner. 2. (2 points) What are the four parts of the compiling process (just give me 4 words, not a paragraph). 3. (4 points) Which of the four steps of the compiling process occurs only once, regardless of the number of source files your application has? 4. (4 points) Write a line of code that causes the preprocessor to generate an error. 5. (4 points) Write a line of code that causes the compiler to generate an error. 6. (5 points) Describe how you could incorrectly compile the joust project to cause the linker to generate an error. 7. (5 points) Given: 1 float* fp; 2 //... 3 float pi; 4 pi=*(314 + fp); Rewrite line 4 using array subscript notation. Spring 2014 CSCI 111 Final exam � of �2 6 8. (5 points) Given: 1 float arr[100]; 2 for(int x=0; x<100; ++x) 3 arr[x]=100-x; What does the following expression print out? cout << *arr << endl; 9. (14 points) Given: int a=0; int b=6; int x=0; Circle each if-expression that evaluates to true: A) if(b) B) if(x) C) if(a=b==6) D) if(a=b==5) E) if(a=b=5) F) if(a=x=0) G) if(a=x==0) Spring 2014 CSCI 111 Final exam � of �3 6 10. (10 points) Given: 1 #include<iostream> 2 using namespace std; 3 4 int main() 5 { 6 int x; 7 cout << "Enter a number greater than 10" << endl; 8 while ( x < 10 ) 9 { 10 cin >> x; 11 } 12 return 0; 13 } This program compiles just fine, and sometimes it runs as expected. But sometimes when you run it, it exits immediately after printing "Enter a number greater than 10". That is, the program doesn't pause for you to enter a number. Why are you getting this inconsistent behavior? 11. (4 points) What is the output of the following: int x=4; int y=3; A) cout << x / y << endl; B) cout << x % y << endl; C) cout << x << "%" << y << endl; D) cout << "x" << '%' << 'y' << endl;  Spring 2014 CSCI 111 Final exam � of �4 6 12. (16 points) What is the type of the expression. That is, what is the kind of thing that each expression evaluates to. For example: 3 + 4 integer You may assume that the variable a has been declared as an integer. A. a + 4 B. a = 4 C. 3.14 + 4.49 D. 3 + 3.14 E. 'a' F. cout << a G. new float[30] H. new float Spring 2014 CSCI 111 Final exam � of �5 6 13. (5 points) Write a for-loop that prints out the numbers between 1 and 100 that are evenly divisible by three. 14. (5 points) Write a while-loop that prints out the numbers between 1 and 100 that are evenly divisible by three. 15. (5 points) Write a do-while-loop that prints out the numbers between 1 and 100 that are evenly divisible by three. Spring 2014 CSCI 111 Final exam � of �6 6 16. (10 points) Given: 1 #include<iostream> 2 3 class Willow { 4 publi.

Spring 2014 CSCI 111 Final exam of 1 61. (2 points) Fl.docx

rafbolet0

C Sharp Jn (3)

jahanullah

Term 2 CS Practical File 2021-22.pdf

KiranKumari204016

One of the essential parts of every reasonably complex application is a state. Managing it and making it more predictable is one of the most important aspects to consider during application or solution development. One way to give more structure to the solution and outline key states an application can be in is to model it using finite-state machines (FSM). In this talk, we'll look at FSMs and how they can be used for good in a real-world desktop application. We'll discuss whether they can help maintain a clear understanding of states and their transitions, look at different implementations in .NET, and point out the drawbacks of using them. We’ll also examine how the overall approach can be improved. And to spice everything up a little bit, we'll explore how FSMs can be implemented in a functional programming world by peeking at F# examples and comparing declarative and imperative approaches.

"Final fsFighting Complex Application State Management with Finite-State Mach...

Fwdays

Borland star team to tfs simple migration

Shreesha Rao

What is Tropo, how do you use it, and what can you use it for? In this session, you'll learn how Tropo works, see some real-life examples, and learn how to create your own voice and SMS applications in minutes. Watch the DevNet 1023 replay from the Cisco Live On-Demand Library at:https://www.ciscolive.com/online/connect/sessionDetail.ww?SESSION_ID=91050&backBtn=true Check out more and register for Cisco DevNet: http://ow.ly/jCNV3030OfS

Getting Started: Developing Tropo Applications

Cisco DevNet

C multiple choice questions and answers pdf

choconyeuquy

Event Driven Programming Made Easy For Network Packet Analysis

Jin Qian

Computer Networks Lab File

Kandarp Tiwari

Virus lab

kunalashutosh92

The Ring programming language version 1.5.1 book - Part 175 of 180

Mahmoud Samir Fayed

Sqlforetltesting 130712042826-phpapp01

Gyanendra Kumar

Similar to Non-Pathological Software Metrics (20)

maxbox starter72 multilanguage coding

(ThoughtWorks Away Day 2009) one or two things you may not know about typesys...

As400 session or device error

Supersize me

Desafios do Profissionalismo Ágil

Loops

ROOT Cause Analysis RCA Workshop maint.ppt

Advanced Visual Studio 2005 Tools For Office Programming And Deployment

Spring 2014 CSCI 111 Final exam of 1 61. (2 points) Fl.docx

C Sharp Jn (3)

Term 2 CS Practical File 2021-22.pdf

"Final fsFighting Complex Application State Management with Finite-State Mach...

Borland star team to tfs simple migration

Getting Started: Developing Tropo Applications

C multiple choice questions and answers pdf

Event Driven Programming Made Easy For Network Packet Analysis

Computer Networks Lab File

Virus lab

The Ring programming language version 1.5.1 book - Part 175 of 180

Sqlforetltesting 130712042826-phpapp01

More from TechWell

Do you ever feel you have lost confidence in your own abilities? Why does this happen? Isabel Evans spends a lot of time painting. Someone once commented, “Why are you doing this, when you are not very good at it?” And gradually she stopped drawing and painting, after being intimidated by a conventional vision of what good art should look like. At the same time, she experienced a parallel loss of confidence in her professional abilities. Attempting creative pursuits like drawing and painting is essential to cognitive, emotional, creative abilities and she began to understand the correlation between her creative activities and her confidence. Making errors, being wrong, failing – that is a generous gift we receive when we practice outside our skill level. By staying in a comfort zone and repeating successes, we stagnate. As Isabel started to create again she thought “I don’t feel good at it, I do feel good doing it” The difference was that she was learning, having ideas and the act of re-engaging with failure, together with the comradeship of friends and colleagues, including at Women Who Test, Isabel has regained her confidence in her professional abilities, and been able to reboot her career and joy. Join Isabel to share a journey from self-perceived failure, to recovery and renewed learning.

Failing and Recovering

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.

Instill a DevOps Testing Culture in Your Team and Organization

TechWell

Imagine this … As soon as any developed functionality is submitted into the code repository, it is automatically subjected to the appropriate battery of tests and then released straight into production. Setting up the pipeline capable of doing just that is becoming more and more common and something you need to know about. But most organizations hit the same stumbling block—just what IS the appropriate battery of tests? Automated build architectures don't always lend themselves well to the traditional stages of testing. In this hands-on tutorial, Melissa Benua introduces you to key test design principles—applicable to organizations both large and small—that allow you to take full advantage of the pipeline's capabilities without introducing unnecessary bottlenecks. Learn how to make highly reliable tests that run fast and preserve just enough information to let testers and developers determine exactly what went wrong and how to reproduce the error locally. Explore ways to reduce overlap while still maintaining adequate test coverage. Take back ideas about which test areas could benefit from being combined into a single suite and which areas could benefit most from being broken out altogether.

Test Design for Fully Automated Build Architecture

TechWell

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.

System-Level Test Automation: Ensuring a Good Start

TechWell

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.

Build Your Mobile App Quality and Test Strategy

TechWell

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.

Testing Transformation: The Art and Science for Success

TechWell

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.

Implement BDD with Cucumber and SpecFlow

TechWell

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.

Develop WebDriver Automated Tests—and Keep Your Sanity

TechWell

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.

Ma 15

TechWell

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.

Eliminate Cloud Waste with a Holistic DevOps Strategy

TechWell

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.

Transform Test Organizations for the New World of DevOps

TechWell

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.

The Fourth Constraint in Project Delivery—Leadership

TechWell

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.

Resolve the Contradiction of Specialists within Agile Teams

TechWell

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.

Pin the Tail on the Metric: A Field-Tested Agile Game

TechWell

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.

Agile Performance Holarchy (APH)—A Model for Scaling Agile Teams

TechWell

A Business-First Approach to DevOps Implementation

TechWell

DevOps is transforming software development with many organizations adopting lean development practices, implementing continuous integration (CI), and performing regular continuous deployment (CD) to their production environments. However, the database is largely ignored and often seen as a bottleneck in the DevOps process. Steve Jones discusses the challenges of database development and why many developers find the database to be an impediment to the CD process. Steve shares the techniques you can use to fit a database into the DevOps process. Learn how to store database code in a version control system, and the differences between that and application code. Steve demonstrates a CI process with SQL code and uses automated testing frameworks to check the code. Steve then shows how automated releases with manual gates can reduce the stress and risk of database deployments while ensuring consistent, reliable, repeatable releases to QA, UAT, and production.

Databases in a Continuous Integration/Delivery Process

TechWell

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.

Mobile Testing: What—and What Not—to Automate

TechWell

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.

Cultural Intelligence: A Key Skill for Success

TechWell

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.

Turn the Lights On: A Power Utility Company's Agile Transformation

TechWell

More from TechWell (20)

Failing and Recovering

Instill a DevOps Testing Culture in Your Team and Organization

Test Design for Fully Automated Build Architecture

System-Level Test Automation: Ensuring a Good Start

Build Your Mobile App Quality and Test Strategy

Testing Transformation: The Art and Science for Success

Implement BDD with Cucumber and SpecFlow

Develop WebDriver Automated Tests—and Keep Your Sanity

Ma 15

Eliminate Cloud Waste with a Holistic DevOps Strategy

Transform Test Organizations for the New World of DevOps

The Fourth Constraint in Project Delivery—Leadership

Resolve the Contradiction of Specialists within Agile Teams

Pin the Tail on the Metric: A Field-Tested Agile Game

Agile Performance Holarchy (APH)—A Model for Scaling Agile Teams

A Business-First Approach to DevOps Implementation

Databases in a Continuous Integration/Delivery Process

Mobile Testing: What—and What Not—to Automate

Cultural Intelligence: A Key Skill for Success

Turn the Lights On: A Power Utility Company's Agile Transformation

Recently uploaded

DBX First Quarter 2024 Investor Presentation

Dropbox

The action of the next cyber saga takes place in the mystical lands of the Asia-Pacific region, where the main characters began their digital activities in the middle of 2021 and qualitatively strengthened it in 2022. Corporate espionage, document theft, audio recordings, and data leaks from messaging platforms were all a matter of one day for Dark Pink. Their geographical focus may have started in the Asia-Pacific region, but their ambitions knew no bounds, targeting a European government ministry in a bold move to expand their portfolio. Their victim profile was as diverse as a UN meeting, targeting military organizations, government agencies, and even a religious organization. Because discrimination is not a fashionable agenda. In the world of cybercrime, they serve as a reminder that sometimes the most serious threats come in the most unassuming packages with a pink bow.

Cyberprint. Dark Pink Apt Group [EN].pdf

Overkill Security

2024: Domino Containers - The Next Step. News from the Domino Container commu...

Martijn de Jong

Three things you will take away from the session: • How to run an effective tenant-to-tenant migration • Best practices for before, during, and after migration • Tips for using migration as a springboard to prepare for Copilot in Microsoft 365 Main ideas: Migration Overview: The presentation covers the current reality of cross-tenant migrations, the triggers, phases, best practices, and benefits of a successful tenant migration Considerations: When considering a migration, it is important to consider the migration scope, performance, customization, flexibility, user-friendly interface, automation, monitoring, support, training, scalability, data integrity, data security, cost, and licensing structure Next Wave: The next wave of change includes the launch of Copilot, which requires businesses to be prepared for upcoming changes related to Copilot and the cloud, and to consolidate data and tighten governance ShareGate: ShareGate can help with pre-migration analysis, configurable migration tool, and automated, end-user driven collaborative governance

Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff

sammart93

Following the popularity of "Cloud Revolution: Exploring the New Wave of Serverless Spatial Data," we're thrilled to announce this much-anticipated encore webinar. In this sequel, we'll dive deeper into the Cloud-Native realm by uncovering practical applications and FME support for these new formats, including COGs, COPC, FlatGeoBuf, GeoParquet, STAC, and ZARR. Building on the foundation laid by industry leaders Michelle Roby of Radiant Earth and Chris Holmes of Planet in the first webinar, this second part offers an in-depth look at the real-world application and behind-the-scenes dynamics of these cutting-edge formats. We will spotlight specific use-cases and workflows, showcasing their efficiency and relevance in practical scenarios. Discover the vast possibilities each format holds, highlighted through detailed discussions and demonstrations. Our expert speakers will dissect the key aspects and provide critical takeaways for effective use, ensuring attendees leave with a thorough understanding of how to apply these formats in their own projects. Elevate your understanding of how FME supports these cutting-edge technologies, enhancing your ability to manage, share, and analyze spatial data. Whether you're building on knowledge from our initial session or are new to the serverless spatial data landscape, this webinar is your gateway to mastering cloud-native formats in your workflows.

Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME

Safe Software

FWD Group - Insurer Innovation Award 2024

The Digital Insurer

Axa Assurance Maroc - Insurer Innovation Award 2024

The Digital Insurer

MS Copilot expands with MS Graph connectors

Nanddeep Nachan

Artificial Intelligence Chap.5 : Uncertainty

Khushali Kathiriya

How to Troubleshoot Apps for the Modern Connected Worker

ThousandEyes

ProductAnonymous-April2024-WinProductDiscovery-MelissaKlemke

Product Anonymous

Boost Fertility New Invention Ups Success Rates.pdf

sudhanshuwaghmare1

presentation ICT roal in 21st century education

jfdjdjcjdnsjd

Following the popularity of “Cloud Revolution: Exploring the New Wave of Serverless Spatial Data,” we’re thrilled to announce this much-anticipated encore webinar. In this sequel, we’ll dive deeper into the Cloud-Native realm by uncovering practical applications and FME support for these new formats, including COGs, COPC, FlatGeoBuf, GeoParquet, STAC, and ZARR. Building on the foundation laid by industry leaders Michelle Roby of Radiant Earth and Chris Holmes of Planet in the first webinar, this second part offers an in-depth look at the real-world application and behind-the-scenes dynamics of these cutting-edge formats. We will spotlight specific use-cases and workflows, showcasing their efficiency and relevance in practical scenarios. Discover the vast possibilities each format holds, highlighted through detailed discussions and demonstrations. Our expert speakers will dissect the key aspects and provide critical takeaways for effective use, ensuring attendees leave with a thorough understanding of how to apply these formats in their own projects. Elevate your understanding of how FME supports these cutting-edge technologies, enhancing your ability to manage, share, and analyze spatial data. Whether you’re building on knowledge from our initial session or are new to the serverless spatial data landscape, this webinar is your gateway to mastering cloud-native formats in your workflows.

Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME

Safe Software

Webinar Recording: https://www.panagenda.com/webinars/why-teams-call-analytics-is-critical-to-your-entire-business Nothing is as frustrating and noticeable as being in an important call and being unable to see or hear the other person. Not surprising then, that issues with Teams calls are among the most common problems users call their helpdesk for. Having in depth insight into everything relevant going on at the user’s device, local network, ISP and Microsoft itself during the call is crucial for good Microsoft Teams Call quality support. To ensure a quick and adequate solution and to ensure your users get the most out of their Microsoft 365. But did you know that ‘bad calls’ are also an excellent indicator of other problems arising? Precisely because it is so noticeable!? Like the canary in the mine, bad calls can be early indicators of problems. Problems that might otherwise not have been noticed for a while but can have a big impact on productivity and satisfaction. Join this session by Christoph Adler to learn how true Microsoft Teams call quality analytics helped other organizations troubleshoot bad calls and identify and fix problems that impacted Teams calls or the use of Microsoft365 in general. See what it can do to keep your users happy and productive! In this session we will cover - Why CQD data alone is not enough to troubleshoot call problems - The importance of attributing call problems to the right call participant - What call quality analytics can do to help you quickly find, fix-, and prevent problems - Why having retrospective detailed insights matters - Real life examples of how others have used Microsoft Teams call quality monitoring to problem shoot problems with their ISP, network, device health and more.

Why Teams call analytics are critical to your entire business

panagenda

Passkeys: Developing APIs to enable passwordless authentication Cody Salas, Sr Developer Advocate | Solutions Architect - Yubico Apidays New York 2024: The API Economy in the AI Era (April 30 & May 1, 2024) ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/

Apidays New York 2024 - Passkeys: Developing APIs to enable passwordless auth...

apidays

Emergent Methods: Multi-lingual narrative tracking in the news - real-time ex...

Zilliz

The Good, the Bad and the Governed - Why is governance a dirty word? David O'Neill, Chief Operating Officer - APIContext Apidays New York 2024: The API Economy in the AI Era (April 30 & May 1, 2024) ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/

Apidays New York 2024 - The Good, the Bad and the Governed by David O'Neill, ...

apidays

Angeliki Cooney has spent over twenty years at the forefront of the life sciences industry, working out of Wynantskill, NY. She is highly regarded for her dedication to advancing the development and accessibility of innovative treatments for chronic diseases, rare disorders, and cancer. Her professional journey has centered on strategic consulting for biopharmaceutical companies, facilitating digital transformation, enhancing omnichannel engagement, and refining strategic commercial practices. Angeliki's innovative contributions include pioneering several software-as-a-service (SaaS) products for the life sciences sector, earning her three patents. As the Senior Vice President of Life Sciences at Avenga, Angeliki orchestrated the firm's strategic entry into the U.S. market. Avenga, a renowned digital engineering and consulting firm, partners with significant entities in the pharmaceutical and biotechnology fields. Her leadership was instrumental in expanding Avenga's client base and establishing its presence in the competitive U.S. market.

Biography Of Angeliki Cooney | Senior Vice President Life Sciences | Albany, ...

Angeliki Cooney

Repurposing LNG terminals for Hydrogen Ammonia: Feasibility and Cost Saving

Edi Saputra

Recently uploaded (20)

DBX First Quarter 2024 Investor Presentation

Cyberprint. Dark Pink Apt Group [EN].pdf

2024: Domino Containers - The Next Step. News from the Domino Container commu...

Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff

Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME

FWD Group - Insurer Innovation Award 2024

Axa Assurance Maroc - Insurer Innovation Award 2024

MS Copilot expands with MS Graph connectors

Artificial Intelligence Chap.5 : Uncertainty

How to Troubleshoot Apps for the Modern Connected Worker

ProductAnonymous-April2024-WinProductDiscovery-MelissaKlemke

Boost Fertility New Invention Ups Success Rates.pdf

presentation ICT roal in 21st century education

Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME

Why Teams call analytics are critical to your entire business

Apidays New York 2024 - Passkeys: Developing APIs to enable passwordless auth...

Emergent Methods: Multi-lingual narrative tracking in the news - real-time ex...

Apidays New York 2024 - The Good, the Bad and the Governed by David O'Neill, ...

Biography Of Angeliki Cooney | Senior Vice President Life Sciences | Albany, ...

Repurposing LNG terminals for Hydrogen Ammonia: Feasibility and Cost Saving

Non-Pathological Software Metrics

1. BT4 Session 6/6/2013 10:15 AM "Non-Pathological Software Metrics" Presented by: Stephen Frein Comcast Cable 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. Stephen Frein Comcast Stephen Frein is a software development manager at Comcast, where his team creates tools for process automation and quality assurance. As an adjunct professor at Drexel University, he delivers soporific lectures on database development and IT management. Stephen has been leading development teams for fifteen years, and occasionally does it well, mostly by dint of accidents he cannot reliably replicate. He has presented at previous conferences by sneaking into unused rooms and deceiving the unsuspecting. Stephen enjoys polluting the hive mind via frein.com and writing vapid, self-deprecating bios.

3. Non Pathological Non-Pathological Software Metrics Stephen Frein Comcast C t http://www.frein.com stephen.frein@gmail.com About Me

4. Context Matters Metrics can do harm. Be careful of what B f l f h you incentivize.

5. Why Measure? Clarity Objectivity Authority

6. What to Measure? Productivity!

7. You can't do that. Quit it. Stop it. -- Joel Spolsky We have no way of reasonably W h f bl measuring productivity. -- Martin Fowler You get what you measure. Is that h t I th t what you want? t?

8. LOC Lines of Code More is Better! public Cost calculateShipmentCost(Order someOrder) { Cost shipCost = new Cost(0); if (someOrder.getTotalCost() < 25) { shipCost.setCost(10); } else { shipCost.setCost(5); } return shipCost; 9 LOC } public Cost calculateTotalCost(Order someOrder) { return someOrder.getTotalCost().add( calculateShipmentCost(someOrder).getCost() ); } public Cost calculateReturnRefund(Order someOrder) { // only half of shipping costs get refunded return someOrder.getTotalCost().add( calculateShipmentCost(someOrder).getCost()/2) ); }

9. public Cost calculateTotalCost(Order someOrder) { Cost shipCost = new Cost(0); if (someOrder.getTotalCost() < 25) { shipCost.setCost(10); } else { shipCost.setCost(5.00); } return someOrder.getTotalCost().add( shipCost.getCost() shipCost getCost() ); } public Cost calculateReturnRefund(Order someOrder) { Cost shipCost = new Cost(0); if (someOrder.getTotalCost() < 25) { shipCost.setCost(10); } else { shipCost.setCost(5.00); } p ( ) // only half of shipping costs get refunded return someOrder.getTotalCost().add( shipCost.getCost()/2 ); } 10 LOC Trade-offs Maintainability “Productivity” Productivity

10. Change Incentives Economics Drive Behavior

11. Goodhart’s Law Don’t make a measure into a target. Guess when …

12. <sarcasm> This never would have happened if we were using </sarcasm> story points. i Predicting the Future “Ideal”

13. Metrics that focus on a proxy often cause pathological PROXY behaviors. GOAL The proxy loses its connection to the intended goal. What to do?

14. Balance Test Cases Per Hour Defects Per Test Case Stealth

15. Voyeurism Independence

16. Metrics I’ve Tried Truck Number How many y people can get hit by a truck before the project is in big trouble?

17.

18. Customer Satisfaction What do your customers think of your product? Recommended: o o o o Short Sh rt Simple Anonymous Comment box

19. Learning

20. Find the Incentives

21. Questions?