How to estimate Testing efforts in an Agile Project?

แชร์
ฝัง
  • เผยแพร่เมื่อ 16 พ.ย. 2024

ความคิดเห็น • 13

  • @AtulSharma-cm9eh
    @AtulSharma-cm9eh 4 ปีที่แล้ว +2

    I love the way you explain the things. You have that influential attribute.

  • @santoshkumar2712
    @santoshkumar2712 3 ปีที่แล้ว +1

    great work Saket

  • @snigshine4481
    @snigshine4481 2 ปีที่แล้ว

    Hi can you please help me with below query
    Can we consider 1 story point =4 hr
    2 SP =8 hr and 3SP =16 hrs

    • @izenbridge
      @izenbridge  2 ปีที่แล้ว

      Complicated question, may this video help th-cam.com/video/3fjQDN83Pgc/w-d-xo.html

  • @prateekwatwale4812
    @prateekwatwale4812 2 ปีที่แล้ว

    For a user story, dev efforts are only understand by devs and qa efforts by only testers, in such scenario, how do we go about estimating correctly as members would be looking at the effort from their point of view, dev may say 8 SP and qa may say 3 then how do we discuss and reach a common ground

    • @izenbridge
      @izenbridge  2 ปีที่แล้ว

      That is something agile expects to team to resolve and come up with the joint number which takes care of all what it takes to get the work done. So no formula, but team need to discuss and agree on one number for a story.

  • @reubenstephen1721
    @reubenstephen1721 3 ปีที่แล้ว

    What is the ideal size of a Scrum team ? For instance, for members over 8, the scrum stand up will definitely not be done in 15 mins as recommended but will generally take about 45 mins on an average across the SDLC.

    • @AtulSharma-cm9eh
      @AtulSharma-cm9eh 3 ปีที่แล้ว +1

      45 minutes is too long for Stand Up meeting. Stand-up duration is kept of 15 minutes because there shouldn't be too much detailed discussion in that meeting, that's why the name is "Stand-up". People will get tired of standing up for long period and try to close the meeting within the defined timebox. Just encourage team members to have "quick" updates on their work and do a meet-after for detailed discussions, that too with concerned people only. Hope that helps.

    • @AtulSharma-cm9eh
      @AtulSharma-cm9eh 3 ปีที่แล้ว

      ++ Ideal size recommended is 6-9 members.

  • @vijaykumar-ut1ze
    @vijaykumar-ut1ze 3 ปีที่แล้ว

    One doubt
    If the story involves only dev task no need of testing effort then as per ur sentence it's the summation of dev plus qa

    • @izenbridge
      @izenbridge  3 ปีที่แล้ว

      Yes, so all work we need to mark the story done , and Done is defined in Definition of Done