O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.

Testing world seen through the thick lens of a business analyst

773 visualizações

Publicada em

Publicada em: Tecnologia, Negócios
  • Seja o primeiro a comentar

  • Seja a primeira pessoa a gostar disto

Testing world seen through the thick lens of a business analyst

  1. 1. Testing world seen through the thick lens of a business analyst Test Camp Iasi, November 16th 2013 Anca Gafiteanu Gabi Rotaru
  2. 2. Agenda Unicredit Business Integrated Solutions Testing department in my eyes IT factory Road Map Project challenges Functional specifications Presentation meetings Contact the business analyst Summary 4
  3. 3. UniCredit Business Integrated Solutions GERMANY CZECH REPUBLIC UK POLAND A community of 11 000 colleagues 11 Countries* SLOVAKIA HUNGARY ITALY ROMANIA AUSTRIA IASI 300 people OUR TEAM  40 people  managing the integration of applications;  sustaining front-end solutions for the  redesigning the corporate and retail eBanking platform for 7 UniCredit banks; components of the eBanking platform. 5 *UniCredit Business Integrated Solutions operates also in 2 additional branches, New York and Singapore
  4. 4. Testing department in my eyes  peaceful and quiet working place  taking one task after another  time and material activity  why is this guy bothering me with questions while I’m working on my task?  having difficulties passing through people on the way to the bathroom  taking the time to plan a barbecue in weekend  party in clubs on weekdays is always a good idea 6
  5. 5. IT factory How do you feel at work?  Third employee on the second row  Groundbreaking haute couture designer OR Flash news: IT industry is all about designing! 7
  6. 6. IT factory (cont.)  if you feel like in a factory, you’d better look around;  exciting new things are flying all around your working place;  if you’re not feeling yourself as a part of it, maybe you should update your CV. 8
  7. 7. Road map Building the product road map  Almighty business department  Customizations and nice-to-have items The business analyst often finds himself in the damage control area. 9
  8. 8. Road map (cont.)  apply latest market trends;  use current projects to drive to a better product;  harmonize road map with the current features. 10
  9. 9. Project challenges I bet you know this joke! Have you ever wondered why is it happening so often? 11
  10. 10. Project challenges (cont.)  communication  personal touch  devil is in the details  customer product knowledge  handle all case scenarios 12
  11. 11. Functional specifications How do you look at the functional specifications document?  Good foundation, let’s build on top of it!  Believe and don’t doubt! OR There is no such thing as perfect functional specification document! 13
  12. 12. Functional specifications (cont.)  translate customer requirements to product terminology;  make sure the related current status is deeply analyzed and understood;  expose the proposed changes into easy-to-understand phrases. 14
  13. 13. Presentation meetings Why do we need presentation meetings?  It’s easier to pass the information  Brainstorming on the proposed solution OR Put your mark on the product! 15
  14. 14. Presentation meetings (cont.)  the business analyst is mainly a meeting mediator;  the idea is to gather (almost) immediate feedback from all the participants;  you are there to offer suggestions and remarks;  “we already thought about it, but…” answer is not a failure;  large number of action items makes the business analyst happy  insist on receiving a proper explanation for turning down your suggestion;  you should broadcast to others where needed. 16
  15. 15. Contact the business analyst Not my favorite email layout 17
  16. 16. Contact the business analyst Checklist:  ID and description of your current task;  if first contact, state your name / department / area;  state high importance and/or urgency;  always quote the functional specifications document;  high level presentation of the problem;  case scenario steps;  avoid sending log files and/or audit logs;  avoid idle times. 18
  17. 17. Summary Approach the business analyst if:  you do not understand the business model / customer requirements;  some related current status functionalities are not present in the document;  the proposed change does not fit the customer requirements;  it will be very difficult for the operator to use the new features;  it will be very difficult for the customer’s end-users to understand the new features. 19
  18. 18. Thank you! 20