My Hair Is Blue
3:49
Жыл бұрын
Project Manager vs Scrum Team 🤔
17:54
Пікірлер
@riyaska4951
@riyaska4951 26 күн бұрын
Why there is not new videos?
@wrecktanglin5126
@wrecktanglin5126 Ай бұрын
It would be great if you made a playlist of all the videos referenced in this video for mobile users
@rameshtr894
@rameshtr894 Ай бұрын
Good
@86arkray
@86arkray Ай бұрын
Thanks!
@ZbigniewCzerwonka
@ZbigniewCzerwonka 2 ай бұрын
Hi Joshua, thanks for this contet - I found it great! 2 issue and 1 question: - Issue: product canvas link does not work for me :( - I remember the old video you created "How to create a Product Goal", it was about Covid vaccine - I remember it made a great job for me, do you have it somewhere? - Question: you mention the best Product Goals are created by Scrum Team themselves - does it mean, that Scrum Team is self founded? I can't say I don't agree but somehow I think it shall be more PO collaborating with rest of Organisation to craft the Product Goal... If you repaly all 3 I own you a coffee :)
@franzbartolome6201
@franzbartolome6201 3 ай бұрын
The Sprint Planning is not just attended by the Scrum Team. Sprint Planning includes the stakeholders and anyone who can add advice and help. 3:51
@aryamainkar
@aryamainkar 3 ай бұрын
Such an amazing explanation
@86arkray
@86arkray 3 ай бұрын
Awesome coach
@gatradatra9475
@gatradatra9475 3 ай бұрын
bahas tentang sistem analis dong omm
@gatradatra9475
@gatradatra9475 3 ай бұрын
pean jowo yo? enek medok e
@czarcoma
@czarcoma 4 ай бұрын
That Is Sad 😢
@barabjornsvartsson
@barabjornsvartsson 4 ай бұрын
straight to the point and very concise leaving no room for doubt !!! new subscriber
@user-rt5ox9jg6z
@user-rt5ox9jg6z 5 ай бұрын
Amazing explanation. Thanks to your awesome I finally understood how to use the Jira Control Chart. Very Powerful tool.
@Steghetta
@Steghetta 5 ай бұрын
LOVE this. Any way you could share that template with the community?
@shadyworld1
@shadyworld1 5 ай бұрын
Totally underrated Gems here ❤ Big fan already
@Sina-sd6qp
@Sina-sd6qp 5 ай бұрын
windy in the background
@MoonlightSonata160
@MoonlightSonata160 6 ай бұрын
thank you for the great explanation! but could you also mention the sources in your video in the description as well? it would be easier to check it out and not have to go through the video again
@user-rt5ox9jg6z
@user-rt5ox9jg6z 6 ай бұрын
Joeshua, many thanks for this video. I will use this content to convince my company to define a Product Goal and Product Vision. I can't download the information, I think the link is not working anymore. Can you help me?
@olowoporoku1000
@olowoporoku1000 6 ай бұрын
I wish you also added product strategy
@gschiavello
@gschiavello 6 ай бұрын
Congratulations! Very clear!
@gschiavello
@gschiavello 6 ай бұрын
Great Video! Great Trainer!!!
@stekl.h
@stekl.h 7 ай бұрын
Sometimes you watch a video and it has the "aha" moment. For me, this video had several of them. Thank you, Joshua :)
@scrummasterinblack
@scrummasterinblack 7 ай бұрын
Thank you for the kind words 🙏
@rafaelleto152
@rafaelleto152 8 ай бұрын
Amazing work!! Helped me internalize Scrum’s main points
@scrummasterinblack
@scrummasterinblack 8 ай бұрын
Glad to hear that @rafaelleto152
@om-qz7kp
@om-qz7kp 8 ай бұрын
Mmm, not convinced
@scrummasterinblack
@scrummasterinblack 8 ай бұрын
Mmmh. How come?
@om-qz7kp
@om-qz7kp 8 ай бұрын
@@scrummasterinblack not sure the product owner is always involved with all the activities you mentioned, especially the financial side. I would be expecting the PO to be more on getting the right thing done and the financials sorted by the product manager. But this based on my experience, on non-software products. Thx for checking the comment anyway.
@scrummasterinblack
@scrummasterinblack 8 ай бұрын
@@om-qz7kp in a company, which do you think is higher, company owner or company manager?
@om-qz7kp
@om-qz7kp 8 ай бұрын
@@scrummasterinblack to be honest, I do not think this is a good parallel. But I ll tell you my opinion. The company owner is not a ceo or a salesman, despite being higher in the hierarchy. The company manager will take all the executive / operative decisions. The product owner is a role within scrum with specific tasks, 100% engaging with the stakeholders but some of the tasks he does in your video are actually product manager's, at least in the companies I ve seen so far. I am not saying its wrong but I haven't heard of this or seen this before. Again thanks for engaging in a conversation on this topic! Really appreciated!
@scrummasterinblack
@scrummasterinblack 8 ай бұрын
@@om-qz7kp It also depends on which school of thoughts the company adopted. In Scrum.org school of thoughts, the Product Owner is like the company owner, spending more time on strategies for the product and can delegate tactical activities to others.
@baertheblader9402
@baertheblader9402 8 ай бұрын
Hi. Just commenting to check in on you. I’ve been enjoying your videos and noticed that it has been some time since your last upload. Just curious if you are still actively working on this channel or if you have moved on to other things. Thanks.
@sakshisrivastava5959
@sakshisrivastava5959 9 ай бұрын
It was very helpful A big like for your video!
@scrummasterinblack
@scrummasterinblack 9 ай бұрын
Thanks for watching.
@gitabuana4425
@gitabuana4425 9 ай бұрын
Love this channel ❤
@scrummasterinblack
@scrummasterinblack 9 ай бұрын
🙏
@saschad.6209
@saschad.6209 10 ай бұрын
At first, I want to say, I love your channel. Your content is stunning. When I got it right, you said that the Product goals should be defined step by step by the Scrum Team. But I thought, that I would need the Product Goals to set up a roadmap. How I set up the Roadmap without predefined Product Goals? And without Roadmap of cause, the stakeholder don't see the path we want to go. Kind Regards Sascha
@scrummasterinblack
@scrummasterinblack 10 ай бұрын
Hi Sascha. Thanks for stopping by. Yes you create the roadmap based on the product goal that has been collaboratively defined by the whole Scrum team.
@saschad.6209
@saschad.6209 10 ай бұрын
@@scrummasterinblack Hi thanks for the feedback! But when I orientate my roadmap "along the Product Goals" toward the Product Vision, I need at least to predefine the Product Goals upfront, right? How does it works when you come up with the goals step by step? Kind regards Sascha
@scrummasterinblack
@scrummasterinblack 10 ай бұрын
Sorry. I don't understand what you mean. After you created your product goal step by step, then you create your product roadmap.
@scrummasterinblack
@scrummasterinblack 10 ай бұрын
@@saschad.6209 yes. After you create the product vision, you create the product goals oriented towards that product vision.
@rejekiramadhan
@rejekiramadhan 10 ай бұрын
Halo Permisi Pak Jo izin konsultasi, dari contoh template sprint goal Anda ada kalimat "this will be validated..." hal ini susah dilakukan oleh tim kami karena sering kali scrum tim saya berhasil merilis increment ketika h-1 dan bahkan hari terakhir sprint. sehingga data analytic-nya belum muncul. apakah hal ini bisa dibilang tim kami berhasil meraih sprint goal? dan apakah next sprint bisa langung kami mulai dengan sprint goal baru sambil scrum team memantau metric dari sprint goal sebelumnya? solusi yang saat ini saya coba terapkan adalah memastikan developer tidak mengambil backlog >= capacity mereka sehingga ada waktu bagi mereka untuk melakukan backlog refinement untuk next sprint dan memvalidasi outcome metric dengan metode usability testing (saya pinjam dari ilmu UXR)
@scrummasterinblack
@scrummasterinblack 10 ай бұрын
Kalau baru rilis H-1 dan angka outcome belum keluar ya tentunya Sprint goal belum tercapai. Coba pakai Sprint yang lebih panjang (mis. 3 minggu / 1 bulan) dan pada saat Sprint Planning timnya juga harus mempertimbangkan pekerjaan untuk validasi juga bukan sekedar mengejar jumlah product backlog yang harus dikerjakan. Jangan rilis H-1. Timnya juga harus mulai belajar teknik-teknik DevOps dan continuous delivery agar bisa rilis beberapa kali dalam satu Sprint.
@rejekiramadhan
@rejekiramadhan 10 ай бұрын
@@scrummasterinblack Halo pak Jo saya mau berkabar outcome dari video yang Anda buat, saya sudah coach C level untuk sprint planning dan sprint review yang lebih outcome oriented dan mereka setuju untuk memperpanjang sprint length, terima kasih banyak atas inspirasinya selama bertahun2, terus ngonten dan selalu sehat ya pak! ga sabar mau ikut kelas PSM 2 di Jakarta
@mahattadinata2404
@mahattadinata2404 10 ай бұрын
Mantab.
@userg-v2r
@userg-v2r 10 ай бұрын
In the product goal example I see four lines which look like four objectives. Shouldn't the product goal contain a single objective?
@scrummasterinblack
@scrummasterinblack 10 ай бұрын
The four lines are the measurable metrics for achieving the single objective 😉
@BeyondBorders00
@BeyondBorders00 10 ай бұрын
This was an awesome explanation. Just subscribed and turned on alerts
@scrummasterinblack
@scrummasterinblack 10 ай бұрын
Thank you for the support 🙏
@jprodriguezjaen
@jprodriguezjaen 10 ай бұрын
I agree with your approach of using outcomes for our sprint goals, but If we use outcomes as sprint goals that means the success of the sprint will be measure just after the outputs have been used by the user or our consumer. Only at this time we will know if the results or effects have been met. In that sense, how we know the goal has been met? Thanks! great video!.
@scrummasterinblack
@scrummasterinblack 10 ай бұрын
There’s quite a few devops techniques to support it, like feature flag or canary release. Another thing, some teams use 1 month Sprint to ensure they can meet the outcome in one Sprint.
@FahadAli-uf3qw
@FahadAli-uf3qw 11 ай бұрын
I agree. Well said
@scrummasterinblack
@scrummasterinblack 11 ай бұрын
🙏
@ardianpramanta704
@ardianpramanta704 11 ай бұрын
Hi Joshua, Greeting from Indonesia. Excellent video!! Wish that this video reach high managements and create better world. How we can do agile, if developers are different entity (outsourced, contracted), they develop their own product and may have different goal than us?
@adriantotejokusumo3124
@adriantotejokusumo3124 11 ай бұрын
hi Joshua, awesome explanation! Btw I have two questions, 1. Do you think nexus daily scrum to be done after team daily scrum or the other way around? and if there is a preferable order, what is the reason? I think based on the "Nexus Guide" : "Each Scrum Team’s Daily Scrum complements the Nexus Daily Scrum by creating plans for the day, focused primarily on addressing the integration issues raised during the Nexus Daily Scrum" It should be before right? 2. What is the preferable approach if we basically have multiple products and multiple scrum teams? Multiple nexus teams? And how if there are still some dependencies between those nexus teams? Thanks
@scrummasterinblack
@scrummasterinblack 11 ай бұрын
Hi Adrian. 1. The Nexus Daily Scrum is held after the Daily Scrum as it requires delegates from each teams to bring obstacles from their team in relation to integration. 2. If you have multiple products that are dependent, you may want to reconsider the product structure as such the dependencies are non-existent or give access to each teams to the source code of components that they depend on. Amazon and Netflix does this. HTH.
@adriantotejokusumo3124
@adriantotejokusumo3124 11 ай бұрын
Thanks Joshua for the clear explanation 🙏🙏
@damianrybinski7386
@damianrybinski7386 11 ай бұрын
Thanks for this video Joshua! :)
@scrummasterinblack
@scrummasterinblack 11 ай бұрын
You’re welcome. Thanks for watching 🙏
@user-xk6eb6xr5n
@user-xk6eb6xr5n 11 ай бұрын
great
@terrancejenkins2204
@terrancejenkins2204 Жыл бұрын
Your videos are excellent! I’m currently enrolled in a scrum certification course and I’m thinking about getting the product owner certification as well. Very well explained and entertaining!
@scrummasterinblack
@scrummasterinblack Жыл бұрын
Thank you for the kind words. All the best for your future endeavours 🙌
@PEACE_LUVR
@PEACE_LUVR Жыл бұрын
I remember you had a video of Scrum Master and different stances he/she takes depending upon the situation. I can’t find that anymore. I wanted to refer an agile coach to that one….was that got removed?
@scrummasterinblack
@scrummasterinblack Жыл бұрын
Hi. Here is the video kzfaq.info/get/bejne/o7efa72p2LKWeoU.html HTH.
@PEACE_LUVR
@PEACE_LUVR Жыл бұрын
@@scrummasterinblack thank you!!!
@PEACE_LUVR
@PEACE_LUVR Жыл бұрын
@@scrummasterinblack if my memory serves right, there was one video in which you show the 4 dimensions on black board…coach, mentor, facilitator and one more*. Did you remove that one and replaced with this one? The one I am referring was pretty old (at least 2 years ago)
@gertjano.v.3664
@gertjano.v.3664 Жыл бұрын
Nice video! Refinement is an activity that serves multiple purposes. What I see a lot of teams struggle with is that they see refinement as a kind of early sprint planning. In my opinion, refinement is primarily about a collective understanding of the what and why. How the Developers are going to tackle the work in a technical perspective is part of sprint planning. Some Scrum teams see value in estimating during a refinement. (I find that a waste of time, by the way; I'd rather work with measuring cycle time and Monte Carlo simulations, but that's just a side note.) To estimate the scope of work, I see that a Developer still makes some kind of technical decomposition in the back of his mind. And that's okay. If the Developers' estimates of the scope of work differ, it is fine to share insights with each other in a technical sense as well. Estimating forces Developers to be concerned earlier than necessary with how they are going to do the work technically. Just enough, just in time remains difficult for many Developers. As a seasoned PST do you agree that making a (technical) plan is not part of refinement?
@scrummasterinblack
@scrummasterinblack Жыл бұрын
Hi. I personally see value in discussing about technical solutions during refinement … especially when the team use it to explore possibilities and options to deliver the solutions. In some cases the team may even lay down options whether to create a simple experiment first before creating a full blown solution.
@Mo.Jo.
@Mo.Jo. Жыл бұрын
I'm a product manager in a completely different field and I've been encouraged by my friends and brother to look into product manager or scrum master roles in software, considering i have alot of experience managing a product. I'm still trying to demystify the differences in these roles in software.
@vinnier8774
@vinnier8774 Жыл бұрын
Can you also share how we can change the status quo as Product owner?
@user-pg2gc5sc3s
@user-pg2gc5sc3s Жыл бұрын
Video would've been so much better if you hadn't constantly called out "if you haven't watched my videos..." which interrupted the flow. Say it once and then reference other videos in the above description field. If it wasn't for this, this would've been amazing.
@scrummasterinblack
@scrummasterinblack Жыл бұрын
Thanks for the feedback 🙏
@DariusTulbure
@DariusTulbure Жыл бұрын
There's one thing I'm not sure I figured out how to solve - and that's how to solve the issue of dependency between designers' output and the ability of the engineers to develop the designed feature. One solution that comes to mind is for designers to be part of the scrum team, but to actively design new screens/features/flows for future sprints, not for the current one. Besides designing the said new screens, in the current sprint designers need to assist engineers with clarifications, support, updates/redesigns if needed, but also to be assisted by developers in ideating and validating design ideas. I don't know if this makes sense.
@scrummasterinblack
@scrummasterinblack Жыл бұрын
Another option is the engineers help out with designing some screens and the designers can facilitate that process. UX or design should not be a specific person’s responsibility. Every team members should help out where they can. That is that crossfunctionality in Scrum is about.
@DariusTulbure
@DariusTulbure Жыл бұрын
@@scrummasterinblack Well, I agree that design is a team activity, in the sense that it's collaborative and everyone can weigh in. But that being said, UX design is a discipline, and of course some people will be better at it than other (including via specialisation, study, experience)! You wouldn't have a specialist front-end developer do the back-end developer's job and vice-versa, would you?
@scrummasterinblack
@scrummasterinblack Жыл бұрын
@@DariusTulbure Yes. And to your point, because UX is a discipline, it can be learnt by anyone. I didn't say _we expect everyone should be an expert in UX_ , my point is _anyone can contribute in doing UX work_ ... and yes everyone will have different level of fidelity in their UX work but _it doesn't mean they can't contribute in doing UX work_ .
@Subzeroeffects
@Subzeroeffects Жыл бұрын
Great video! Thank you so much!
@scrummasterinblack
@scrummasterinblack Жыл бұрын
Thank you for watching.
@magixpipez
@magixpipez Жыл бұрын
Can you do a detailed video, as soon as possible if possible, taking all the job titles I am going to mention here and review them, explaining which will transfer over to SM but most importantly go over a few 2-3 job postings for each position and see what duties are important that will transfer to SM. And how to list it in a resume and what to mention during a SM interview etc. I don't think you or anyone done this before so it would be a special treat for all the subscribers . job titles to review thoroughly, 1. Product analyst 2. Product designer 3. Product developer 4. Product development analyst 5. Product development manager 6. Product director 7. Product lead 8. Product leader 9. Product marketing 10. Product marketing manager 11. Product policy managers 12. Product purchasing coordinator 13. Product support 14. Product support associate 15. Product specialist. (I can't think of anything but except everything I said in the beginning. By when do you think you can make an hour or so video covering this topic. It took me months to collect these job titles. Now I want to challenge you to review each title job, 2-3 postings and see if you find any similarities to SM and etc) feel free to talk about PO. Wouldn't be a bad thing to hear about that either . I am unemployed and i am going to apply to all SM positions sometime this summer or fall in September. Just in case something goes wrong. I want to have a backup plan and that's where this video will come in handy for that backup plan and maybe take on one of these positions first for a year before the SM role.
@janek29567
@janek29567 Жыл бұрын
Where did you make these animations with examples? :)
@ThymoRK
@ThymoRK Жыл бұрын
"A new Sprint starts immediantely after the conclusion of the previous Sprint" (after sprint Retrospectiv, not during the sprint Planning)*
@hendragunawan9615
@hendragunawan9615 Жыл бұрын
Hi Joshua, Greeting from Indonesia. Could you please make a video about how a good workflow is, the example of a good one, example of a bad one, in related to implementing kanban in scrum and not making our workflow as mini-waterfall? Thanks and scrum on