Change Requests In Agile Projects • Business Analysis Technique

แชร์
ฝัง
  • เผยแพร่เมื่อ 11 ก.ย. 2024
  • Agile software development is something that all business analysts will eventually encounter in their careers. Some organizations do a good job of implementing agile practices into their solution delivery process. Others do not.
    Agile comes with some significant drawbacks, and these drawbacks can have a big impact on how business analysts perform their duties. This video discusses one of these drawbacks.
    This video was released to our community months ago. Join us using the link below to get these community videos as they are released.
    --
    Community • bablocks.com/m...
    Courses • bablocks.com/c...
    Podcast • bablocks.com/p...
    --
    #businessanalysis #businessanalyst

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

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

    Take the first step to becoming a high-performing business analyst ⇨ bablocks.com/membership/?ref=2

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

    This is very helpful. Thank you

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

      You're very welcome.

  • @sumitmitra7336
    @sumitmitra7336 ปีที่แล้ว

    if in an Agile Project a customer makes a request for addition of a new feature in the last sprint of the release, that is nearing completion, then should the Scrum master ask the project manager to consider the request (considering Agile embraces changes) or should the scrum master assess the impact on sprints deadline along with the team members first?

    • @BABLOCKS
      @BABLOCKS  ปีที่แล้ว

      If you're lucky enough to have a project manager and a scrum master on the same project then you should notify the PM right away and ask them for direction.
      The PM is accountable for cost/schedule and may not have the budget for any additional work.
      I hope that helps.

  • @siblingworldtv1946
    @siblingworldtv1946 ปีที่แล้ว

    Isn't a change request simply a new User Story that can be added to the backlog and prioritised (just like another User Story)? The Story that was accepted must go ahead and delivered as per the normal way .. that's how I could address this situation

    • @BABLOCKS
      @BABLOCKS  ปีที่แล้ว

      It can be. This video addresses the more extreme situation where the customer is demanding a change to a feature/function that is mid-build.
      It can be very common on some projects the receive these types of requests and the developers are the ones who should be making the yes/no decision.

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

    very helpful

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

    Hello, do you actually teach the BA class? How do we register if interested? Price and course curriculum and duration? Thanks

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

      Hi, you can see a list of our courses here: bablocks.com/courses/
      The course schedule is published inside our community. You can join here if you haven't already done so: bablocks.com/membership/

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

    This video doesn't help, I am sorry.

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

      Hi Suraj,
      Do you have any follow-up questions that you'd like answered to help you understand this more clearly?

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

      @@BABLOCKS "how do you handle change requests in agile projects?" I had that question on my mind when I clicked on the video...

    • @BABLOCKS
      @BABLOCKS  3 ปีที่แล้ว +5

      1. Check with the dev team to see if they can absorb the change request into their sprint for the next release.
      2. If so, then let your customers know that the change can be accepted.
      3. If not, tell your customers that the change cannot be accepted into the current release.
      Does that clear things up?