My review of EuroSTAR 2015 - Maastrict

There are lot of great talks in EuroSTAR 2015.  I was really enjoy it, as well as the city Maastricht. Tidy, charming city with history, gourmet and exclusive shopping :)

There are a few hot words into my ears.

  • Autonomous management, self steer group. 
  • DevOps is all about communication, collaboration, transparency. 
  • Always start with WHY, follow with WHAT then HOW
  • Continuous learning is the way to survival for tester.  
  • Dedicate team, Automation in Agile. 
  • Small team with Big goal, leads to -> disruptive. 


**************************************************************************

DevOps:
  • My feel of DevOps is Collabration and Communcation.  To achieve efficiency, TA should be communication with different parities, get the needs from them ,and make the things happen. Open mind and fearless. [TU4]. 
  • Continuous Delivery means Continuous Testing, but not means Continuous Deployment [TU4].
  • Communication brings Trust [KS2]
  • from Engagement -> Excellence.-> Integration
  • Rapid roll out is a challenge to Operations, and Operations fears change. but change is good
    • C.Delivery is an auto process. 
    • build, test every change every day.
    • let the build failed fast, that is the only purpose of DevOps
    • use static analysis, autotest, manual test.

  • Use automation:
    get ROI
      get the fail fast,
              Force the collabration
              continuous improvement
              fast come result give the managment a blinky, give them the information for next step fast. 
     In DevOps everything is considered as code. 
  • Automation in DevOps needs efficient. 
    Run all automation is obviously not efficent and not necessary
    How to select the automation: maybe only those related to change is first priority to test
    how to make the schedule of test automation. 

Inline image 1





Management:

  1.  Allow to take risk and fearless is the basic spirit. [T2, TU4]. 
    1. Management should allow new thinking and allow to fail. 
    2. As the team, should be fearless. 
    3. ready to take the risk and award the risk taker, Allow to failed, 
  2. The culture give people a lot of constraints,  "It wont work" , this is not correct, the problem can be solve, and it can work. [KS2]
  3. Manager should ask Why and What...Do not ask HOW,,,give the team freedom.[KS2]
  4.  Know the people, only performance, give feedback ,ask for more..
    1. Do not make a standard team, the team will not exceptional. 
    2. feedback based on behaviors, ask the permission to give feedback
    3. sell the testing, change teh stale think, 
    4. manage give little value, give the team freedom.
    5. Have board connection, widen your awareness. 
    6. 3 important quesiton
      2. Is that always true?
      3. Is the opposite always false?
      4. Was there ever a time when that was not true?
    7. Manager do thing right, Leader doing right thing
    8. Manager is not more than make relationship
  5. People First
  6. Disruptive management
  • process blocks change, habit kills disruption
  • Automous managment.
    • Employee decide themselves, they steer themselves. 
    • new method attract talent, if do not do this, the new comer will replace you. 
    • need massive good, need massive transformative purpose, let people believe what you believe. 
    • Big is good, big is appealing
  • Do not prevent innovation. Amazon need manager write 2 pages to reject the ideas from employee. 
  • Don't own anything, when everything is under 1 roof === better performance
    • Smaller organiztion more active
    • Outsource as many as you can
    • company become smaller as outsource and automation
    • Small is a new BIG
  • Permanent job will be a dream for every one. Freelance type will be more usual. People work everywhere.
    • Skill set expired from 30 years to 5 years
    • Everyday learning for everyone. 
  • Disrupt yourself before others disrrupt you.
    •  A younger management team
    • find the white bear in your organization, join them, and lead the disruption


New Technology:
  • Mutant
    • Mutant test is not a new concept, but new easy to implement in the real test.  [TU8]
    • The problem of mutant test is about performance, the skill to select correct testcase is important.
  • Docker
    • a lightweight software container to replace the bad performance VM (Hypervisor, which translate is a bottleneck)
      docker can take snapshot in memory and storage to recover
      docker and host have to have same type of kernal, but not necessary same release. e.g. Ubuntu 64 can run Redhat64 bit docker, but cannot run Ubuntu 32 bit docker.




Test Management

  • Session based Management
    • Session based mgmt is a GAMBLING
    • LIMIT:
      • session Time, 20M to 3H
      • session scope
    • Remember there are always something you can discover. 
    • Note taking during the test, Very important
    • even debrife only take 5-10% of test time, it still a lot. use peer debrife instead. 
      • ask the feeling of tester by: ""HOW MUCH MORE TIME DO YOU NEED"" 
    • Remember: The discovery may fool you, you might not even close the truth.
  • Community
    • Traditional TM position does not fit in the DevOps world. but they will have new role.
      Coach the new tester, 
      Sell the testing, explain the value of testing
    • Community is a great experience, lean coffee concept is easy to be adopted.
      • do not incentive the community.  
    • Transferrable skill set is very useful.
  • Traditional TM is no way to work in multiple team in DevOps environment. 
  • Cross functional, autonomous, independent teams



Test Strategy and Communication

  • Test policy talks WHY, test strategy talks HOW
    • Before test: Test Strategy ,  During Test: Visualition the result for the decision , After Test: Proper test result. 
    • From Test Policy goes to Test Strategy to the Master TestPlan
    • Inline image 1
  • Always a test mission
    • WHY testing
    • WHAT information the stakeholder want to know
  • Express the quality in customer's word.  
    • Tester as a facilitator to make sure not important part is forgot to test.
    • use the words that customer understand,perform the test they care
    • pull info from customer, the customer mostly will not push to you.
    • People is always important.
    • Follow up, act on their answers. 
    • Find what is the important to test. 
  • Do the above we from context unawared -> Context Driven. 
  • Do the below we from Context driven -> Stakeholder Conversationalist
    • Think why we testing
    • Why my test strategy is good
    • what is your test and why it is important
    • how you talk about test strategy and test result
  • Out of context matrix is very dangerous
    • Be careful of False positive an false negative
  • Used visualization as information radiator
    • when something goes wrong, make a noise
    • 'A low tech testing dashboard'  

Test Mind:
  • Do not anticipate the result or success.  
  • Solve the problem by discover the problem. 
  • Focus --> Deepter    Defocus -->> Further


Comments

Post a Comment

Popular posts from this blog

Such a cold summer

I almost did not wear the t-shirt alone this summer, always have a jacket on when I went outside. Most of time the temperature is lower than 20 c-degree. Totally did not get the feeling of summer. What a pity.
Read more

My Unsolve Questions

How to reduce the admin work for tester? test Measurement, Management, Communication, Automation.  Agile: Test Might take longer time than development.  How to solve that in Agile? how to make exp test efficient in scurm. does tester be scurm master better sit with developer or tester in scrum should we can Quality advisor Automation test negitive test?
Read more

My interview questions to a company using SAFe.

What is the setup of your QA team?  What is the ratio of Test vs Developer Do you have the system layer test?  Do you have the non function test layer?  How do you divide the train, do you have plat form team, and do they have their own train? Any support work in the team` What is the good part, and what is the bad part How long does the team learn how to do PI planning.  What is the biggest challenge you meet,  Did you have any challenge when you split up the team?  Any suggestion on how to devide the team, and what is the practise in lego.  In the new setup, is it possible different team work on a same product of same feature?  BDD:  In which level do you apply the BDD, how do you use it in integration level? who responsible for design and implemented BDD? Agile: What is your product, do you have technical(platform) team, how do you make them work in the agile framework.  Special list can swap among ...
Read more