Home

 

Siteindex for shalimatech.com

Home

Recipes

  1. Lobster
  2. Stuffed muscles
  3. Fish curry

Software testing

  1. HP Loadrunner
  2. Load Balancing
  3. Performance testing vs Load testing vs Stress testing
  4. Virtual user generator
  5. QTP
  6. QTP smart identification
  7. QTP parameterization
  8. QTP- recovery scenarios
  9. Jmeter
  10. Jmeter Installation
  11. Jmeter – script recording
  12. Selenium-Cucumber
  13. HTML

Blog

  1. Trending news
  2. QTP
  3. Hub and Node
  4. IPL 2017
  5. QTP and SQL Server
  6. QTP and MS access
  7. Headless Webbrowser
  8. QTP String reverse
  9. qtp-program-display-odd-even-numbers
  10. cloud-computing
  11. jenkins
  12. web-server-vs-application-server-vs-database-server
  13. distributed-systemssoftware
  14. correlation
  15. rendezvous-point
  16. loadrunner-components
  17. html-5-sample-code
  18. html5-apis
  19. pepper-chicken
  20. some-of-the-http-status-codes
  21. load-balancing
  22. Salesforce
  23. MDM Mobile
  24. customer-success-manager-csm
  25. software-as-a-service-saas
  26. service-oriented-architecture-soa
  27. firebase
  28. apache-ambari
  29. apache-spark
  30. apache-cassandra
  31. apache-mahout
  32. apache-oozie
  33. hadoop-sqoop
  34. hadoop-pivotal-hd
  35. hadoop-zookeeper
  36. hadoop-cloudera
  37. pig-hive-in-hadoop

Recipes

  1. Lobster
  2. Stuffed muscles
  3. Fish curry

Software testing

  1. HP Loadrunner
  2. Load Balancing
  3. Performance testing vs Load testing vs Stress testing
  4. Virtual user generator
  5. QTP
  6. QTP smart identification
  7. QTP parameterization
  8. QTP- recovery scenarios
  9. Jmeter
  10. Jmeter Installation
  11. Jmeter – script recording
  12. Selenium-Cucumber
  13. HTML

Disclaimer

About Us

Sample post – Scrum practical example

Scrum practical example that can get easily implemented in any IT industry. Scrum is effective and best way to run any complicated project. Real world scenario on scrum

Assume company has 10 products and 5 product owners.

Each product owner is responsible for 2 products.

Every sprint is planned for  2 weeks (10 days in this e.g. not 28 days)

Monday of first week  Sprint planning session for entire day

Product owner explains 2 high level requirements from his product backlog. Scrum team (scrum master, Dev , SQA, implementation, DB team) reviews this and break down into many user stories.

Tuesday onwards, daily 1 meeting i.e stand up call happens and in that people says what I achieved so far, what is planning for today. And what are the main issues which are blocking me.

If any Stand up call produce any shippable product, that can be planned to move to production immediately. Sometimes Sprint review with all interested parties may occur.

If both of the requirements are fulfilled by covering all user stories , then next spring planning session can happen on following day to add new requirements.

If any one of the requirement can not be fulfilled in 1st sprint and that was found out during Sprint review or subsequent stand up call, product owner can put that requirement back to Product backlog.

Scrum is a framework for Agile testing. Some companies uses scrum for innovation process as well where employees only creates the product backlog and start working for it. the product backlog and start working for it.

Leave a Reply

Your email address will not be published. Required fields are marked *