Hi, I am just an ordinary bloke who scaffolds for a living and has an innovative product that I want to implement in the professional sporting industry. I have very basic knowledge when it comes to business so I am trying to learn in my own time after work. I am so grateful for your channel and content 🙌🏾
@bumang2 жыл бұрын
thank you for sharing your insight. it clarified my view and where I stand
@relabstudios2 жыл бұрын
Amazing to hear that 🙏
@jgdesigner2 жыл бұрын
Congrats! I see how the channel is evolving to make your great content even more appealing.
@relabstudios2 жыл бұрын
Thanks to people like you Jose!
@umangshrestha66738 ай бұрын
Hi there, this was a huge help for me. Thanks and liked, shared and subscribed!!!
@sulafaabdulrahim6798 Жыл бұрын
Super informative Thank you
@relabstudios Жыл бұрын
Thank you!🙏
@choirulgarin10 ай бұрын
Thanks Ko Alvin atas ilmunya!
@younghakim13262 жыл бұрын
Thanks for this, Alvin!
@relabstudios2 жыл бұрын
Thank you Young Ha 💙
@akinyemiolabode8992 жыл бұрын
Thank you, this is very detailed
@relabstudios2 жыл бұрын
Appreciate it Akinyemi 🙏
@GuzForster Жыл бұрын
Thanks!
@relabstudios Жыл бұрын
Thanks Guz. Much love!
@TetsusaigaDrgn2 ай бұрын
Hi Alvin! This is a great video that I shared with my work friends who are unsure of how they fit into an agile/scrum framework. What’s your opinion in scenarios where the UX team is a separate org from the Product/Tech teams, especially in a Scrum framework where designs are a dependency for the Tech build? At my company, designers can be considered a borrowed resource and Product would simply ask and expects designs to be turned around in a very short timeframe, without really paying attention to their capacity and workload. I find this to be a consequence of Product and the Tech Scrum Master feel that it is not their responsibility to manage the designer from a Scrum perspective. Could you also do a video on Design Ops and Design Program Management (DPM)? I’m not sure of the UX community is aware of these roles and their responsibilities. Thanks!
@md.sumonbiswas2272 Жыл бұрын
Thank you
@relabstudios Жыл бұрын
Thank you!
@ABChi22 Жыл бұрын
Does the Retrospective also occur immediately after the go/no go decision?
@relabstudios Жыл бұрын
Hi @ABChi22 , yes I would suggest having the Retrospective right after while it's still fresh✨
@djashawe88923 Жыл бұрын
Thanks a lot for the great content. I subscribed to your channel, liked your videos, and have been binge-watching them one by one. I have a question. Do User Research, Competitor Analysis, Market research, Mappings, Journeys, and Flows take place in the Understand Phase?
@RemcoBakker5486 ай бұрын
If you add a design sprint/phase after an agile dev cycle, what would the devs work on while designers design another iteration? Do they wait until design is finished?
@RemcoBakker5485 ай бұрын
Hello?🙂
@madarauchiha5433 Жыл бұрын
Hey Alvin, how is Agile methoadology better when it comes to product design as appose to tradition waterfall method?
@tangik4329 ай бұрын
This is great
@okezsoke Жыл бұрын
So...basically you need to insert a mini UX design waterfall projekt between the agile sprints if you are not lucky. That's a problem. What should devs do until they are waiting for the UX?
@sujaybhagwat3872 жыл бұрын
Hello, I have a question. Do you also have a video or a blog which explain an end-to-end agile process for website project? If yes, that will be great. If not, please share references where I can learn more about this.
@heyons28082 жыл бұрын
Informative video but dude make the screen larger it’s impossible to read/reference back on phone without pausing and zooming 😅
@MukeshThakur Жыл бұрын
From dev pov Is agile for just one project or all projects?
@relabstudios Жыл бұрын
I’d say not all projects are created equal. Some are better to be waterfall and some are perfect for agile. There’s a methodology known as “hybrid” where they typically run with waterfall from the macro and agile in the micro. Perhaps we can do a video on this to help explain soon!
@LM432432 жыл бұрын
Awesome video, many thanks man! One question though, at 4:30 you show the relationship between the design thinking design process and the development cycle, aren't those two done simultaneously, but instead of the design feeding into the dev cycle, the previous sprint's design feeds into the cycle while new design is being created during development. Sorry if this was confusing, but I hope that you get my question :) Cheers
@henkegiaretta Жыл бұрын
Yes this was my thought aswell 🙂 it seems like a waste of time for developers to sit and wait for the design process to finish.
@shesanosan Жыл бұрын
What if as a designer you have nothing to contribute during the daily stand up since you have said it is more about supporting developers. Then is it important to still attend regulalry?
@kylenicholas6362 Жыл бұрын
Depends on how it’s facilitated. Daily scrum should be treated as a short planning event, so a developer may call out that they need your eyes on something after the call, or need your advice on how to progress. If it’s being run as a status update, it makes no sense for anyone to attend because that can be an email.
@sayaleerakh3175 Жыл бұрын
Watching this before my interview, very insightful thanks!!
@relabstudios Жыл бұрын
@sayaleerakh3175 Amazing! This might be too late but hopefully the interview went well!
@messagedeleted35262 жыл бұрын
UXers shouldn’t use design thinking lol DT was created from UX, just used superficially for people that don’t work in UX and boiled it down to a trendy exercise non-designers use to “solve problems”. Now as for a designers role in Agile, be strategic, ask questions, discover the underlying problem to a feature, and use critical thinking in your process. Everything else is iterative. Discover, research, ideate, prototype, test and deploy. This is best used in dual track agile.
@relabstudios2 жыл бұрын
You got it buddy!
@camgere Жыл бұрын
The terms "designer", "design thinking", "design sprint", "developer" and "development sprint" don't mean what they mean in English. "Software designer" would probably be silly.