Methods & Tools Software Development Magazine

Software Development Magazine - Project Management, Programming, Software Testing

 

Methods & Tools - November 2017
Sharing global software development expertise since 1993


=== Sponsor ===


TimeShiftX – Travel in Time, Test with Ease

TimeShiftX lets you time travel your software stack into the future or past to temporal test all date and time sensitive functionality and code such as year-end, daylight savings, leap year, billing, policies, etc. Employ instant time travel inside Active Directory & Kerberos without code changes, manual work, or server isolation. TimeShiftX is multi-platform, cloud compatible, and supports all applications and databases.

Start your free trial today!


*** Updates ***


Last Articles Published on Methods & Tools Website

Communication Tips For Software Architects Communication is one of the most important skills for a software architect. Technical background is important to make technical decisions, but without proper communication it is not possible to explain the chosen technical solution and to sell it to the stakeholders. Communication skills (or the lack of communication skills) can have a large impact on the success of software development projects. Read more...


*** Quote of the Month ***


To reiterate, an aspirant architect should have in-depth knowledge in either one of the application, data or infrastructure domains. Just has having at least one pillar to support the roof of a house is essential, an IT architect needs depth in at least one of the domains to support a solution architecture “roof”.

A critical related concept is architect depth. Having depth in one of the domains is important, but it is not necessary, or advisable, to act as the SME for that domain. Architect depth loosely means that, that at most, the role requires only the level of expertise and input required to develop and communicate architecture-level information. For example, an architect who was a software developer in a former job should understand that at architect depth, there is no need to get into detail design decisions. Provide breadth and depth, but do not step on the toes of the developer team in the process. A good architect should always include the developer’s point of view in a proposed solution; as it is important for that person, normally the SME for that system or application, to buy into its planned implementation. That is because those selfsame developers will be the ones implementing and supporting it. Although this example comes from the application development world, the same concept applies to business, data, and infrastructure domains. Navigating this process can sometimes be difficult. When an architect’s specialized skills coincide with the application or system on which he or she is working, there can sometimes be a temptation to dive into the details and to take control of the entire depth. Inevitably, this leads to frustration for other members of the team, who have trouble determining where their expertise begins and the architect’s expertise ends.

Source: How to Become an IT Architect, Cristian Bojinca, Artech House, ISBN: 9781630811464

Readers can buy this book with a 40% discount on http://us.artechhouse.com/How-to-Become-an-IT-Architect-P1851.aspx until the end of 2017 using the code "MethodsAndTools2017".


=== Sponsor ===


Scrum Expert

Scrum Expert presents Agile articles, resources, book reviews, tools lists, conferences schedule, videos and industry news about Agile software development and project management using Scrum and other Agile and Lean approaches like Kanban, eXtremme Programming or Software Craftmanship with a global perspective.

Visit http://www.scrumexpert.com/ today!


=== Web Sponsors ===


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


*** Software Development Linkopedia ***


Text: How to build quality into your software development workflow

Text: UX Mapping Methods Compared: A Cheat Sheet

Text: How to Set the Technical Direction for Your Team

Text: Writing tests like a novelist

Text: Great product managers don’t spend their time on solutions

Text: Functional Testing Scenarios for Mobile Apps

Text: Four Steps for a Successful Scrum Product Demo

Text: Test Impact Analysis

Video: Becoming a Skeptic Software Tester

Video: Continuous Delivery with Docker Containers and Java EE

Video: How to Select an Agile Scaling Framework

Video: Mixing Tests and Production Code With Doctest

Video: Coaching Agile Technical Practices

Tools: Mobly is a E2E test tool for complex environment requirements.

Tools: Wekan is an open source Trello-like kanban board

Tools: Updated version of Using Commercial Scrum Tools for Free

Find more interesting links on the software development tools, the software development articles or the software development videos websites.


*** Partner Software Development Conferences ***


ConTEST NYC, November 29- December 1 2017, New York, USA

AgentConf, 27-28 January 2018, Spielboden Dornbirn, Austria

Aginext.io London, 23 March 2018, London, UK
The call for papers is open until the November 30 2017

Agile on the Beach, 12-13 July 2018, Falmouth Cornwall, UK
The call for papers is open until the December 20 2017


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

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

Software Testing
Magazine


The Scrum Expert