Methods & Tools Software Development Magazine

Software Development Magazine - Project Management, Programming, Software Testing

Scrum Expert - Articles, tools, videos, news and other resources on Agile, Scrum and Kanban

Methods & Tools - February 2022
Sharing global software development expertise since 1993

=== Sponsor ===

TimeShiftX - Travel in Time, Test with Ease

TimeShiftX lets you time travel your software into the future or past to temporal test date and time sensitive functionality and code such as year-end, daylight savings, billing, and policies. Employ instant time travel inside Active Directory & Kerberos without changing system clocks, editing code, or isolating servers. TimeShiftX is multi-platform, cloud & container compatible, and supports all applications and databases.

Start your free trial today!

*** Updates ***

Last Articles Published on Methods & Tools Website

MeuScrum - Free Online ScrumTool MeuScrum is a free online Scrum tool. It provides simple features that allow managing project, people, releases stories, tasks and sprints. MeuScrum is available in English, Portuguese (Brazil) and Spanish Read more...

*** From The Archives ***

Articles from Methods & Tools' Archives

Something Old, Something New: Requirements and Specifications For many, perhaps most, development teams the terms requirement and specification are used interchangeably with no detrimental effect. In everyday development conversations the terms are used synonymously, one is as likely to opt for the "spec" as the "requirements." However it is sometimes useful, and occasionally important, to differentiate between the two terms. Read more...

=== Sponsor ===

Advertise with Methods & Tools

Reach an audience of more than 60'000 professional software developers, software testers and project managers publishing with Methods & Tools for as low a $60 / month. Do you want to promote a software development tool or conference? Are you interested in buying a link to your website from a good reference?

Contact Methods & Tools today to advertise with us!

*** Quote of the Month ***

It's beyond time we reexamine the post-incident question of luck, and I submit: asking "how we were lucky" in an incident retrospective is not only a waste of you and your colleague's time, it is distractingly detrimental to post-incident analysis.

An obvious reason why "luck" discussions are not useful: what are you supposed to do with aspects of the incident attributed to a good outcome of a roll of the dice? We don't follow-up a "lucky" attribution by asking "What will you do next time to be lucky? How can we all get luckier in the future? Can you teach me how to flick my wrists just right when I let go of the dice?" Director James Cameron is oft-quoted as saying "Hope is not a strategy; luck is not a factor" and spending time talking about something, by definition, we have no control over is placing a pretty big bet on hope. For all of the discussions of "luck" I've heard in incident retrospectives, I've never seen anyone put "Be more lucky again next time" on the list of action items that goes to the boss' boss.

A second, and more important, reason why an attribution of "luck" is unhelpful in incident analyses: its use often masks other aspects of the system that we can influence and when we chalk it up to "luck" and move on, we miss a big opportunity. In a recent retrospective, someone said "We were really lucky Sam happened to be on the call for this incident; he's worked here a really long time, and he noticed that error code didn't look quite right, which led us all to investigate and find the triggering issue. Nobody else would've found that as quickly."

Source: What's Luck Got To Do With It?, J. Paul Reed,

*** Software Development Linkopedia ***

Text: Lessons from Leading a Remote Engineering Team. You may think that managing remote teams is hard, and it is, but there are real benefits that you can achieve by being open to remote employees and building a remote team. Let's talk about the benefits of a remote team, how to build your remote team, and how to set your people up to succeed.

Text: Mutation Testing For those who are not familiar with it, mutation testing is a method of evaluating test quality by injecting bugs into the code and seeing whether the tests detect the fault or not. The more injected bugs the tests catch, the better they are.

Text: Don't Let Legacy Code Make You Suffer. Make It Suffer. Feeling like the codebase you're working on is poorly designed? Wish you could focus on writing good code, rather than trudging through mud code all day long? Would life be easier if only the legacy codebase had a clearer structure? If you answered “Yes” to any of those questions, be aware that you're not alone. Quite the opposite, in fact. You only need to talk to people for more than a minute at meetups or conferences to realize that a significant amount of developers suffer from legacy code.

Text: Delivering on an architecture strategy In this article I'll show that we can achieve a sustainable balance between feature delivery and foundational architectural work by empowering teams with autonomy, and fostering a strong partnership between product and tech on within those teams. We'll also see that autonomy isn't enough. To make coherent progress on architectural goals, our teams also need to align behind a shared vision. The Strategic Architectural Initiatives framework delivers that alignment, allowing you to reap full benefit from your high-performing teams.

Text: How to track automation tests coverage & statistics. All QA Engineers eventually face the need for automation tests coverage tracking and statistics gathering. How to solve this problem with minimal losses and maximum wow effect (and benefit for yourself surely)?

Text: Barriers to Agility Agile organizations require different leaders, cultures, and structures. In this article, Zuzana "Zuzi" Šochová explains that the fewer barriers you give agility on the way, the more likely the frameworks, methods, and practices can make a difference. You don't have to start with changing everything immediately, but sooner or later such change is inevitable.

Text: How to Deal with Software Tester Burnout The problem of occupational burnout among people due to the lack of interest in the tasks assigned or the unevenness of the assigned load has been extremely acute these days. And the field of software testing is not an exception for this issue. This article proposes tips on how software testers can deal with burnout.

Video: Efficiency vs Effectiveness in Agile. Learn the difference between effectiveness and efficiency, and whether your software development team can be agile without knowing it.

Video: What Is The Ideal Programming Language? What would your ideal programming language look like? Erik Doernenburg, head of technology at Thoughtworks, and Richard Feldman, author of "Elm in Action," sat together at GOTO Copenhagen 2021 to chat about what theirs would look like. They also had a look into the future of up-and-coming programming languages.

Video: Expert Talk: DevOps & Software Architecture. In a world where software architecture is evolving rapidly, we are confronted with new challenges. Simon Brown, Dave Farley and Hannes Lowette cover some recent trends in software architecture, touching on hot topics such as DevOps and how to deal with complexity. At the same time they discuss bounded context and continuous delivery and how they are still being misunderstood by the industry.

Video: Transforming Agile Teams Through Feminist Leadership. Feminist Leadership is about capitalizing on the ideas and skills of as many individuals as possible by establishing team cooperation and group leadership instead of competition and personal leadership; it seeks to develop power "with others" instead of power "over others."

Video: What Should Software QA Do? This talk tries to answer the question of what the software quality assurance (QA) team should be doing, and how it is not only more fruitful for the software development organization, but a more rewarding path for the Testing Craftsman.

Tools: Scrumlr is an open source web app for collaborative online retrospectives

Tools: EaselQA is an Open Source, Codeless, End to End Test automation framework.

Tools: RetroCadence: The Best Retrospective Tool For Agile Teams The retrospective is arguably the event that will yield the most benefits for your agile team. This is because it is the place where you identify crucial, valuable improvements for your team that will drive ongoing performance improvements. Such improvements allow your team to deliver higher value products in a shorter timescale.

=== Web Sponsors ===

This month, the Methods & Tools website is supported by,, Software Testing Magazine and Scrum Expert. We thank them for their support.

*** Software Development Training ***

Software Development Lifecycle Specialization: This course is designed for people who are new to software engineering. It is also for those who have already developed software, but wish to gain a deeper understanding of the underlying context and theory of software development practices.

Contact us if you want to your training courses listed in this newsletter and reach 35'000 software development profesionnals worldwide.

*** Featured Software Development Conferences ***

Agile Alliance Agile2022, July 18-22 2021, Nashville, USA

Pacific Northwest Software Quality Conference, Portland, USA, October 10-12 2022

Contact us if you want your software development conference listed here.
Find more upcoming conferences on,,

November 2022
October 2022
September 2022
August 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
November 2009
October 2009
August 2009
May 2009
April 2009
February 2009
January 2009
November 2008
October 2008
August 2008
May 2008
April 2008
February 2008
January 2008
November 2007
October 2007
August 2007
May 2007
April 2007
February 2007
January 2007
November 2006
October 2006
August 2006
May 2006
April 2006
February 2006
January 2006
November 2005
October 2005
August 2005
May 2005
April 2005
February 2005
January 2005
November 2004
October 2004
August 2004
May 2004
April 2004
February 2004
January 2004
November 2003
October 2003
August 2003
May 2003
April 2003
February 2003
January 2003
November 2002
October 2002
May 2002
April 2002
February 2002
January 2002
November 2001
October 2001
May 2001
April 2001
February 2001
January 2001
Winter 2000
Fall 2000

Methods & Tools
is supported by

Software Testing

The Scrum Expert