Dr. Sue Black starts off the morning by describing what her life was like before she made a sojourn into developing a technology career. Her life was not one of stable means, she had three small children, a broken marriage, and being a single parent at age twenty-five, with a question of “how am I going to support my children on my own?” From here, she did a degree in computing and started a PhD with three small children (I can’t imagine how she did this, to be honest, but she did :) ). It took her seven years to complete it, but she did, and she focused on reverse engineering and doing research on systems measurement and “ripple effects”.
One of the biggest challenges for Sue when it came to going to conferences was the focus on talking to other people. She really struggled with trying to talk with people, especially since she was one of the few women attending these conferences. this changed when she attended the Women in Technology Conference in Brussels, and she discovered the advent of online networks. She decided she wanted to create a group for Women in Computing, where they could meet online and discuss things.
Sue was also instrumental in an initiative to save Bletchley Park (the scene for Alan Turing and the many code breakers that worked on breaking the Enigma code. For those who have seen “The Imitation Game”, this is where that all happened). Additionally, it was a neat discovery to Sue to realize that most of the participants in the Bletchley Park initiative were women. Sue and her group worked on a oral history project to capture the memories of many of these women that worked on the code breaking project.
Through a social media campaign, she was able to generate and develop interest in Bletchley Park and generate a true grassroots movement to help get people involved, including many prominent people who helped the cause. As it was Twitter that I learned about Bletchley Park and what it meant, I probably have Dr. Black to thank for the fact I received awareness about it :).
Beyomnd Bletchley Park, Dr. Black has also been actively engaged in an effort called "Techmums", which is the idea that children, especially girls, will be more likely to be encouraged to approach technology if their mothers specifically had tech skills and a comfort with technology. Techmums is an outgrowth of that idea, and she is changing lives one family at a time, and I'm hopeful to see how the demographics for these children will change because of this initiative.
What I am taking from this is the fact that many of the great opportunities in our lives come about because of genuine interest, a passion for seeing something happen, and being willing and able to drive that passion. If you have a passion for a topic or cause, it's a good bet you will be able to find others who share in that passion. Opportunities often arise because someone has a genuine drive and desire to see something happen. I have myself sen this in my own reality, and I've been grateful for the opportunities that have come my way because I've shared my own passions and determination to see something happen around my goals and desires. So yes, I do agree, if we can do it, you can too (my "I can do it" is a bit more modest than Dr. Black's, but the main message is still relevant). Put your passion out there, and don't be surprised if you find many people willing to help you develop and keep momentum going.
Wednesday, November 11, 2015
Early Morning Enlightenment - Live from #AgileTD
It's another full day ahead for us, including me talking in a couple of hours in the "big room". I'm both excited and anxious, but I'm grateful that I m covering a topic I've been actively engaged in for quite some time, and that I am covering a topic that Albert Gareev and I have been actively working on the better part of a year.
It's been a year of learning and experimenting, and I am hoping the details I am providing about Inclusive Design will prove to be interesting and possibly game changing for some. For obvious reasons, I will not be live blogging my own session today, but I hope to have a recap about the experience a bit later in the day.
After a fun Wild West themed party last night, some die hards are in bright and early to do Lean Coffee once again. It does often astound me how many people show up for these early morning events, especially after a late nights revelry. Work hard, play hard, I guess ;).
The range of topics as always is wide and varied, and based on the top votes, we started out with the topic of "Relevant Test Metrics in Agile". It's frequently a push and pull in the Agile space that we don't over emphasize metrics, but the fact is, measurement happens in organizations. We need some way to determine if we are succeeding or failing, or how long it is taking us to get stories created, tested and out in the wild. One challenge that we have when it comes to working with areas such as TDD, ATDD, BDD, etc., is that the number of bugs is often nebulous. In my own experience, since I work in a Kanban shop, bugs found in the process of development are reworked inside the story. We find a number of things, we fix a lot of things, but the number of "bugs" in most of these cases is zero, because the work is done as the "product" moves down the line. In our world view, bugs are what happen after that feature "ships", whether they be found on our staging server or in production. We definitely keep track of and focus on those, since they are genuine bugs and issues that made their way through testing. For us, this is relevant because it gives us insights on areas that we can provide greater focus during testing. Other organizations look at things like the financial cost to the business for delays or for issues that make it out in the wild. I find that intriguing and wonder how that would work, but it certainly "bottom lines" the approach.
"No UI Tests" looks at the dichotomy of the value of automated UI tests (or supposed lack thereof) and the fact that a lot of tests do have to happen within the UI. Part of the challenge is the fact that, traditionally, UI tests and running them from the front end are more brittle than similar unit tests that look at atomic functions and procedures. Still, the UI is the interface that most users will be using, so those tests still have a value and are important to run. Getting a balance between writing tests that focus on unit testing, integration testing and a few key tests that are built around the UI is important. Having a Page Model approach helps a bit, and there is a definite value to making sure that surface level changes don't introduce problems in the testing and create an undue burden on the test maintainers. Tests that need to be frequently reworked are going to be problematic. Some rework is, of course to be expected.
"Building and Sustaining Internal Communities in Organizations" is another topic that received a lot of votes, and this is going to depend considerably on the size and culture of a company. In my case, the community is relatively small. At present, we have three software testers and nine programmers, so we are pretty solidly integrated. Larger companies I would imagine have a harder time with integrating and talking with one another. One way to encourage this level of discussion was to cover a particular topic, or to do some kind of tester games, and make a way to make it applicable to the broader group. By doing that, they were able to get more of the testers together to share ideas and develop comraderie within the various teams.
"What do you do Against Agile KPI's"... put simply, Key Performance Indicators are going to vary dramatically from company to company. Each organization is going to determine which aspects matter to them, and many organizations look to fish out "metrics" to answer this. Positive, they are values that are objectively measured. negative, metrics are almost never objective. They are filtered through the audience and the people that are interpreting them. A question to ask is "What caused the organization to look to Agile as an approach in the first place? Generally, the goal is to be more efficient and more responsive, to create better software out the gate, but ultimately, the goal for most organizations is to do well, and to keep themselves viable. That means that the Excel needs to line up at the end of this, so it's key that any and all performance indicators ultimately support the organization, and there's really no way to totally escape that.
All right, that's a good start, heading into the main room and getting ready to get day two underway, including my own talk. See you all soon :).
Tuesday, November 10, 2015
Human Refactoring for Agilists - Live at #AgileTD
If you have spent any time whatsoever with an Agile project, you should be well acquainted with the idea of Refactoring. The simple explanation of Refactoring is to clean up any duplication and remove any waste so that the end result is as sturdy and error free as possible.
That's all well and good, but what in the world is "Human Refactoring"? It's the concept that, the methods we use to clean up and strengthen our code, can also be applied to ourselves. Our diet, exercise and sleep habits can be refactored (and considering the last almost 90 days I've had, boy do I understand this :) ).
We can refactor our brains by encouraging our brains to do new things. Activities that excite or calm the brain can be mutually beneficial. Sleep is a big component to helping us achieve our health objectives. Too little sleep prevents optimal healing (read: refactoring) of our bodies. The food that we eat, the substances we drink, and the air we breathe can be both beneficial and detrimental. Ultimately, it is up to us as to what we consume and in which quantities. To not beat on this too hard, I've come to really appreciate the solid benefits of dropping soda in favor of water, dropping packaged foods in favor of fresh foods, and looking to boost my intake of unique fruit and vegetables each given day. Additionally, I've moved to considering meat as a flavoring, rather than as a primary item at the center of my meals. The net result is a 45 pound drop in 90 days, with a goal to lose another 30 in the next 90 days.
Exercise can be very basic, and it doesn't take a lot to make small changes, but if you want or need to make radical changes, then you will need to put in a significant amount of time in addition to reducing calories to reach your goals. It may well be unpleasant, but it is bearable, and if you take time to get to your goals, and make small changes each day, then reaching that optimal burn rate will be possible. It will take time regardless, and dramatic changes will require dramatic effort, at least at first. I've found ten thousand steps a day to be effective, and I've also added a goal to eat 225 calories of fresh fruit every day, with 200 calories coming from fresh vegetables every day. The fruit calories are pretty easy to meet. The vegetable calories are a bit harder, but still doable with planning and paying attention.
Think about the environment you live and work in. Think of your desk. Think of your chair. think of your mental environment and your co-workers and their attitudes. Can they affect you? Answer is, certainly.
Something to consider it the idea of 'The Mental Limit". People need to believe that it is possible. the sub four minute mile was a barrier for a long time, but it quickly was surpassed after Roger Bannister became the first to break that limit.
Bottom line is, we have the skills and tools to refactor code, so let's also use those skills to help refactor our selves; our minds, our bodies, our spirits, our well being. You name it, you can refactor it.
That's all well and good, but what in the world is "Human Refactoring"? It's the concept that, the methods we use to clean up and strengthen our code, can also be applied to ourselves. Our diet, exercise and sleep habits can be refactored (and considering the last almost 90 days I've had, boy do I understand this :) ).
We can refactor our brains by encouraging our brains to do new things. Activities that excite or calm the brain can be mutually beneficial. Sleep is a big component to helping us achieve our health objectives. Too little sleep prevents optimal healing (read: refactoring) of our bodies. The food that we eat, the substances we drink, and the air we breathe can be both beneficial and detrimental. Ultimately, it is up to us as to what we consume and in which quantities. To not beat on this too hard, I've come to really appreciate the solid benefits of dropping soda in favor of water, dropping packaged foods in favor of fresh foods, and looking to boost my intake of unique fruit and vegetables each given day. Additionally, I've moved to considering meat as a flavoring, rather than as a primary item at the center of my meals. The net result is a 45 pound drop in 90 days, with a goal to lose another 30 in the next 90 days.
Exercise can be very basic, and it doesn't take a lot to make small changes, but if you want or need to make radical changes, then you will need to put in a significant amount of time in addition to reducing calories to reach your goals. It may well be unpleasant, but it is bearable, and if you take time to get to your goals, and make small changes each day, then reaching that optimal burn rate will be possible. It will take time regardless, and dramatic changes will require dramatic effort, at least at first. I've found ten thousand steps a day to be effective, and I've also added a goal to eat 225 calories of fresh fruit every day, with 200 calories coming from fresh vegetables every day. The fruit calories are pretty easy to meet. The vegetable calories are a bit harder, but still doable with planning and paying attention.
Think about the environment you live and work in. Think of your desk. Think of your chair. think of your mental environment and your co-workers and their attitudes. Can they affect you? Answer is, certainly.
Something to consider it the idea of 'The Mental Limit". People need to believe that it is possible. the sub four minute mile was a barrier for a long time, but it quickly was surpassed after Roger Bannister became the first to break that limit.
Bottom line is, we have the skills and tools to refactor code, so let's also use those skills to help refactor our selves; our minds, our bodies, our spirits, our well being. You name it, you can refactor it.
Scaling QA With Docker, Jenkins and Mesos - Live from #AgileTD
Adé Mochtar & Maarten van den Ende put together a workshop based around the idea that we don't have to spend so much time manually setting up Selenium Grids. What's more, each of us were given a USB stick with the files and exercises to work with. The goal of the sessions is to be able to set up scalable and solid Selenium Grids, as well as writing maintainable and scalable Selenium / WebDriver tests.
At the moment, we have been setting up our environments so that we can load the environment and get it up and running. If you haven't seen much of me the past hour, well, that's why ;).
There are a bunch of components that are part of this package, including vagrant, selenium, selenium grid, jenkins, docker, a few virtualbox machines and scheduler called Mesos. For this process of scaling Selenium Grid, even in this small example, Mesos gives the flexibility that will allow as many CPUs and RAM that you can throw at the system. In our example, the CPU's are limited to the number of virtual machines we have created and are spinning up.
One additional cool aspect of Mesos is that it's a generic scheduler. It can be used to schedule anything, so any test and configuration can be run using it.
Very interesting model, I've just barely scratched the surface, but I am curious to play with it some more, seeing as I have it set up and all that :).
Wait, I'm Dying?! - Live from #AgileTD
The talk is a little misleading by the title. The talk is called "Testers Are Dying" and my first reaction was "OK, joy, another 'testing is dead' talk" but no, not really. The real issue is not that testing is going away, we actually need to keep up with the demand for testing.
But wait, how is there an increase of testing demand while we are seeing the role of traditional testing disappear? What gives?
Karen Greaves and Sam Laing are both with Growing Agile, a company located in South Africa. South Africa has a unique problem when it comes to electricity. They have significant power shortages and rolling blackouts. Thus South Africa has had to be creative when it comes to conservation of electricity.
The fact is a number of companies have taken steps to either eliminate or greatly reduce the headcount of their test teams. Yet there's more testing needed than ever. Again, what gives?
In many ways, we are dealing with a situation where multiple people are focused on a need for testing, but we have a shortage of people that need to use it. Going forward, the chances are the dedicated role will continue to see attrition, while the actual efforts and needs for them will increase.
The challenge that I see is that there is a dis-connect happening between the need for good testing and the questioning of the value of dedicated testers. If the issue is that the testers are seen as being of limited value, then there are two possible courses of action. Remove the testers (generally a bad idea) or improve the quality and understanding of the testing being performed, and extending the value of that testing to more and more people. Paradoxically, the more people are involved in the testing activities, the more likely dedicated testers will be retained, because the value of their efforts and what they bring to the table becomes clearer the more people actually test (shocking, isn't it ;)?).
Additionally, skills increases can help to make it possible for testers to leverage their skills. If the challenge is too many testers but, not enough testing, then having software testers that are very good at testing being able to spread the skills they have around, and encourage/effect the other members of their team will be a net positive. On the whole, many software testers are not so much dead weight but radically underutilized, or utilized in a very poor way. By having testers get involved earlier in the process, and having testing performed by as many people as possible, the visibility of testing improves, and an understanding of what testing actually is grows.
But wait, how is there an increase of testing demand while we are seeing the role of traditional testing disappear? What gives?
Karen Greaves and Sam Laing are both with Growing Agile, a company located in South Africa. South Africa has a unique problem when it comes to electricity. They have significant power shortages and rolling blackouts. Thus South Africa has had to be creative when it comes to conservation of electricity.
The fact is a number of companies have taken steps to either eliminate or greatly reduce the headcount of their test teams. Yet there's more testing needed than ever. Again, what gives?
In many ways, we are dealing with a situation where multiple people are focused on a need for testing, but we have a shortage of people that need to use it. Going forward, the chances are the dedicated role will continue to see attrition, while the actual efforts and needs for them will increase.
The challenge that I see is that there is a dis-connect happening between the need for good testing and the questioning of the value of dedicated testers. If the issue is that the testers are seen as being of limited value, then there are two possible courses of action. Remove the testers (generally a bad idea) or improve the quality and understanding of the testing being performed, and extending the value of that testing to more and more people. Paradoxically, the more people are involved in the testing activities, the more likely dedicated testers will be retained, because the value of their efforts and what they bring to the table becomes clearer the more people actually test (shocking, isn't it ;)?).
Additionally, skills increases can help to make it possible for testers to leverage their skills. If the challenge is too many testers but, not enough testing, then having software testers that are very good at testing being able to spread the skills they have around, and encourage/effect the other members of their team will be a net positive. On the whole, many software testers are not so much dead weight but radically underutilized, or utilized in a very poor way. By having testers get involved earlier in the process, and having testing performed by as many people as possible, the visibility of testing improves, and an understanding of what testing actually is grows.
Automation in Testing - Live at #AgileTD
Richard Bradshaw is a name a few of you out there are probably familiar with. Test Automation and Richard tend to go hand in hand, and Richard opens his talk saying that that might be a bit of a problem, and that he wanted to break free of that way of thinking.
In this talk, Richard is keen to look at the idea that "checks" are more accurate a phrase as in regards to automation. The bigger question to ask is "what does it mean when we perform test automation"? Are we "automating tests", or are we "automating checks"? What does the computer actually do for us? Computers are fast, accurate and stupid. Humans are slow, faulty and brilliant. Together, we can do magnificent things, but we are best suited to doing the things we are best adapted to. Automating is important, it needs to be done, and in many cases, it is a real lifesaver for a harried and overworked test team.
The key point to the whole "testing vs. checking" is that there is a need to use our brains to cover more and more areas. We can't remember it all, and frankly, we don't want to. There are so many steps that we have to keep track of that having a system that can keep everything running in sequence is wonderful. In these cases, I love having automation. It's especially helpful when you know that very step as defined will run the same way every time. The more that I interact with applications and I try to find things that are known issues, the more I find that I end up with a collection of terms and phrases. Each of those terms and phrases are areas I can search for next time. More to that point, commands I run over and over again, save a couple of variable changes, are wonderful areas for creating miniature tool chains (they can be a simple as a single line to parse a log file, or as large as an entire build sequence with a variety of possible conditions.
There are a lot of tools and programming environments out there, and many testers feel frustrated that they don't know how to use these tools. Yet these same "non technical" people do shell manipulations all day long, and many of them are saving those commands in executable files so they can save some keystrokes. These people are the unsung automators. Yes, they are doing automation. They just don't give themselves credit for it because they feel their scripts are not "sophisticated" enough. This is totally OK. This is actually a core part of the journey, and these early steps are key to getting the chops necessary to do more advanced automation.
We have to ask ourselves, why do we test? It's not to run the same things over and over again. Instead, it's to get new information about our product. Automation can help us find new things, but in many cases, it sequences events we know well, and looks for an event we expect to see. In these cases, green tests provide some comfort, but they don't tell us anything genuinely new. Automation will rarely lead us into new vistas, but exploratory testing certainly can. Every initial test we run is exploratory in nature, and as we get a better feel for what we expect to see, then we have space to create automation to cover the steps we know for the paths we have determined are important.
In this talk, Richard is keen to look at the idea that "checks" are more accurate a phrase as in regards to automation. The bigger question to ask is "what does it mean when we perform test automation"? Are we "automating tests", or are we "automating checks"? What does the computer actually do for us? Computers are fast, accurate and stupid. Humans are slow, faulty and brilliant. Together, we can do magnificent things, but we are best suited to doing the things we are best adapted to. Automating is important, it needs to be done, and in many cases, it is a real lifesaver for a harried and overworked test team.
The key point to the whole "testing vs. checking" is that there is a need to use our brains to cover more and more areas. We can't remember it all, and frankly, we don't want to. There are so many steps that we have to keep track of that having a system that can keep everything running in sequence is wonderful. In these cases, I love having automation. It's especially helpful when you know that very step as defined will run the same way every time. The more that I interact with applications and I try to find things that are known issues, the more I find that I end up with a collection of terms and phrases. Each of those terms and phrases are areas I can search for next time. More to that point, commands I run over and over again, save a couple of variable changes, are wonderful areas for creating miniature tool chains (they can be a simple as a single line to parse a log file, or as large as an entire build sequence with a variety of possible conditions.
There are a lot of tools and programming environments out there, and many testers feel frustrated that they don't know how to use these tools. Yet these same "non technical" people do shell manipulations all day long, and many of them are saving those commands in executable files so they can save some keystrokes. These people are the unsung automators. Yes, they are doing automation. They just don't give themselves credit for it because they feel their scripts are not "sophisticated" enough. This is totally OK. This is actually a core part of the journey, and these early steps are key to getting the chops necessary to do more advanced automation.
We have to ask ourselves, why do we test? It's not to run the same things over and over again. Instead, it's to get new information about our product. Automation can help us find new things, but in many cases, it sequences events we know well, and looks for an event we expect to see. In these cases, green tests provide some comfort, but they don't tell us anything genuinely new. Automation will rarely lead us into new vistas, but exploratory testing certainly can. Every initial test we run is exploratory in nature, and as we get a better feel for what we expect to see, then we have space to create automation to cover the steps we know for the paths we have determined are important.
Add Some "Docker" To Your Testing - Live from #AgileTD
I am one of those people. I use Docker. It's part of our infrastructure. I get the basics of containerization. I can start an instance, I can do work in them. That's all well and good, but how much do I know vs. how much do I just think I know? When I saw a session titled "Using Docker for Testing", I figured now was as good a time as any to see how much I actually knew about Docker and whether or not I could pick up some new things (the answer, to save you all some suspense, is "of course" ;) ).
first off, what is Docker specifically? Docker is one of a number of "container" technologies available. Containers allow you to package an application, with all of its dependencies, into a standardized unit for software development and testing. What that ultimately means is that a container is able to load an environment, and it should run the same way each time. the nice thing is that you don't necessarily need to know the machine internals to be able to share an app with others.
One of the nice implementations of Docker and a very helpful one in my work is that we use Docker to containerize our testing environments for automated tests, as well as our development environments and our customer appliances. The beauty of this is that we can create a variety of parallel machines, and we can run tests in a number of containers that can be set up rapidly and destroyed as soon as we finish. Instead of building machines from the ground up each time, we can open as many Docker hosts as we need, which helps make our tests run faster.
The tricky stuff starts to happen when we want to run multiple test runs, or with multiple different release versions, or some variety of tests that require a variety of machines. Here's where having a variety of docker containers help provide interchangeability. Jenkins provides a variety of Docker plugins that allow the user to be able to create new containers and destroy them after jobs are completed. Additionally, the containers can be created completely independent from any other job, and can be used with any slave, or can be called uniquely/individually.
One of the interesting approaches that can be used is to create a container that has Selenium, the app you want to test, and the configuration options so that the tests are run with the browser you intend to target. All of it is in the respective containers. One of the options for running across multiple hosts is a tool called Kubernetes. Kubernetes starts multiple nodes which in turn allocate container to nodes. It's an interesting paradigm, and worth looking into.
first off, what is Docker specifically? Docker is one of a number of "container" technologies available. Containers allow you to package an application, with all of its dependencies, into a standardized unit for software development and testing. What that ultimately means is that a container is able to load an environment, and it should run the same way each time. the nice thing is that you don't necessarily need to know the machine internals to be able to share an app with others.
One of the nice implementations of Docker and a very helpful one in my work is that we use Docker to containerize our testing environments for automated tests, as well as our development environments and our customer appliances. The beauty of this is that we can create a variety of parallel machines, and we can run tests in a number of containers that can be set up rapidly and destroyed as soon as we finish. Instead of building machines from the ground up each time, we can open as many Docker hosts as we need, which helps make our tests run faster.
The tricky stuff starts to happen when we want to run multiple test runs, or with multiple different release versions, or some variety of tests that require a variety of machines. Here's where having a variety of docker containers help provide interchangeability. Jenkins provides a variety of Docker plugins that allow the user to be able to create new containers and destroy them after jobs are completed. Additionally, the containers can be created completely independent from any other job, and can be used with any slave, or can be called uniquely/individually.
One of the interesting approaches that can be used is to create a container that has Selenium, the app you want to test, and the configuration options so that the tests are run with the browser you intend to target. All of it is in the respective containers. One of the options for running across multiple hosts is a tool called Kubernetes. Kubernetes starts multiple nodes which in turn allocate container to nodes. It's an interesting paradigm, and worth looking into.
"Muse"-ing on the state of Agile - Live from #AgileTD
Agile Testing Days is celebrating it’s biggest year yet. The total number of attendees at this event are numbering over 600. additionally, they have announced a variety of new conference dates in different locations in Europe for 2016, as well as an Agile Testing Days event scheduled for the U.S. in 2017.
One of the things that Agile Testing Days does is they give a “sponsors rapid fire round” so that the people who are sponsoring the event and are in the expo area get a chance to share their products and what they are offering. This gives the attendees a chance to hear what they are doing and offering, as well as to give them a few moments to “sell the crows” without doing so during the sessions themselves.
An additional fun element of this event is a Wild West theme. Contrary to popular belief, the "Wild West" goes well beyond the mid-west and western part of the United States. It also includes Canada, Mexico and South America for good measure (which makes sense, because as far as Europe is concerned, the entire "New World" counted as the Wild West, with lots of opportunities and new horizons to learn about). Lisa Crispin and Janet Grogory did a fun little session to help encourage everyone to get the most out of the conference, and dressing like prospectors helped get that point across.
Alex Schladebek and Huib Schoots handled the first keynote with "Where Words Fail, Music Speaks...", and it's not common to see a violin and a trombone as an opening remarks, but yet, here we are :). With renditions of music from "Star Wars", they explained how they learned how to play and why music is important to the discussion of software testing. Music is everywhere, it invokes emotions and passions, and it also helps inform about who and what we are. Therefore, the goal of the talk is to show how music can help inform and develop an appreciation for software testing and agile software development. One of the interesting things about music is that you get instant feedback. If a note is clean, you hear it. If a note is not clean... you hear it :). Music and learning have similarities. You get feedback, you reduce the complexity to practice, you learn the fundamentals, and then through muscle memory and practice you get a better feel for what you are doing. Also, in music, you don't practice what you are doing front to back, generally you practice different areas, and some things require more time and energy than others.
They played two examples of music. One song was the theme to James Bond, and another was "The Wild Asparagus". Almost everyone knows the tune to the James Bond theme, but not everyone is as familiar with the second song, so the mental image of the music had a much broader interpretation and "mental image".
Agile teams also have ways of interpreting their themes and their performances. As there are more performers, there is a greater need for coordination and focus, more so than a single performer will require. Additionally, different groupings will require different levels of formality. A session is more free form and open, while an Orchestra is more scripted and focused. Sessions have a structure, and a heuristic we can use is called STAR (Structured, Tune, Accompaniment, Rhythm). All of these are emphasized in different levels, but each performer needs to be aware of what they are doing and how they are doing it. Testers also have a variety of heuristics they can use.
Music also has what are called "cadences". There are definite cadences, or full cadences, that come to a conclusion and a sense of completion. and there are incomplete cadences, often min minor keys, that seem like they are going to end, but don't really, if they do, they "feel incomplete". testing has its own set of cadences as well, and if you are focused, you can tell when testing has reached a full or half cadence, or if it feels complete or not.
Exploratory testing has a correlation to music as well. if you follow the sheet music precisely, then you are following a defined script. By contrast, if you perform without sheet music, and play it by memory, you will likely vary and embellish the song. in short, you will not play it exactly the same way, and the more musicians you add, the odds of variation increase exponentially.
Music also contains certain patterns. If you know the patterns, then it is easier to improvise. By improvising, there's a greater chance you can vary your performance and your ability to adapt to different situations. As your team learns and grows, you will also get the ability to recognize patterns in applications, and how to interact and react as you are testing.
Nicely done, Alex and Huib :)!!!
Monday, November 9, 2015
Lean Café, a Half a World Away - Live Blog From #AgileTD
The past few days have been extraordinary, to say the least. Starting with a flight from San Francisco to Instanbul via Turkish Airlines, I had a too brief layover in Istanbul (one of the few times I've genuinely wished that I had more time between flights so I could get out of the airport and explore the city). The stopover in Istanbul was also noteworthy in that this is the farthest east I have ever traveled from where I have lived most of my life (i.e. California). Sure, it was just a stopover to get another flight to Berlin, but I set my feet down there, so it counts ;).
The flight to Berlin was enjoyable, and for the record, Turkish Airlines offers wonderful service, even to the economy passengers like myself. If you get a chance to fly with them, I encourage it. I landed in Berlin about 10:00 p.m. local time, and most of the services in the airport were closed. I was fortunate to have the information desk open, and when I asked them how I could get to the the Dorint-Sanssouci resort in Potsdam, she returned with a printout that had a bus route to a train, and then a train to a tram line, and then a walk to the destination. Part of me was dismayed (seriously, are there no cabs at this hour?), but the tester in me also smiled and said "OK, challenge accepted!" It made for a much more fun experience, and I had a change to see a lot more of the city this way, as well as the approach out to Potsdam. I will confess, the tram dropped me off at Park Sanssouci, and as I walked off at just before midnight, not a soul was around. No cars, no streetlights, no house lights, and I really wondered "where the heck am I?" Fortunately, a brief walk to the west, and I saw the destination. Made it!
Monday was a day to adjust and get used to being nine hours ahead, and also to get a chance to see the sights in and around Potsdam (courtesy my friend Mieke Mertsche, who showed me around and introduced me to several of the local details, including Red Bull Cola, and its characteristic pine tree flavor (seriously, it's in there :) ). Additionally, the speakers dinner took place in the central area of town, with good dinner, great conversation, and a chance to catch up with many friends both personal and virtual (it's still a little strange each time I have someone walk up to me and say hi, and then realizing they know me through my blog or via Twitter. Awesome, but still strange :) ).
Today being Tuesday, the Agile Testing Days conference has gotten underway proper, and first order of business is Lean Coffee (or Lean Café as the sign says). For those not familiar with Lean Coffee, the idea is that everyone writes down topics that they would like to talk about, then everyone votes on the topics they want to discuss, and a queue is made based on the votes. Each topic gets seven minutes to start, and then based on the energy in the group, more time is given to those topics until the energy runs out.
A topic I put into play received the top votes, so I presented the topic of "Testing and 'that other stuff'". In my daily reality, I test, but I do other things, specifically related to being a release manager. At times, it seems that I get more interest and attention towards my efforts to improve the release management process than i do as a software tester. Part of that, I think, stems from the fact that release management is an infrastructure and delivery problem, and it has a very concrete problem. either the builds are deployable, or they aren't. Testing has a lot of fuzz around it, i nthe sense that there is a lot of work done, but there's also a lot of judgment that can be applied to what is to be taken care of and what can be deferred. IT's all important, but in smaller teams, I don't have the luxury of being "just a tester", I need to be able to adapt to additional roles and needs. Frankly, I'm totally cool with that, and I've appreciated the opportunities to get involved in other areas. Still, at times, I've wanted to see what could be done to help encourage and improve the visibility of the testing work I and my team are doing. One suggestion to increase the visibility of testing is to have specific stories that showcase the testing effort, as well as the time it takes to do the testing. Fact is, people respond to the immediate needs, and if your role affects immediate needs, chances are people will pay closer attention to what you are doing when it directly affects what your team needs to accomplish their goals.
The next topic was "how do we incorporate more UX and UI design options into our work". For me, the biggest way that we can help with this is to get involved early in the design and discussion process. We use a three amigos approach to story development, and in that way, design, programming and testing get together to discuss the options available, and how we can put testability into the design, and to encourage UX from the beginning, rather than having to improve it later. One way that I have started to think about this especially (and a foreshadow of my talk tomorrow) is to focus on ideas of "inclusive design" where possible, and to encourage the idea of making the product as usable as possible by the largest volume of people. That process can really help drive UX discussion.
"How to do BDD 'Right'" was the next topic, and there have been a variety of experiences with trying to use it in organizations. Cucumber is a popular framework for this, so it's not uncommon to have people think of Cucumber as BDD, but it's just one way of doing it. The real focus behind BDD is the fact that Behavior is the primary focus, and the testing is based around the desired vs. actual behavior of an application. BDD affects UX and UI interactions, as well as other "ilities" of a product. Ideally, making tests that focus on individual behavior characteristics are going to be the most effective. Trying to cram multiple behaviors into a single test will make tests more complex and more difficult to maintain as time goes on. By keeping the behavior characteristics as simple as possible, and as atomic as possible, then tests are more specific, and ultimately easier to maintain.
"Starting a new team" focused on the issues of creating a new QA organization in a company. I've been in this situation a few times, and each time has been as unique as the teams hoping to implement the new approach. Testing is important, and it needs to happen at all levels of the product and process. Having a QA "role" may or may not be appropriate, but testing is going to happen, and absolutely needs to happen. Everyone needs to own quality, and everyone needs toe be a part of the testing equation. Encouraging a culture of continuous testing takes communication and setting an expectation that everyone needs to be involved in testing. If there is a dedicate tester role, more important than just testing is being able to share important and actionable information. Learn what the team does to share information. Learn how the team wants to deal with issues and defects, and the tools and infrastructure that is in place. Most important, testers need to learn the application they are working on and get as much experience with it as possible. It seems obvious, but that step alone really helps to get a feel for what is a nice to have and what is absolutely essential.
All told, a great start to the day. Looking forward to the next session. stay tuned for further posts (as I did at CAST, I will make a new post for each talk or topic). More to come, stay tuned :)!!!
The flight to Berlin was enjoyable, and for the record, Turkish Airlines offers wonderful service, even to the economy passengers like myself. If you get a chance to fly with them, I encourage it. I landed in Berlin about 10:00 p.m. local time, and most of the services in the airport were closed. I was fortunate to have the information desk open, and when I asked them how I could get to the the Dorint-Sanssouci resort in Potsdam, she returned with a printout that had a bus route to a train, and then a train to a tram line, and then a walk to the destination. Part of me was dismayed (seriously, are there no cabs at this hour?), but the tester in me also smiled and said "OK, challenge accepted!" It made for a much more fun experience, and I had a change to see a lot more of the city this way, as well as the approach out to Potsdam. I will confess, the tram dropped me off at Park Sanssouci, and as I walked off at just before midnight, not a soul was around. No cars, no streetlights, no house lights, and I really wondered "where the heck am I?" Fortunately, a brief walk to the west, and I saw the destination. Made it!
Monday was a day to adjust and get used to being nine hours ahead, and also to get a chance to see the sights in and around Potsdam (courtesy my friend Mieke Mertsche, who showed me around and introduced me to several of the local details, including Red Bull Cola, and its characteristic pine tree flavor (seriously, it's in there :) ). Additionally, the speakers dinner took place in the central area of town, with good dinner, great conversation, and a chance to catch up with many friends both personal and virtual (it's still a little strange each time I have someone walk up to me and say hi, and then realizing they know me through my blog or via Twitter. Awesome, but still strange :) ).
Today being Tuesday, the Agile Testing Days conference has gotten underway proper, and first order of business is Lean Coffee (or Lean Café as the sign says). For those not familiar with Lean Coffee, the idea is that everyone writes down topics that they would like to talk about, then everyone votes on the topics they want to discuss, and a queue is made based on the votes. Each topic gets seven minutes to start, and then based on the energy in the group, more time is given to those topics until the energy runs out.
A topic I put into play received the top votes, so I presented the topic of "Testing and 'that other stuff'". In my daily reality, I test, but I do other things, specifically related to being a release manager. At times, it seems that I get more interest and attention towards my efforts to improve the release management process than i do as a software tester. Part of that, I think, stems from the fact that release management is an infrastructure and delivery problem, and it has a very concrete problem. either the builds are deployable, or they aren't. Testing has a lot of fuzz around it, i nthe sense that there is a lot of work done, but there's also a lot of judgment that can be applied to what is to be taken care of and what can be deferred. IT's all important, but in smaller teams, I don't have the luxury of being "just a tester", I need to be able to adapt to additional roles and needs. Frankly, I'm totally cool with that, and I've appreciated the opportunities to get involved in other areas. Still, at times, I've wanted to see what could be done to help encourage and improve the visibility of the testing work I and my team are doing. One suggestion to increase the visibility of testing is to have specific stories that showcase the testing effort, as well as the time it takes to do the testing. Fact is, people respond to the immediate needs, and if your role affects immediate needs, chances are people will pay closer attention to what you are doing when it directly affects what your team needs to accomplish their goals.
The next topic was "how do we incorporate more UX and UI design options into our work". For me, the biggest way that we can help with this is to get involved early in the design and discussion process. We use a three amigos approach to story development, and in that way, design, programming and testing get together to discuss the options available, and how we can put testability into the design, and to encourage UX from the beginning, rather than having to improve it later. One way that I have started to think about this especially (and a foreshadow of my talk tomorrow) is to focus on ideas of "inclusive design" where possible, and to encourage the idea of making the product as usable as possible by the largest volume of people. That process can really help drive UX discussion.
"How to do BDD 'Right'" was the next topic, and there have been a variety of experiences with trying to use it in organizations. Cucumber is a popular framework for this, so it's not uncommon to have people think of Cucumber as BDD, but it's just one way of doing it. The real focus behind BDD is the fact that Behavior is the primary focus, and the testing is based around the desired vs. actual behavior of an application. BDD affects UX and UI interactions, as well as other "ilities" of a product. Ideally, making tests that focus on individual behavior characteristics are going to be the most effective. Trying to cram multiple behaviors into a single test will make tests more complex and more difficult to maintain as time goes on. By keeping the behavior characteristics as simple as possible, and as atomic as possible, then tests are more specific, and ultimately easier to maintain.
"Starting a new team" focused on the issues of creating a new QA organization in a company. I've been in this situation a few times, and each time has been as unique as the teams hoping to implement the new approach. Testing is important, and it needs to happen at all levels of the product and process. Having a QA "role" may or may not be appropriate, but testing is going to happen, and absolutely needs to happen. Everyone needs to own quality, and everyone needs toe be a part of the testing equation. Encouraging a culture of continuous testing takes communication and setting an expectation that everyone needs to be involved in testing. If there is a dedicate tester role, more important than just testing is being able to share important and actionable information. Learn what the team does to share information. Learn how the team wants to deal with issues and defects, and the tools and infrastructure that is in place. Most important, testers need to learn the application they are working on and get as much experience with it as possible. It seems obvious, but that step alone really helps to get a feel for what is a nice to have and what is absolutely essential.
All told, a great start to the day. Looking forward to the next session. stay tuned for further posts (as I did at CAST, I will make a new post for each talk or topic). More to come, stay tuned :)!!!
Tuesday, October 13, 2015
Aedificamus: Sixty Days In: Testing Myself as I Lose Weight
Two hundred and sixty pounds. That’s where I was on August 14, 2015. Officially recording the heaviest I have ever been. The thoughts going through my head were not pretty, but I decided on that day I needed to do something, anything other than stay the course I had found myself on.
Over the last twenty-five years, I have had a variety of ups and downs when it came to weight, fitness, leanness and other factors both health and aesthetic related. The past few years, my exercise habits have been mostly nonexistent. My eating has been haphazard, often on the side of over-indulging (yes, I did go to Kilwin's in Grand Rapids five times while I was there. It was fantastic, but I’m sure it had a part to play in the number I was looking at on the scale August 14th as well).
There’s an aphorism that says people will not do anything until they are “sick and tired of being sick and tired”. I reached that point, and I decided that, once again, it was time to do something. This time, though, I decided to get a bit more “tech” in my approach, and use it as an excuse to do a long term software testing project. In this case, the products being tested are health apps (currently focusing on two, but looked at a few more to evaluate), a Bluetooth digital scale, and revisiting some old exercise companions from decades ago (one of which I had not done anything with in more than 30 years).
My first course of action was to download an app called Pacer. The express purpose was to track my steps, with a goal to get in 10,000 each day. I would allow myself one day per week to not have to make that goal (typically Sunday). Over the ensuing two weeks, I explored every aspect of this app I could. I wanted to see how it tracked my steps, how accurate it was, what the GPS function could tell me, and what the graphs and charts could tell me. I decided to spring for a year’s premium service just to see what the deal was with the extended options (mostly around setting goals and tracking them). I’ve collected a pretty nice list of GPS maps showing me where I’ve been and what ground I’ve covered. I have feelings of “oh, that’s neat” mixed with “wow, that’s a little creepy”, but if people want to see where I’ve walked and it intrigues them, be my guest :).
At the two week mark, I had already dropped ten pounds. Going from doing nothing structured to putting in 10,000 steps a day, that’s not at all surprising. It was at this point I added the LoseIt app to my daily routine for conscious calorie counting. I had first put together my own little spreadsheet with some of my own calculations, but a touch of laziness and a desire to have the device directly gather and present the data won out. I’ve been actively using LoseIt since August 30, 2015.
After two weeks of calorie counting, tracking meals, scanning labels, and getting involved with a few challenges, I added a Bluetooth scale into the mix, and committed to using it every day. More on that in a bit.
Once I squared away the walking, the calorie counting and regular weighing, I decided to add additional exercise in the form of free weights, an old school isometric device called a Bullworker and its smaller cousin, the Steel-Bow, and to keep things interesting, I’ve added in yoga as a daily practice (using a lot of different resources, but I've found the Fitstar Yoga app to be a good one). Like with the steps, I typically take a day off each week, usually Sunday.
This morning (10/13/15), I stepped on the scale and weighed in at 226.6 pounds. That’s 33.4 pounds less than I weighed 60 days ago. Averaged out, that's a little over four pounds weight loss per week. An ideal amount would be two pounds per week, maximize fat burning and minimizing catabolism (muscle loss). When you get beyond two pounds a week, it’s a guarantee that water weight, and muscle mass, is getting put to the torch as well. Granted, I am going to lose some muscle mass regardless (that's just the nature of the tradeoff; I can put on appreciable muscle by adding a little fat, or I can remove appreciable bodyfat by sacrificing a little muscle).
Overall, I feel pretty good about this weight loss and what it’s meant for me and my overall health. There have been some significant positives:
- According to my spouse, I no longer snore, or at least, if I do, it’s significantly less frequent.
- Walking for considerable distances is no longer a chore or feels like it takes much effort.
- Even with the brief period of time I have been doing yoga, my flexibility is slowly improving, and many aches in joints are slowly disappearing.
- My clothes, which were getting embarrassingly tight, are now becoming embarrassingly loose.
- My calorie budget, which at first felt hard to meet, now feels very doable each day.
Sounds all rosy and great, right? As a software tester, have I found any “bugs” in these protocols? Perhaps.
The scale I use measures weight, body fat percentage, hydration and BMI. I feel I can trust the physical weight and the BMI calculation, because they are fairly consistent and based on pretty simple algorithms. The body fat percentage and hydration values, however, I don’t feel I can trust at all. The reason? They are directly counter to one another. If I have a day where I have significant body hydration, then my body fat reading is lower. If I have a day with significantly low body hydration, then I get a body fat percentage reading that is much higher, as in six or seven percentage points higher. The dramatic rise and fall of my bodyfat percentages are tied exactly to the increase and decrease of hydration. In other words, the readings are not worth calculating and tracking as any official values, but it is good to know that when I’m well hydrated, I’m skinnier… err, sorta’.
There is some interesting weirdness that happens when you try to “share” data from one app to another. iOS 8 and above has the Apple Health app, and Health can help use a lot of data being generated by the phone (its accelerometer in particular) and coordinate with other apps and devices to tell you how many steps you have taken and how many calories you have burned. This data can be read by Health coming from apps, and can be written back to apps from Health and from other respective apps. In some conditions, LoseIt will add a calorie and step bonus that gets recorded back as more steps than you took, which then gets fed to Pacer which adds to the total as you walk, which causes further step rewards to be added, and the count can feel wildly off. Limit the two way read and write options allowed so that apps don’t conflict with each other and inflate numbers.
I’ve been playing with a LoseIt challenge based around eating more fresh fruit and vegetables. For every seventy-five calories I consume of fruit, I earn a point, with a maximum of three per day. For every twenty five calories of vegetables I eat, I earn a point, with a maximum of eight points per day. That means I aim to get two hundred and twenty-five calories from fruit and two hundred calories from vegetables each day. Getting the fruit calories? Not difficult. Getting the vegetable calories? That is proving to be a challenge. In addition, I’m keeping track of how much it costs to get those vegetables and fruit so I can get those proportions. Suffice it to say, it is not cheap! Also, many packaged foods, such as vegetable mixes with a variety of ingredients, don't get calculated well. You will have to take the items, separate them (physically or mentally) and tally up the total of each item. rather than just scanning the code for the bag, you enter in the amount of carrots, the amount of peas, the amount of beans, and so on. I keep a set of measuring spoons, measuring cups and a digital scale in my bag at all times for this purpose... yes, I sometimes get interesting stares ;). Over time, you also get good at guessing content, so you can "eyeball" an amount of a food and come to a close approximation of its size and quantity.
I always knew that sodium was a big part of weight gain (specifically because of its role in holding water in your system) but I didn’t realize just how much of an issue it really was, or how prevalent sodium is in the food we eat. Generally, every time I would eat out I would put on one or two pounds, and I would subsequently lose that one or two pounds in a couple of days if I prepared my own food and focused on adding no additional sodium.
Exercise helps you burn calories, but nowhere near the rate you think that it will. I have a little bag of trail mix that is three hundred calories when eaten. To counteract that three hundred calories, I need to walk for an hour, or run several miles, or some other combination that will cover that three hundred calories through exercise. In short, it is much easier to just say "no" to the trail mix than it is to say “sure, have at it, I can walk it off later!”
Fitness takes time, and if you are looking to lose a significant amount of weight, it takes a significant amount of time! Ten thousand steps is on average an hour and forty minutes of active walking. A Yoga session lasts anywhere from 30 minutes to an hour, a weight training session takes about the same time. Keeping the walking consistent and switching up the exercise options, you are still looking at two to three hours of activity each day to make a dent in your weight. No question, it takes time and effort, and that time and effort takes away from other things. In my case, it really takes away from my time to blog. I’m still working out how to keep these two options going at the same time.
There you have it. Sixty days in, and a piece of what is my reality today. Anyone who says losing weight is easy needs to be kicked. It’s simple, sure, but on the whole, it’s a hard thing to do day in and day out. Additionally, as I’ve said to myself many times before, it’s not a “brief change of behavior” thing. If I hope to be successful, I need to be making commitments and scheduling the time to do this and developing the discipline to eat like this daily for the rest of my life. Too often, I sabotage myself through complacency. I reach a goal, I let go of the reigns, and then I find myself back where I started, and then some. I’m really hoping to make this time be different. Perhaps by making this public, and part of my site legacy, that extra motivation will do the trick. We shall see :).
Subscribe to:
Posts (Atom)


















