Комментарии:
Thank you, Thank you for your video. Very helpful
ОтветитьCan you stop kissing your lips when you talk? It’s so irritating 😠
ОтветитьNice!
ОтветитьExcellent 3 mins thank you 🌹
ОтветитьHahae so good
ОтветитьWell, I thought that I had enough requirements listed to get started on a few scrum sprints. Within a week I had a working prototype. What I didn't realize or make clear was that the department chief thought that was it. Done. In one week!!!!?? I guess she thought I was able to do waterfall method in 1 week. But here we are 5 weeks after the first meeting and every week i've sent screenshots and change logs for her to look at. Telling her to open the browser and look at the product and test it out. I would get feed back like "this is awesome!" and "you're a genius!" Finally here we are week 6 and while in her office I get her to open it up in a browser and look at it. What does she say? "This is all wrong. This won't work at all." I didn't call her out and say "but I sent you screenshots." Instead I said, "ok no problem we can fix it and it's better that you caught this now rather than 3 months from now." Lesson learned: don't even start scrum until you are 10000% clear on all the business requirements and maybe even don't start the next sprint until you get a face-to-face meeting to discuss progress. Otherwise you will get emails like "you're a genius!" but really they never looked at your prototype and you keep working several sprints into a project before they finally LOOK at the prototype. Ridiculous!
ОтветитьPlease do a video from the perspective of, say, starting a new agile team: developers, QA, product owner, business analyst and scrum master. Then show what should happen first. May be there is a meeting first with the upper management and BA or a project manager (is there a PM in scrum team? or he/she works outside the scrum team) to chart out the project/scope etc. Show what each team member will do and at what stage.
I thought the backlog was created by both PO and the scrum master. I may be wrong. I am new to agile. I worked as a QA in agile environment for few months. I loved it. As I wanted to see how things are done from the scratch. I did not get the full picture. The product owner was the one creating/prioritizing backlog items and the sprint team would pick out the ones to work on for that sprint. Now this is 10 years ago. I am sure things have changed since then.
Good one Angelo. You were direct and glad you did not say like a few that BA and PO both can exist ..Yes .And BA needs to be Product Owner taking decisions. BA always does requirements priorities using age old DSDM techniques, he just have to break and group as independent, verifiable, negotiable, investable and testable blocks ..that's it BA us a new PO...
ОтветитьThanks man...that was so informative...I just have a confusion,Do we make analysis and design once in the life time of the project? or as Agile states: Don't make big designs that do not allow change. As Agile allow Dynamic change during project life time.
ОтветитьThis is very good and relevant.
ОтветитьBrilliant mate, thank you. Loved your training format and engaging voice, very smart, very clear, very thankful.
ОтветитьInteresting! Thx.
ОтветитьVery nice! Thanks for such detailed explanation. Your video helped me a lot understand BA's role in an Agile environment.
ОтветитьVery good and thank you.
ОтветитьI needed that visual explanation.. thank you. All the way from Denmark :)
ОтветитьThank you!
Ответить