Maintaining quality involves a blend of exploratory and automated testing. As new features are developed, exploratory testing ensures that new code meets the quality standard in a broader sense than automated tests alone. This includes ease of use, pleasing visual design, and overall usefulness of the feature in addition to the robust protections against regressions that automated testing provides.
Group items matching
in title, tags, annotations or url
Lean software development - Wikipedia - 0 views
Engineering Higher Quality Through Agile Testing Practices The Agile Coach - 1 views
-
-
Exploratory testing is a risk-based, critical thinking approach to testing that enables the person testing to use their knowledge of risks, implementation details, and the customers' needs.
-
On our development teams, QA team members pair with developers in exploratory testing, a valuable practice during development for fending off more serious bugs. Much like code review, we’ve seen testing knowledge transfer across the development team because of this. When developers become better testers, better code is delivered the first time.
http://studios.thoughtworks.com/2007/5/10/continuous-integration-in-the-enterprise-with-cruisecontrol - 0 views
-
One of the developers had checked in some code that failed the regression tests. The application, on which the company had spent considerable time, money and effort, was now in an uncertain state. It wasn't behaving as expected. In the past, this type of bug usually wasn't discovered for months. Usually, it wasn't discovered until the System Integration Testing cycle got underway. For this project, that wasn't scheduled for another 6 months.
-
In the past, this bug would have lingered in the code for 6 months before anyone even realized it was a problem
-
. The light had gone off only 6 minutes after the code had been committed. Notice: not 6 months...but 6 minutes!
- ...1 more annotation...
Continuous Integration - 0 views
-
On the whole I think the greatest and most wide ranging benefit of Continuous Integration is reduced risk. My mind still floats back to that early software project I mentioned in my first paragraph. There they were at the end (they hoped) of a long project, yet with no real idea of how long it would be before they were done.
Distributed Agile Development - 0 views
How Google Sold Its Engineers on Management - 0 views
-
A good manager: 1. Is a good coach 2. Empowers the team and does not micromanage (See the sidebar “How Google Defines One Key Behavior”) 3. Expresses interest in and concern for team members’ success and personal well-being 4. Is productive and results-oriented 5. Is a good communicator—listens and shares information 6. Helps with career development 7. Has a clear vision and strategy for the team 8. Has key technical skills that help him or her advise the team
-
Employees with high-scoring bosses consistently reported greater satisfaction in multiple areas, including innovation, work-life balance, and career development
-
high-scoring managers saw less turnover on their teams than the others did—and retention was related more strongly to manager quality than to seniority, performance, tenure, or promotions
- ...1 more annotation...
Functional Subgrouping the core method of Systems-Centered Training - developed by Y. Agazarian - YouTube - 0 views
-
Short description of facilitation tool
Lean Startup: Why it rocks far more than agile development - Joshua Kerievsky - YouTube - 0 views
-
Good intro to Lean Startup for agile practitioners