“In the last decade, the software development community has strived to build software the “right” way, focusing on technical practices and ideas to ensure high-quality results. But building the product right and building the right product are two different things. We need to do both in order to succeed.
Blog: What if your first cycle ends up with zero story points completed? Blog: Performance Testing Basic’s – What is Throughput? Blog: The Chaos Addiction Article: 5 Common Mistakes We Make Writing User Stories Article: Use Selenium Grid to enhance testing of web applications Article: Dancing with Pigs Article: Platforms …
Blog: A simulation to show the importance of backlog prioritization Blog: Measuring Code Blog: Working with the testing debt – part 3 Article: Are You a Whole Team? Article: Agile Project Dashboards Article: Power and Influence Charting: The Google Way Tool: Reqline Requirement Management Tool Tool: ckwnc – creating UML …
This book defines acceptance tests not as the traditional user acceptance tests performed after implementation, but as the tests created by the customer in collaboration with the developer and the tester prior to implementation. Ken Pugh proposes mainly an approach where all project stakeholders will collaborate to create tests that …
The last Methods & Tools asked the following question: “Which format is used to express requirements in your organization?” Free text 36% User Stories 23% UML Use Cases 20% Other format 7% Requirements are not formalized 14% Participants: 325 Ending date: April 2011 Source: Methods & Tools Requirements Survey The …
Methods & Tools – the free e-magazine for software developers, testers and project managers – has just published its Winter 2010 issue with the following articles: * Non-Functional Requirements: Do User Stories Really Help? * Software Testing Dojos * Process improvement, The Agile Way! * Tool: Apache ServiceMix * Tool: …
