FriendlyTester/Ideas

## Ideas
So these are all the postits note I could find after the LeanBaconTeaCoffee at TestBash.
It was suggested by an attendee that these could make could help people formulate some blog ideas
so here they are!

1.	Release candidate testing
2.	Are unit checks only for programmers
3.	When does a tester become a developer
4.	Sustainable pace
5.	Ant fucking (nit picking) how picky is it OK to be with testing?
6.	Is there a way to inspire 9-5 testers?
7.	Testing with non-testers
8.	Engaging the actual business users
9.	Group testing sessions, good or bad?
10.	Overcoming tester fear, what haven’t I tested?
11.	What to do when you know that your customer is wrong?
12.	How lazy can a tester be?
13.	What do you think testers need to do to be taken seriously?
14.	Convince your boss to pay for TestBash
15.	What makes a great tester? (Recruitment)
16.	How to make PO’s get involved in testing?
17.	Best book you have read (or blog)
18.	What makes a good bug report
19.	Do we need testers on teams?
20.	Agile = Sprint vs releases?
21.	What is quality?
22.	What are the “but not us” topics you have seen
23.	Why are you here?
24.	Is automation the answer
25.	Testing certifications / conferences
26.	How to become test architects
27.	What is a Test Architect? Different from a test manager?
28.	The role of QA managers?
29.	Where does Test Manager fit in agile?
30.	Hiring testers
31.	What’s the next level for a tester?
32.	UI Testing
33.	What’s twitter all about?
34.	How do we change the mind-set of a traditional risk averse “stats” driven organisation?
35.	Testers cannot fix defects
36.	How to get people to understand defects are not the testers fault
37.	Testing tools
38.	Have only one E2E environment
39.	Automation can be dull
40.	How to get people interested in testing
41.	Should testers be involved in setting up build infrastructure
42.	Automation vs sprint commitment, agile sprint
43.	What kind of things are you testing
44.	How to involve manual testers in automation
45.	What testing means to you?
46.	When is enough to stop testing?
47.	Enough documentation in agile?
48.	What skills do you need in an agile test team?
49.	Are testers afraid to test for security?
50.	Are dev only teams better?
51.	Does testing happen in self organising teams?
52.	How to ensure that PO does not push automation to the end?
53.	What/Which activities do you like the most in the development cycle?
54.	Is Scrum agile?
55.	Evangelist Dysfunction
56.	Where’s the value in testing?
57.	Tester > TM > Then what?
58.	The companies 1st tester
59.	Eliminating the pen & paper in test documentation
60.	Burnout
61.	Reporting what you haven’t tested
62.	What part of your job gives you the most satisfaction?
63.	QA squeezed to the end of the sprint execution
64.	What to do when the project has inertia
65.	 What do you do when you have tester a feature, how do you know its “fully” tested
66.	Massive Bug Databases – Why create these, are they useful?
	So these are all the postits note I could find after the LeanBaconTeaCoffee at TestBash.
	It was suggested by an attendee that these could make could help people formulate some blog ideas
	so here they are!

	1. Release candidate testing
	2. Are unit checks only for programmers
	3. When does a tester become a developer
	4. Sustainable pace
	5. Ant fucking (nit picking) how picky is it OK to be with testing?
	6. Is there a way to inspire 9-5 testers?
	7. Testing with non-testers
	8. Engaging the actual business users
	9. Group testing sessions, good or bad?
	10. Overcoming tester fear, what haven’t I tested?
	11. What to do when you know that your customer is wrong?
	12. How lazy can a tester be?
	13. What do you think testers need to do to be taken seriously?
	14. Convince your boss to pay for TestBash
	15. What makes a great tester? (Recruitment)
	16. How to make PO’s get involved in testing?
	17. Best book you have read (or blog)
	18. What makes a good bug report
	19. Do we need testers on teams?
	20. Agile = Sprint vs releases?
	21. What is quality?
	22. What are the “but not us” topics you have seen
	23. Why are you here?
	24. Is automation the answer
	25. Testing certifications / conferences
	26. How to become test architects
	27. What is a Test Architect? Different from a test manager?
	28. The role of QA managers?
	29. Where does Test Manager fit in agile?
	30. Hiring testers
	31. What’s the next level for a tester?
	32. UI Testing
	33. What’s twitter all about?
	34. How do we change the mind-set of a traditional risk averse “stats” driven organisation?
	35. Testers cannot fix defects
	36. How to get people to understand defects are not the testers fault
	37. Testing tools
	38. Have only one E2E environment
	39. Automation can be dull
	40. How to get people interested in testing
	41. Should testers be involved in setting up build infrastructure
	42. Automation vs sprint commitment, agile sprint
	43. What kind of things are you testing
	44. How to involve manual testers in automation
	45. What testing means to you?
	46. When is enough to stop testing?
	47. Enough documentation in agile?
	48. What skills do you need in an agile test team?
	49. Are testers afraid to test for security?
	50. Are dev only teams better?
	51. Does testing happen in self organising teams?
	52. How to ensure that PO does not push automation to the end?
	53. What/Which activities do you like the most in the development cycle?
	54. Is Scrum agile?
	55. Evangelist Dysfunction
	56. Where’s the value in testing?
	57. Tester > TM > Then what?
	58. The companies 1st tester
	59. Eliminating the pen & paper in test documentation
	60. Burnout
	61. Reporting what you haven’t tested
	62. What part of your job gives you the most satisfaction?
	63. QA squeezed to the end of the sprint execution
	64. What to do when the project has inertia
	65. What do you do when you have tester a feature, how do you know its “fully” tested
	66. Massive Bug Databases – Why create these, are they useful?