Keep an Eye on Agile in 2017

starwest

Keeping an eye on the horizon in the testing world is an important part of staying in the game. Hans is no stranger to looking to the future with eyes wide and ears open. His expertise is what makes Hans valuable at the STARWEST Expo, which he recently delivered two talks to.

STARWEST is one of the most respected conferences to date and longest-running conference on software testing and quality assurance. This year’s event week featured over 100 learning and networking opportunities, covering a wide variety of some of the most in-demand topics.

With such a variety of fresh ideas to explore, we decided to catch up with Hans and enquire about what he think are the up and coming topics to pay attention to.

1. How do you think Agile and Devops will develop in 2017?

From what I’m seeing DevOps, in particular CI/CD, is getting more attention these days than Agile. The distributed version tracking system Git continues to change the landscape, and drive good workflows for system development. This includes distributed models, as alternatives or additions to methods like Scrum. Organizations like our own are learning from the open source community how to best produce stable software and control its quality, including in projects where team members are not co-located. Our methods and practices, and our Services organization, are well positioned to effectively support the many variations in workflows we are seeing in the market.

2. How many STARWEST conferences have you managed to attend?

Quite a few. I’m doing Star and some other Techwell conferences since 1998. As far as I can tell I have done 16 STARWEST conferences.

3. Did you notice any trends starting to gain momentum in automation?

Definitely. The field is undergoing major changes. The main ones obviously being Agile and DevOps. This is actually helping the ideas presented in my talks move forward very well.

4. What did you enjoy most about this conference? Why?

Meeting and talking with the delegates, hearing about their challenges and their own ideas and solutions. It is also great to see other speakers again that I have got to know over the years.

5. What is the atmosphere like, and how has it changed/grown from the first one you attended (if at all)?

The atmosphere is great, and has in fact not changed much. It is very open and all about sharing ideas and experiences.

6. What was the best feedback you received about your talk?

I get a lot of feedback during the conference. For me the best response is if people say they will use the ideas from the classes into their own practice, meaning that what was presented really made a difference.

7. What do you think is the most important part people took away from each talk?

For most of my talks that would be the importance of good test design to make automation successful. In my view automation is not as much a technical challenge as it is a test design challenge. This is not a common message, but it is the basis of our Action Based Testing (ABT) method. The idea is to divide tests into modules, and to develop them as a sequence of keyword-driven “actions”.

 

Hans Buwalda

Hans leads LogiGear’s research and development of test automation solutions, and the delivery of advanced test automation consulting and engineering services. He is a pioneer of the keyword approach for software testing organizations, and he assists clients in strategic implementation of the Action Based Testing™ method throughout their testing organizations.

Hans is also the original architect of LogiGear’s TestArchitect™, the modular keyword-driven toolset for software test design, automation and management. Hans is an internationally recognized expert on test automation, test development and testing technology management. He is coauthor of Integrated Test Design and Automation (Addison Wesley, 2001), and speaks frequently at international testing conferences.

Hans holds a Master of Science in Computer Science from Free University, Amsterdam.

Hans Buwalda
Hans Buwalda, CTO of LogiGear, is a pioneer of the Action Based and Soap Opera methodologies of testing and automation, and lead developer of TestArchitect, LogiGear’s keyword-based toolset for software test design, automation and management. He is co-author of Integrated Test Design and Automation, and a frequent speaker at test conferences.

The Related Post

As CTO of Xebia and highly experienced in offshore testing in India, Guido articulates his methods in addressing common challenges faced by the in-house and offshore teams. He weighs heavily on strategic tactics as well as key cultural aspects to execute efficient and effective Agile methods. 1. I work at a US-based company and we ...
Video narrated by MICHAEL HACKETT – Certified ScrumMaster This is Part Three of a Four Part Video on “New Roles for Traditional Testers in Agile Development” Michael shares his thoughts on “A Primer – New Roles for Traditional Testers in Agile”   LogiGear Corporation  LogiGear Corporation LogiGear Corporation provides global solutions for software testing, and ...
Janet Gregory draws from her own experience in helping agile teams address alternative ways to cope with roadblocks including projects without clear documentation, testers with limited domain knowledge and dealing with either black box or white box testing. For testing on projects without clear documentation, is exploratory the only method? I often make “tester errors” ...
Video narrated by MICHAEL HACKETT – Certified ScrumMaster This is Part Four of a Four Part Video on “New Roles for Traditional Testers in Agile Development” Michael shares his thoughts on “A Primer – New Roles for Traditional Testers in Agile”   LogiGear Corporation  LogiGear Corporation LogiGear Corporation provides global solutions for software testing, and ...
Continuous Improvement and Short Feedback loops (think: Test Driven Development; Sprint Demo/Review; …) are at the core of any Agile process. Without a structured improvement process it can be difficult for teams to improve and without improvement we stagnate. For methods like Scrum, XP and et al., Retrospectives are that tool.
If your Agile implementation is not about people, you’ve missed the boat! The most profound impact to becoming more Agile is happier teams! Agile manifesto Value #1: * Individuals and interactions over processes and tools Words like these do not show up in Waterfall or RUP SDLC process descriptions. Agile cannot get more basic than ...
Agile methods were developed as a response to the issues that waterfall and V-model methodologies had with defining requirements and delivering a product that turned out to be not what the end user actually wanted and needed. From www.agiletesting.com.au A software tester’s role in traditional software development methodology, a.k.a waterfall & the V-model can be ...
Agile stresses instant and easy communication and is built on teams working efficiently together. This necessitates an open work space environment. A characteristic of an effective team is a high level of collaboration, making the physical work environment an important factor. Cubicles should be eliminated in favor of an open work space in an effort ...
LogiGear Magazine – July 2013 – Agile Testing
Agile is a philosophy focused on delivering constant value to customers incrementally and frequently, based on communication and feedback. These two ingredients are vital to a successful Agile recipe. Agile is no longer a buzzword or an unknown territory in the industry. Agile has progressed leaps and bounds the last few years and has matured to ...
One of the challenges with building an application these days is the number of dependencies that application will actually have on other applications. Ideally in order to know how that application will actually perform, application developers would be able to test their application against the application it depends on running in production. The odds of ...
Writing code that is easy to read and easy to test is difficult to achieve. The fact that poorly written code can function often leads to coding practices that are effective but not necessarily efficient. Too often, many programmers fresh out of school write code in the manner that was effective for passing their courses, but contains ...

Leave a Reply

Your email address will not be published. Required fields are marked *

Stay in the loop with the lastest
software testing news

Subscribe