I am binging your vidoes. I am writing my PMP exam tomorrow, I only discovered your channel 2 days ago and wish I had known about it sooner. I'm still learning a lot though. Thank you for your service!
I'm your fan. I'm an architect. I'll continue with your SUPER LECTURES till I'll earn my PMP Keep going God increase your knowledge as well as mine I know one we would shake hands Many thanks Nigerian
Thank you Amit, i watched all your agile videos. Very helpful, passed my PMI-ACP today with 6 AT and 1 T. Used your videos for my PMP preparation in February and passed the PMP with 2 AT and 1 T. I am now PMP and PMI-ACP certified. Thank you again, i really appreciate your help. Keep up the good work.
@@samuelquansah6390 Awesome! Yes, applying the best practices and mindset learned is also important... Hope you inspire great work ethics in your organisation 👍😊
Hi, in a small project, the PM will be the facilitator. In a large project with multiple scrum teams, Scrum Master and PM both will be facilitator. In Projects that do not use Scrum, Leads will be the facilitator. Facilitator is a role for all the leads of an agile team at all levels. So both Scrum Master and Project Manager would be facilitators.
Hi Amit, could you please explain why the sequence is different in your slide, per agile practice guide i learned, it should be Epics/Features/Stories/Tasks but in your slide it is Features comes first and then Epics.
Hi, yes features and epics and interchangeably used in multiple places in the “hierarchy”. It isn’t that big an issue because we don’t have to document it in agile projects like we do with WBS for traditional. Hence, for managing project, it’s fine either ways. For exam however, any conflict in information should be resolved in favour of what PMI issues guides say.
Hello Amit, I already took sessions through Simplielearn, and I wished I heard your sessions before signing up with them. Is it possible for you to give me a structure way of learning please? I really enjoy listning to your sessions and find them very useful.
Hi Arpita, sure. I will be more than happy to help. Please write to us at contact@edzest.org and we will set up a discussion to help you with the plan.
Hi, incase customer wants some features to add in the current sprint and says this feature is imperative must be add in current sprint, in this scenario what do the team and scrum master.
We should not add that, because if you do it once, it sets a precedence, and you'll not be able to say no in future sprints as well. Best thing is to discuss with the customer and inform why it's not a good idea to add a feature to ongoing sprint.
Hi. In Traditional Projects, the project manager is responsible for integration activities. But who is responsible in case of Agile Projects? Team or PM
Think about what do you need to integrate in Agile? In traditional, the responsibility is to bring the pieces of puzzle together as a lot of things are happening in parallel. In agile, we do things one by one and integration would mainly be towards product features only. (Not a lot of integration required). Hence, team will suggest on priorities product owner would take decisions.
Product owner prioritizes the product backlog. Team estimates the effort in Story points. Based on both the team selects user stories for the sprint - and it's called sprint backlog. Features to user stories should be done by the product owner. They can discuss with team or facilitator while doing it.
You have done super job .just a doubt is features are breakdown to epics or epics are breakdown to features.? But a wonderful and informative video.keep the good work going.
It’s the confusing part across Agile. Some people follow a practice of Feature to epics and some follow epics to feature… ultimately it doesn’t matter for a given project, and we should follow the same approach throughout the project.
No, but there are certain suggested timelines like 30 min to 45 min. The idea is that you should fix an approximate duration for these ceremonies in the beginning itself for entire project, so that everyone becomes habitual to finish the meetings on time.
Sir There is a question. The project team is analyzing its current iteration progress and reviewing the following chart. Which will be the answer. Burn up or burn down. I selected burn up but the answer is burn down. Why not burn up as it shows the completed work and can be used to calculate the velocity as well.
Hi, Sir. You explained in this lecture that if you did not complete the whole user stories in the sprint that's mean you are zero. 16/0 . My concept is not clear because you were saying incase you didn't complete the whole user stories. The remaining will back to the product back log. There will be reproitize the users stories. Then it will take to the next sprint.
Hi, the idea is to ensure that the team completes every user story they pick up and then only move to another user story. So that working product can be developed. The measurement, hence, is based on full completion of every user story. While calculating the team actual velocity, you will add story points of completed user stories, even if any user story is 90% complete, you’ll still consider it as 0 story points. And this incomplete user story will be compared with other user story in the backlog, and if it believe to still have the highest priority, only then we will complete the user story in next iteration. Otherwise, it will be completed later in the project. (The idea is that everytime you decide which user story to work on, you always take the maximum value delivering user story)
I am binging your vidoes. I am writing my PMP exam tomorrow, I only discovered your channel 2 days ago and wish I had known about it sooner. I'm still learning a lot though. Thank you for your service!
You're welcome. And all the best for your exam... 👍 You'll do well.
I'm your fan.
I'm an architect.
I'll continue with your SUPER LECTURES till
I'll earn my PMP
Keep going
God increase your knowledge as well as mine I know one we would shake hands
Many thanks
Nigerian
Thank you so much. I hope we meet soon.. all the best for your exam as well.
Thank you Amit, i watched all your agile videos. Very helpful, passed my PMI-ACP today with 6 AT and 1 T. Used your videos for my PMP preparation in February and passed the PMP with 2 AT and 1 T. I am now PMP and PMI-ACP certified. Thank you again, i really appreciate your help. Keep up the good work.
Awesome Samuel, Congratulations. Infact, double congratulations... I'm glad I was able to help in your journey.
What's next for you? :)
@@edzest want to take a break for now and focus on work. I may consider PMI-RMP later
@@samuelquansah6390 Awesome! Yes, applying the best practices and mindset learned is also important... Hope you inspire great work ethics in your organisation 👍😊
the best lecture on Agile I saw!
Thank you so much!
THANK YOU AMIT!YOU ARE SERVING ME A LOT! MAY ALLAH SERVE YOU FULLY!
Thank you for your constant encouragement
Thank You Very Murch, I appreciate for your service. God Bless you
Thank you so much 😀
The sequence is always EPIC-FEATURE-USER STORY-TASK❣
Not always, but majority of times- yes!
Thank you for the clear presentation , very useful ❤
Thanks a lot...
Amazing Presentation, thank you so much for your clear explanation.
Guilda.
You’re welcome. We are glad that you like our videos.thanks a lot for your support as well.
I can understand the effort for making this video. Keep it up. Will connect soon.
Thanks for your comment… you can reach out to us on email- contact@edzest.org
is the facilitator the Project manager or scrum master? its not clear
Hi, in a small project, the PM will be the facilitator. In a large project with multiple scrum teams, Scrum Master and PM both will be facilitator. In Projects that do not use Scrum, Leads will be the facilitator.
Facilitator is a role for all the leads of an agile team at all levels.
So both Scrum Master and Project Manager would be facilitators.
Initiation: 1:16:55
👍🏻
Hi Amit, could you please explain why the sequence is different in your slide, per agile practice guide i learned, it should be Epics/Features/Stories/Tasks but in your slide it is Features comes first and then Epics.
Hi, yes features and epics and interchangeably used in multiple places in the “hierarchy”.
It isn’t that big an issue because we don’t have to document it in agile projects like we do with WBS for traditional.
Hence, for managing project, it’s fine either ways.
For exam however, any conflict in information should be resolved in favour of what PMI issues guides say.
Thanks for sharing ...
You’re welcome.
Hello Amit, I already took sessions through Simplielearn, and I wished I heard your sessions before signing up with them. Is it possible for you to give me a structure way of learning please? I really enjoy listning to your sessions and find them very useful.
Hi Arpita, sure. I will be more than happy to help. Please write to us at contact@edzest.org and we will set up a discussion to help you with the plan.
Hi, incase customer wants some features to add in the current sprint and says this feature is imperative must be add in current sprint, in this scenario what do the team and scrum master.
We should not add that, because if you do it once, it sets a precedence, and you'll not be able to say no in future sprints as well.
Best thing is to discuss with the customer and inform why it's not a good idea to add a feature to ongoing sprint.
Hi. In Traditional Projects, the project manager is responsible for integration activities. But who is responsible in case of Agile Projects? Team or PM
Think about what do you need to integrate in Agile? In traditional, the responsibility is to bring the pieces of puzzle together as a lot of things are happening in parallel. In agile, we do things one by one and integration would mainly be towards product features only. (Not a lot of integration required). Hence, team will suggest on priorities product owner would take decisions.
I have question that while preparing of sprint backlog...Features are choosen by team or PO Direct them...
And who breakdowns the features upto user stories...
Product owner prioritizes the product backlog. Team estimates the effort in Story points.
Based on both the team selects user stories for the sprint - and it's called sprint backlog.
Features to user stories should be done by the product owner. They can discuss with team or facilitator while doing it.
You have done super job .just a doubt is features are breakdown to epics or epics are breakdown to features.? But a wonderful and informative video.keep the good work going.
It’s the confusing part across Agile. Some people follow a practice of Feature to epics and some follow epics to feature… ultimately it doesn’t matter for a given project, and we should follow the same approach throughout the project.
Thank you for your kind comments as well. Is there anything else you would like us to cover…
Sir is there any specific duration for sprint planning, sprint retrospective and sprint review?
No, but there are certain suggested timelines like 30 min to 45 min. The idea is that you should fix an approximate duration for these ceremonies in the beginning itself for entire project, so that everyone becomes habitual to finish the meetings on time.
We will prioritize feature based on higher value .... so what about risk in this case?
Value of risk will be estimated and the feature will be compared with other features.
Sir There is a question. The project team is analyzing its current iteration progress and reviewing the following chart. Which will be the answer.
Burn up or burn down.
I selected burn up but the answer is burn down.
Why not burn up as it shows the completed work and can be used to calculate the velocity as well.
Burn Up can also be used. Nothing in your question mentions only burn down should be used. You are right. 👍
@@edzest Thank you Sir 🙏
@@footballclicks6847 you're welcome
Thank you 🙏
You’re welcome!
Hi, Sir.
You explained in this lecture that if you did not complete the whole user stories in the sprint that's mean you are zero.
16/0 . My concept is not clear because you were saying incase you didn't complete the whole user stories. The remaining will back to the product back log. There will be reproitize the users stories. Then it will take to the next sprint.
Hi, the idea is to ensure that the team completes every user story they pick up and then only move to another user story. So that working product can be developed. The measurement, hence, is based on full completion of every user story.
While calculating the team actual velocity, you will add story points of completed user stories, even if any user story is 90% complete, you’ll still consider it as 0 story points. And this incomplete user story will be compared with other user story in the backlog, and if it believe to still have the highest priority, only then we will complete the user story in next iteration. Otherwise, it will be completed later in the project. (The idea is that everytime you decide which user story to work on, you always take the maximum value delivering user story)
@1:28:47 its EPICS-->FEATURES-->USER STORIES--> TASKS
👍🏻