I'm accustomed to relatively rigid defect reporting, something like this.
Steps to reproduce: 1. Access customer manager for user Test01 2. Check "User must change password" and click Apply 3. Access login page 4. Enter user name and password 5. Click Login Expected results: 6. Site displays user profile page (see use case 21.1.2) Actual results: 6. Site displays error page (see attached screen shot)
I recently joined an Agile project where the defect reports look more like this:
Can't sign on with user Test01, see screenshots
In my many years of development experience, I've found that the longer defect reports serve numerous purposes, e.g. it succinctly communicated the precise problem and avoids any sort of judgmental language, and clearly represents the defect as a departure from a required behavior, rather than allowing the QA engineer to make up defects for behaviors that "seem" wrong.
Agile methodology de-emphasizes the importance of documentation. Instead we're encouraged to pick up the phone and talk to each other.
Is this a valid application of Agile principles? Or should defect reports be fairly verbose even when we're trying to be agile?