This was the opening keynote of the conference, done by Johanna Rothman (@johannarothman). Johanna was so nice to publish her slides on slideshare, find them embedded at te end of this article.
Schlagwort: feedback
QuickLinks for April 2011
Here a quick list of articles I´ve read during the last month:
QuickLinks for March 2011
Here a quick list of articles I´ve read during the last month:
Here a quick list of articles I´ve read during the last month:
- GTAC 2010: Early Test Feedback by Test Prioritisation: Slides Video
- Share your vision with you employees to empower them
- A new blog for the new year: Testing with Vision
- Testing for Bug Bucks & Breaking The Rules
- Tester’s Pedal
- Exploratory Testing or Scripted Testing: Which Comes First?
- When A Bug Isn’t Really Fixed
- Recognizing Impediments
- Things you should do to sabotage your Scrum implementation
- Test Challenge: On the first software testing team…
- The History of Software Testing
- The Cost of Retrospectives at Large Animal Games
- Agiles Management: Delegation und Authorität/ Agile Management – Authority & Delegation
- Führen ohne Macht
- New Year’s Resolutions
- On Agile Misconceptions
- Definition of Done: A Reference
- Good enough, or perfect?
- Better Testers Keep Their Plates Spinning
- Elephants in the room: seven reasons why project risks are ignored
- Daily Stand-up Variations
- How Much Influence Should Testers Have?
Here a quick list of articles I´ve read during the last month:
- When do you write a concept?: When to write a concept? For governance reasons or to cover your back? And listing alternatives: e.g. a spike or take a decision based on the team´s tacit knowledge.
- A Prototype is Worth a Thousand Lines of Code – use the right prototype to emphasize the right ideas, and elicit the right feedback.
- How we got rid of time reports
- „Imagine an airplane or nuclear power plant with a fancy monitoring system that logs all kinds of data but never actually alerts anyone when something is obviously wrong…“
- ‚There is nothing so useless as doing efficiently that which should not be done at all‘ – Peter Drucker
- „Bottom line: I don’t care exactly how many hours you work, as long as it is roughly corresponds to a full time job. I do care that you are focused, energized, and motivated when you do work. Can I trust you to handle this responsibly?“
- Lateral Tester Exercise I – Status Report Virus
- Who owns quality? – „I forget how often some companies blame testers for escaped bugs. It’s not their fault.“
- It’s All About Value – „‚Just tell us when you’ll be done with all these requirements‘ is not how to guide an Agile project, be it Kanban, Scrum, or XP. Not remotely.“
- Steps to achieve higher code quality Summary about tools & techniques how to improve quality.
- Steps to achieve even more code quality Explains different kind of code reviews.
- Work in Process Multiple parallel items as wip vs. „one at a time“
- What Agile Metrics Should We Report?
- Should Story Points Be Assigned to A Bug-Fixing Story
- Stopping the line to run with zero known defects
- I Am a Certified Scrum Coach and I Am Not Nice
- Synthesizing Test Ideas – „It is very difficult to describe the process of synthesizing test ideas. It involves a multitude of information sources, a sense of what’s important, and a dose of creativity to come up with ingenious test ideas, and effective ways to execute them.“
- Context-Free Questions for Testing
- The Phoenix Checklist
- Assumptions are the mother of all … successes.
- Shower of Appreciation – or, talking behind ones back
- Dealing with “Difficult” Co-workers
- XP Days Benelux 2010
- Updated Agile Requirements Metamodel (Enterprise Backlog Model)
During our latest book study group session some of the members of the group stated that they aren’t interested in reading the whole book, since they would not benefit from every chapter. So we decided to read the (at first sight) most interesting (looking) chapters first and then see how to go on.
So as next chapter to study and discuss, we decided on „Chapter 18, Coding and Testing“.
First of all, I have to admit, that from the title I would have expected a more technical content; I expected to see things like examples of code and unit tests, see automated tests and stuff like this, but this wasn’t the case, and at the beginning I was a bit surprised. 😉
But here we go, my notes & summary on the chapter: