Your teaching style is a top notch.....I love the fact that you keep it original 👌
@ashwingphusey Жыл бұрын
I like the way you speak, i can listen you whole day.
@lydiaogun4162 жыл бұрын
You are so brilliant with your explanations💯💯💯. Thank you very much Karaleise 👏👏👏💞💞😙😙
@penny.ventures4 жыл бұрын
this is the most exciting video of agile, I never thought i'd see the day. Thank you girl, im subbed
@karaleise4 жыл бұрын
Thanks Penny! I appreciate it!
@danieldonkoh26983 жыл бұрын
Brilliant explanation...and also riveting. Thanks
@phiyikuauta28953 жыл бұрын
Hi Kara, I just want to say I looove you!!!! ❤❤❤ I just stumbled on your channel and I have been binge watching your videos. Thank you so much for the great content. Love your personality!!! You are 💯💯💯💯💯🔥🔥🔥🔥🔥!!!😁😁 Thank you!!!
@karaleise3 жыл бұрын
Awww! Thank you Phiyiku!!!! I appreciate it!❤❤ Be sure to sign up to my mailing list on karaleise.com!
@phiyikuauta28953 жыл бұрын
@@karaleise I definitely will. Thank you! ❤
@mariomorency80344 жыл бұрын
Great info, thanks so much for sharing
@coolrelaxed19824 жыл бұрын
Glad to have you back
@ifeajumobi76064 жыл бұрын
Thanks for always making it interesting
@blessing5952 Жыл бұрын
I have just recently joined a project and replaced the new BA. It seems the product owner and dev team wrote out the user stories some time ago and the PO also validates them on the storyboard as they are assigned to her. Is that the norm? The PO seems to be doing everything. I am not complaining at all. As a fairly new BA (which this team aren’t aware of), it gives me the opportunity to observe, I just don’t want to get into a false sense of security with future projects or look useless. I keep thinking why am I here. In the standups I have nothing to input so only listen, but know I will be required for testing. They are on sprint 89 (very far) so I stay silent during planning and retrospective so as to not hold them back by asking questions as opposed to making suggestions. It’s awkward because the project is in flight and I naturally want to add value, but friends outside of work keep telling me not to overthink it & if they need me they will ask. What is the rule of thumb here? I am really looking forward to your response as I know this is a safer environment than asking colleagues who might use you for gossip
@karaleise Жыл бұрын
Thanks for watching and great question! Your team is doing what they are used to doing before you joined because the project is in flight. They do not yet know you well enough to hand things over to you. You must earn this trust. They cannot stop to cater to you right now, doesn’t mean you cannot help. You can take ownership of something small first and deliver on that - and they will start to include you more. First setup meetings with the PO and ask questions you may not want to ask in the bigger forum- ask what features you can help write stories for if any? Ask about timelines - if they are close to the end ask about plans for UAT and how you can help, do they need follow up with any stakeholders? - offer to do that. Are there any action items from the refinement sessions? offer to help with that. Do not be a BA that does nothing and says nothing. You must create a space for yourself - find a BA task to own and do your best at it!
@preciouschilemevictor79744 жыл бұрын
Glad i stumbled into you
@AceHardy4 жыл бұрын
🙏
@Newmanidentity2 жыл бұрын
🤣....Never really saw this side of you.. so fun!
@eziomaiwuh6494 жыл бұрын
I would like to know if a BA needs to update her documents every time there is a slight change in design like you gave an example with the slider?
@karaleise4 жыл бұрын
Hi Ezioma, thanks for checking out the video! Ideally your requirements should not be so closely tied to the design to require you to update it everytime a design element changes. In the slider example the requirement would be something like: "The user must be able to select xxx". The mockup can have the slider, if there is a change to use a droplist instead, then all you would need to update is the mockup not the requirement itself. In some cases the developer can have the freedom to choose how best to meet the requirement. BAs should focus on WHAT to build not on HOW to build it. Hope that helps! Please subscribe!😁👌
@eziomaiwuh6494 жыл бұрын
Thanks @@karaleise . I have subscribed and had been binge-watching your videos for the past 24 hrs. Great content. Do you have a video on which stakeholders (product manager, developers, executive management, QA, etc) uses which documents?