Microsoft Press

Пікірлер

@SOS_12 2 ай бұрын

I am listening this in 2024!! Thank you from the future!

@jimmiller9330 8 ай бұрын

Where on the “board” is the architecture and requirements defined?

@Geza_Molnar_ 4 ай бұрын

@jimmiller9330 In his specific board at "Breakdown" - what may be read as "refinement". Though, his board is more specific for the handling of questions during this talk than suitable for software development. The Kanban board adapts to the work under consideration. There are weird and funny ones on the internet, it's worth for a search 🙂 You may define a board as that suits your team, the environment, the work etc. - they may be even branches in the middle (I saw that). Two general examples for sw dev: - you have a wider-longer lifecycle on the board that at the left (beginning) includes also the work of e.g. the Product Owner and the Solution Architect and the Software Architect, etc. - you may have a board for the PO, one for the Software Architect, and one for the Dev Team - the result of their work 'falls off' their board on the other's board, however not necessarily knot together so tightly, they are not related every time (some tools have automatisations to support this) As a heretical example for both 'sides' of Kanban and of Scrum: - a scrum board for sw dev work running that in sprints - AND a kanban board for bugs (possibly higher priorities) and other errands like research, evaluation of new tools, architecture work, etc. - and then adaptive 🙂prioritisation and share of capacities.

@KiezKind030 9 ай бұрын

Gues Video, sauber erklärt! ❤

@evenzero Жыл бұрын

the original win32 api was pretty tight

@redpilldude8688 Жыл бұрын

The estimating answer was underwhelming. For complex cross functional projects, we need to know the start, late start, end and then critical path to be best able to work cross functionally at an enterprise level. His estimations would be lacking, to say the least. Not to mention updating them somehow on his board. This is fine for coding but not real projects at a high level.

@TheFlacidFlamingo Жыл бұрын

Someone get this audience a cough drop and a glass of water!

@martinaniethus8756 Жыл бұрын

DaNkEsChOn FüR dIe HiLfE :)

@martinaniethus8756 Жыл бұрын

Babimimhong

@venus5471 Жыл бұрын

Good lecture on Kanban overview.

@gulabeerkhan2150 Жыл бұрын

Amazing presentation

@1317511 Жыл бұрын

Come on give Doug a break and let this gent talks estimation and schedule..and really no one asking follow up questions there..FANTASTIC

@bluehelion Жыл бұрын

I started reading it 2 weeks ago and I am hooked to read and put into practice what this great Microsoft professional has achieved with this book.

@Heroas_Hamseros Жыл бұрын

Und wenn man ne Online Version verwendet?

@shrawankumar-yp4xs Жыл бұрын

He is genius

@LearningToCodeAndDesign 2 жыл бұрын

I loved seeing when he took the audience questions and started using a Kanban board to get to them.

@MrApaHotel 2 жыл бұрын

I need kanban to clean my house

@Powellyy93 2 жыл бұрын

Love Code - anyone know other CS books of similar style?

@dmdm8018 2 жыл бұрын

I remember reading about how windows worked and the messages etc. it was so helpful. Thank you.

@drapsin89 2 жыл бұрын

14:19 Didn't know Michael Phelps grew a beard and likes Agile project management

@adityaverma2492 2 жыл бұрын

freudian slip @01:25

@Marvin-vb8ek 2 жыл бұрын

Man merkt das Video von 2012 ist xD

@ralphwallace2223 3 жыл бұрын

An excellent overview.

@atchg3388 3 жыл бұрын

This is a great lecture on Kanban. Thank you.

@Bash0r3 3 жыл бұрын

Danke, hat mir sehr geholfen, selbst nach all den Jahren.

@kravets_coding 3 жыл бұрын

47:32 Branching and Publishing 49:23 Bugs 51:02 Geographically distributed teams. Online boards. 54:10 What about timing for a daily meeting 55:20 Benefits versus timeboxing

@planetjam3529 2 жыл бұрын

21:31 WIP Limits

@jaguarclub2679 3 жыл бұрын

bin beim Video eingeschlafen

@kian8385 3 жыл бұрын

Danke

@abkarmy911 3 жыл бұрын

Gute Nacht Leute

@philip7184 3 жыл бұрын

I still like Zen Tao software, full life cycle management tools, which including Kanban tools

@anandsingh9719 3 жыл бұрын

25:00

@anandsingh9719 3 жыл бұрын

20:00

@anandsingh9719 3 жыл бұрын

16:00

@anandsingh9719 3 жыл бұрын

1:00

@kingsleyoji649 3 жыл бұрын

Do different job titles/responsibilities/expertise have different backlog priorities or would this be beneficial??

@sirisaksirisak6981 3 жыл бұрын

They bring kanban into agile method not all steps, in kanban product line they have control point to protect materials or items in assembly product this method aim to have a material or an item in time in product line protect lack of material and safey stock and sunk cost, kanban means the number code of materials or item part paper put in the bin along the assembly line in product station control points this method aim to avoid lead time in MRP chart to have enough materials we call JIT just in time in product line in order to save time, see in flow chart from start to finish out come.Kanban Pros suit for made by order product have high flexiblity in productivty not fix. Cons lack of creativity and product developed cause focus on finish in time.

@karimsoboh6862 3 жыл бұрын

Well, I´m a strong SCRUM fun, but u make me like KANBAN after this video ... what is ur book name? wanna look through amazon on it, Thanks.

@jamesjanse3731 3 жыл бұрын

Physical boards are great, but then COVID happened :p

@johnjacobs1969 4 жыл бұрын

Interesting guy :)

@jesusbasketball8740 4 жыл бұрын

Priorities can change in scrum in any given/on going sprint directed by the Product Owner. For the team is Managing work from backlog/priority which is similar in Kanban you still have the same work to dev/test/perf/deploy in Kanban. If your trying to reduce overhead of scrum ceremonies that’s fine but show me proven time/cost savings on delivering software? If requirements, test results all other unknowns become impediments what is difference in each process? Both processes can pull new if impediments occur or new priority or defects. It’s Product Owner responsibility to manage and communicate effectively to the team. Time box or not solutions have to be delivered to the market or your consumers efficient and quickly.

@Geza_Molnar_ 4 ай бұрын

@jesusbasketball8740 I agree with you on most of what you mention. However "Priorities can change in scrum in any given/on going sprint directed by the Product Owner." - in the ongoing sprint???

@pollafattah7062 4 жыл бұрын

OK, strange times!! He kisses the book at the end and I am thinking "IT'S CORONA TIME"

@adishabhatra 4 жыл бұрын

So much for selling Kanban - LOL

@shekhar0304 3 жыл бұрын

Dear Friend, this presentation is from 2015...People used to kiss so many things back then...

@pedroveas4751 4 жыл бұрын

Very good presentation, but I think only mature and self-organized team supported by they organization can adopt it. Organization with Waterfall background usually not allow this without a manager involved that generally cause huge noise, there by frameworks like Scrum or methodologies like XP may facilitate and protect a process flow optimization methods and maybe with that umbrella, then Kanban can be applied.

@PhaseFabrication 4 жыл бұрын

scam

@LuigiZambetti 4 жыл бұрын

A Legend, that's he.

@praedatos5489 4 жыл бұрын

Gutes Video zum Einschlafen aber nicht als tutorial xD

@marciomaiajr 4 жыл бұрын

Programming Windows 5th edition should be re-released. It's a masterpiece.

@stephanie9533 4 жыл бұрын

Great presentation thanks! i am using zentao project management tool. It's a total game changer because it's Scrum tool with open source version more features with cheaper price. It's been the tool I've been dreaming of for foreverrrr!