-
- Current Issue
- Comments
-
EA’s Jane Fraser Talks Complex Systems
March 30, 2012 By admin -
LogiGear Magazine – February 2012 – The Training Issue
February 07, 2012 By admin -
Letter From The Editor – February 2012
February 07, 2012 By admin -
Fun & Games: Keep Training Lively
February 07, 2012 By admin -
Black Box Software Testing: Test Design Course
February 07, 2012 By admin
Category: Agile
User Stories, Scenarios & Use Cases
Distinguishing these terms from each other can be rather confusing. In an attempt to go back to the basics, Nadine Schaeffer explains in detail the benefits and the necessity of using realistic situations.
Get High Performance Out of Your Testing Team
Michael Hackett
Testing is often looked upon by many as an unmanageable, unpredictable, unorganized practice with little structure. It is common to hear questions or complaints from development including:
- What are test teams doing?
- Testing takes too long
- Testers have negative attitudes
Agile Retrospectives
Mark Levison
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.
Spotlight Interview with Mark Levison
Mark Levison has over twenty years experience in the IT industry, working as a developer, manager, technical lead, architect, and consultant. He discovered Agile in 2001 and is now a Certified Scrum Trainer and Agile Coach with Agile Pain Relief Consulting.
Levison has introduced Scrum, Lean and other Agile methods to a number of organizations and coaches from executive level to the individual developer and tester. Levison is also an Agile editor at InfoQ and has written dozens of articles on Agile topics and publishes a blog – Notes from a Tool User. Mark’s training benefits from his study and writing on the neuroscience of learning: Learning Best Approaches for Your Brain. To contact Mark Levison, please email him at mark@agilepainrelief.com.
Spotlight Interview with Jonathan Rasmusson
Author of The Agile Warrior, Rasmusson answers questions from LogiGear’s testing staff about test automation in agile projects.
Action Based Testing: The Solution for Agile Test Automation
To address the challenges and fears of implementing automation in agile projects, LogiGear CTO Hans Buwalda presents Action Based Testing as the answer.
Michael Hackett: Agile Automation
Agile Automation Michael Hackett – Senior Vice President – LogiGear Corporation |
Automation Tool: Automated Test and Retest (ATRT)
What is Automated Test and Retest (ATRT)?
IDT’s ATRT Test Manager addresses the complex testing challenges of mission critical systems by providing an innovative technical solution that solves the unique testing problems associated with this domain. It provides an integrated solution that can be applied across the entire testing lifecycle.
Testing in Agile Part 5: TOOLS
Michael Hackett, Senior Vice President, LogiGear Corporation
To begin this article, it would be a good idea to, remember this key point:
Agile Manifesto Value #1
Individuals and interactions over processes and tools
Tools work at the service of people. People, particularly intelligent people, can never be slaves to tools. People talking to each other, working together and solving problems is much more important than following a process or conforming to a tool. This also means someone who tells you a tool will solve your Agile problems knows nothing about Agile. A disaster for software development over the past decade has been companies investing gobs of money into “project management tools” or “test management tools” to replace, in some cases, successful practices of software development, in favor of the process the tool or tool vendor told that company was “best practice”. That made certain tool vendors rich and many software development teams unhappy.
If your team wants to be Agile, and work in line with the value outlined above, I have a couple of rules to remember when it comes to tools and Agile.
Does Agile development need specialists?