Software Development Magazine - Project Management, Programming, Software Testing |
Scrum Expert - Articles, tools, videos, news and other resources on Agile, Scrum and Kanban |
Methods & Tools - September 2019
Sharing global software development expertise since 1993
=== Sponsor ===
5 Ways to Time Travel Test [Whitepaper]
Temporal testing is critical for date sensitive business rules such as insurance rates, billing, and enrollment. Efficient time travel testing can increase your test coverage, accelerate development, and improve software quality.
Read our whitepaper to learn the 5 ways to time travel software!
*** Updates ***
Last Articles Published on Methods & Tools Website
Helping Software Development with a Product Discovery Phase In the software development, it is common that clients approach development agencies like ours with a product they want to create. However, sometimes these ideas involve a huge product or sometimes a smaller one, but it still has some undefined aspects; for example uncertainties about its potential users, its functionalities, monetization strategy, etc. which can make the estimation process difficult. This article explains what the Product Discovery process is all about and why it is essential for a successful software development project. Read more...
*** From The Archives ***
Articles from Methods & Tools' Archives
Five Symptoms of Mechanical Agile This article provides five stories, mostly based on real life, that might help you see how Agile and Scrum can become mechanical and what you should do about this. Processes cannot be mechanical, they have to be living, breathing processes that can adapt effortlessly. The only way to have processes that are alive like this are to have openings in them for people to do what they think is the right thing to do. We need to allow people to act like people, and not try to force them into a machine model that we've created for them. Read more...
=== Sponsor ===
Enov8 Environment Manager - DevOps at Scale
Enov8 Environment Manager is an out of the box "IT & Test Environment Management" platform that allows you to drive productivity across your IT projects and DevOps teams. A "DevOps at Scale" solution that improves transparency, control and cost optimization. Use Enov8 to model IT environments, monitor health, identify demand (including bookings), centrally planning & coordinate, standardise & automate release operations and improve through enterprise status accounting & reporting.
Learn more on enov8.com
*** Quote of the Month ***
A few years back, I was working with an organization where teams were achieving the expected increase in velocity, but leadership didn't feel like things were moving any faster. Selecting one team, we looked at their history and found that their velocity had gone from an average of about 20 points to an average of about 40. On a hunch, we ran a report to figure out the average story size for each iteration. Sure enough, the average story size had gone from around 1.4 to around 3.1. In fact, you could see a punctuated increase in average size followed by a slow but steady incline. The punctuated increase came right around the time leadership introduced the new burn up charts and put a focus on velocity.
Looking at the average number of stories completed per iteration, the numbers were telling. With an average velocity of 20 at 1.4 points per story, they were completing around 14 stories per iteration. With an average velocity of 40 at 3.1 points per story, they were completing around 13 stories per iteration. Were they in fact moving faster and the stories were coincidentally larger? How could we know for sure?
We took an evenly distributed sampling of stories across the history of the project and printed them out without any sizing information. We then asked the team to size the stories using the same techniques they'd always used. The average story size came out to be approximately 2.8 with earlier stories growing from an average of 1.4 to 2.6.
Had they been gaming the system? No. As we've already discussed; we game the system when we change it, the resulting behaviors are just natural consequence. We can't know for sure if there was, at one time, a deliberate increase in story sizes, but we can say that under the given conditions, the team genuinely believed the larger numbers were more accurate.
Source: Escape Velocity - Better Metrics for Agile Teams, Doc Norton, https://leanpub.com/escapevelocity
=== 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 Linkopedia ***
Text: Product vs. Feature Teams
Text: Don’t get locked up into avoiding lock-in
Text: Clean up bad BDD scenarios
Text: Team Leader Venn Diagram
Text: Why Don't We Just Call Agile What It Is: Feminist
Text: Addressing The Elephant: And Why Most Conflicts In Teams Are Invisible
Text: Most Common Mistakes of ScrumMasters
Video: Are DevSecOps, Containers & Shift-Left just Buzzwords?
Video: Challenges of Serverless Java
Video: Agile Requires Excellence
Video: Automatic Testing of a Heavily Integrated Software
Video: How NOT to Implement Agile
Tools: Exploratory Testing Chrome Extensions
Tools: Commercial Scrum Retrospectives Tools
*** Promoted Software Development Conferences ***
Pacific Northwest Software Quality Conference, October 14-16 2019, Portland, USA
Agile Tour London, October 18 2019, London, UK
STARCANADA Testing Conference, October 20-25 2019, Toronto, ON, Canada
Agile + DevOps East, November 3-8 2019, Orlando, FL, USA
Contact us if you want your software development conference promoted here.
Find more upcoming conferences on SoftDevConferences.com,
ScrumExpert.com,
SoftwareTestingMagazine.com
Methods & Tools Testmatick.com Software Testing Magazine The Scrum Expert |