Бывают преподаватели "with passion", Яна - одна из них. Время на ее лекциях просто пролетает незаметно, подача материала, примеры - всё продуманно, интересно, живо!
Awesome Lecture, Really it open my mind about Agile and Scrum and brilliant way to deliver the knowledge. Hats off Lady and heartiest thanks to the Up-loader :).
Very informative and interesting presentation. Understandable for common user. Real good examples from the life. Iana is a nice and intelligent teacher, professional. Thank you!
Brilliant and pretty, dangerous combination. Really awesome, would be lucky have a teacher like her. Nothing can get away my mind having look and listening her.
Good presentation about Agile. But before agile products were tested as well in cycles it's just there were 2-3 levels of QA. QA closest to development was testing day after day. Agree that those who didn't follow that and released buggy products but 1y earlier won on long term. Those having great product but too late, lost.
The answer is to avoid unnecessary rework. You should test, identify defects and fix (or understand) defects in iteration A before starting Iteration B. If you do overlap you might find a defect late in iteration A which breaks your functionality in iteration B. This will force you to rework Iteration B and lose time and money. Does that make sense to you?
Yes! Probably I may refine my question. Immagine you have a masterplan where you define milestone each milestone refer to a specific release of the product taht containt differnet requirement. If I wan to start rel 2 before ending rel 1. We can't use iteration to map the two relaeses. How is possible to manage multi product in scrum ? We are introducing SCRUM but we are nto ableto mange in IBM RTC these multi project concept. In these scenario parallel development is common.
One question regarding iteration. Why Agile didn't include the possibility to overlap in time iterations? The goal of overlapping is to improve process response time Thanks Giacomo
The common sense of multiple sprints and iterative development is clear. But the man-day approximation thing based on painting a house was an inopportune example. Better, I think, to keep that analogy abstract as heuristically estimated task - blobs(else folks regard the process as something like painting so many square feet of wall with so many brushes-- a horrible analogy, as in, Mythical Man Month.) I think a more accurate estimate could be based on how heavily a developer cringes/flinches when asked to develop some particular feature over some target period of time; when they finally stop looking like they are passing a kidney stone, multiply by two. As well, QA hours were made implicitely fungible with developer hours on a 1:1 basis, which is only OK if that is explicitely your model. This talk kind of reinforces my belief that Agile is partly what management wants to hear, as in, wishful thinking. The description that I found most apt is that success depends primarily on the quality of the people. And who are these stakeholders that actually prioritize what they want? The goal of stakeholders in most group efforts is to act in such a manner as to be able to deny accountability after the fact.
You can do what ever works best in your context but.....there is a conflict in your objectives (as expressed in your reply). You want to adopt a so called 'Agile' approach but your business objective is to deliver to a fixed scope on a fixed date. These two objectives are irreconcilable with a 'pure' Agile approach. I am no proponent of Agile, IMO a lot of Agile is just hacking! Hacking is fine is some contexts but it depends on the complexity of your problem.
How else would you suggest developing and testing at the necessary speed for today's marketplace? Waterfall becomes a mess of wasted time so if both don't work then where do we go from here?
Perry Thomas Well 'Waterfall' as the traditional SDLC became known when people started suggesting alternatives wasn't represented fairly at all in this presentation. End-to-end testing occurs long after component and progressive systems integration testing. Most of the world we live in was built successfully in a 'Waterfall' style. No-one in a Waterfall+V-model project would be crazy enough to sit on a huge pile of development until everything was completed. Leaving that aside, Iterative development and testing as originally intended in RUP is a strong alternative. The bottom line is if you have the right people you don't need any prescriptive methodology, and if you have the wrong people no methodology will save you.
youwhatnow In regards to SDLC, I can't agree more with: "The bottom line is if you have the right people you don't need any prescriptive methodology, and if you have the wrong people no methodology will save you."
This is how SPECTRE plan to set off a nuclear bomb in a volcano to cause an earthquake that will rupture the Fort Knox gold reserves and kill James Bond when he tries to ski away to a desirable holiday destination.
Бывают преподаватели "with passion", Яна - одна из них. Время на ее лекциях просто пролетает незаметно, подача материала, примеры - всё продуманно, интересно, живо!
jke
The more she talks, the more I want to listen. Brilliant presentation!
i watched almost 20 agile scrum videos on youtube ,but this one was the best so far..
Brilliantly explained !!!
Very good explanation of scrum for dummies. The best I`ve ever heard .
I'm just preparing for ISTQB Agile testing exam, and this video was very useful for my preparation.
I love the way she explains everything! Thank you!
22:44 Agile Software Engineering
25:50 What is Scrum / Lean Development / Extreme programming
29:10 Scrum Team
Awesome Lecture, Really it open my mind about Agile and Scrum and brilliant way to deliver the knowledge. Hats off Lady and heartiest thanks to the Up-loader :).
I went through lot of video, but this video made all my Agile concept a lot clearer. Thanks for Posting.
Very informative and interesting presentation. Understandable for common user. Real good examples from the life. Iana is a nice and intelligent teacher, professional. Thank you!
Great video, easy, clear with amazing explanation!
I love her lectures. Very nice presentation.
This was a really great lecture, thank you for posting it.
Very Good Presentation clear concise and to the point.
Brilliant and pretty, dangerous combination. Really awesome, would be lucky have a teacher like her. Nothing can get away my mind having look and listening her.
Спасибо. Отличная запись и презентация! Для новичков - То шо треба!)
Good Lecture. Thanks so much for giving the good example. This will be helpful for the new agile testers.
Very nicely presented. More clear about agile/Scrum and Sprint. Thank you.
Очень интересно и понятно.
a great and very simple to understand.. thanks alot.. helped me to understand agile ...........
GREAT PRESENTATION!!!!! Thank you
Good presentation about Agile. But before agile products were tested as well in cycles it's just there were 2-3 levels of QA. QA closest to development was testing day after day. Agree that those who didn't follow that and released buggy products but 1y earlier won on long term. Those having great product but too late, lost.
@llyena,......is that all you observed and gained all tru the lessons. Be more proactive. @Portnovschool...great n wonderful job. Kudos
Iana you are the best!!!
Best video on Agile
Good Lecture!! Thanks so much Iana :)
Awesome video... so nicely explain... very technical
Fantastic lecture!
Very good lecture delivery. Its as if I'm there in class. This really helps. Thanks
Wonderful lecture. So helpful!!
Your are absolutely right. Thanks
Really....Good one for beginners.
Documents can be a part of your requirements and be prioritized as user stories. It all depends of what the business requires
great training video.
thank you...very nice lecture..!!! Keep Posting..!!!
Thank you very much
57:00 - methodologies for determining the duration of tickets development
great video ! thank you ma'am & thank you uploader
Thanks! Its good for beginers!!
Thanks for posting!
nice explanation ..................
i love it and easy for understand thank you so much
very good Lecture on Agile...Nice,helped us.Thank U:-)
This video title is incorrect, she teaches agile methodology, not "Agile Scrum Testing methodology"
great video..........
Excellent prof. tho
Very Nice Lecture, Thanks a lot :-)
Excellent
The answer is to avoid unnecessary rework.
You should test, identify defects and fix (or understand) defects in iteration A before starting Iteration B.
If you do overlap you might find a defect late in iteration A which breaks your functionality in iteration B. This will force you to rework Iteration B and lose time and money.
Does that make sense to you?
Yes! Probably I may refine my question.
Immagine you have a masterplan where you define milestone each milestone refer to a specific release of the product taht containt differnet requirement. If I wan to start rel 2 before ending rel 1. We can't use iteration to map the two relaeses. How is possible to manage multi product in scrum ?
We are introducing SCRUM but we are nto ableto mange in IBM RTC these multi project concept. In these scenario parallel development is common.
One question regarding iteration. Why Agile didn't include the possibility to overlap in time iterations? The goal of overlapping is to improve process response time
Thanks Giacomo
@Iana Mourza --> Could you please tell how we prioritize the work??
Good course...
Awesome lecture truly helped me,... love you :)
God bless -_-
worth watching
Очень круто и очень полезно!
thanks!
awesome! kind of funny in the end! thx :)
so does the computer when you switch on auto captions.
The common sense of multiple sprints and iterative development is clear. But the man-day approximation thing based on painting a house was an inopportune example. Better, I think, to keep that analogy abstract as heuristically estimated task - blobs(else folks regard the process as something like painting so many square feet of wall with so many brushes-- a horrible analogy, as in, Mythical Man Month.) I think a more accurate estimate could be based on how heavily a developer cringes/flinches when asked to develop some particular feature over some target period of time; when they finally stop looking like they are passing a kidney stone, multiply by two. As well, QA hours were made implicitely fungible with developer hours on a 1:1 basis, which is only OK if that is explicitely your model. This talk kind of reinforces my belief that Agile is partly what management wants to hear, as in, wishful thinking. The description that I found most apt is that success depends primarily on the quality of the people. And who are these stakeholders that actually prioritize what they want? The goal of stakeholders in most group efforts is to act in such a manner as to be able to deny accountability after the fact.
Can you get the presentation file somewhere??
Можно ли прослушать этот материал на русском? Спасибо.
cool
I am not getting any sound can anyone help?
Something might be wrong with your sound drivers or your system might be on mute or may be another reason
why you are taking movie like this ..is not good..we are not able to see a board...it is really pity !!!
You can do what ever works best in your context but.....there is a conflict in your objectives (as expressed in your reply).
You want to adopt a so called 'Agile' approach but your business objective is to deliver to a fixed scope on a fixed date.
These two objectives are irreconcilable with a 'pure' Agile approach.
I am no proponent of Agile, IMO a lot of Agile is just hacking!
Hacking is fine is some contexts but it depends on the complexity of your problem.
wow...(Y)
Am I the only one who thinks these methodologies are Bs?
How else would you suggest developing and testing at the necessary speed for today's marketplace? Waterfall becomes a mess of wasted time so if both don't work then where do we go from here?
Perry Thomas
Well 'Waterfall' as the traditional SDLC became known when people started suggesting alternatives wasn't represented fairly at all in this presentation. End-to-end testing occurs long after component and progressive systems integration testing. Most of the world we live in was built successfully in a 'Waterfall' style. No-one in a Waterfall+V-model project would be crazy enough to sit on a huge pile of development until everything was completed.
Leaving that aside, Iterative development and testing as originally intended in RUP is a strong alternative. The bottom line is if you have the right people you don't need any prescriptive methodology, and if you have the wrong people no methodology will save you.
youwhatnow In regards to SDLC, I can't agree more with:
"The bottom line is if you have the right people you don't need any prescriptive methodology, and if you have the wrong people no methodology will save you."
есть на русском ?
Understandable presentation but not agile...something like water agile fall
++
hehe funny accent, but excellent skill n knowledge....
This is how SPECTRE plan to set off a nuclear bomb in a volcano to cause an earthquake that will rupture the Fort Knox gold reserves and kill James Bond when he tries to ski away to a desirable holiday destination.
youwhatnow LOL I actually read your comment in russian accent ..
Looks like you have listening problem. If go to doctor he will say you are out of focus.
Brilliantly explained !!!