Presentations, keynotes, how-to's, and Agile tips by Agile Velocity. Serving Agile Austin-style everywhere in the United States.
We love Agile. We love helping people become more productive and happier at work. Put them together and you get Agile Velocity. Our mission is to help accelerate organizational Agility through coaching and training.
Пікірлер
Excellent this is so comprehensive
Mlhd
Mlhd
Thanks, this was informative.
This is the most relevant video on this subject matter. Amazing!
This is not risk management. This more process and project management from quality control and management.
This is just amazing and simple.
“Much of the advice and instruction is in improving the dance and not the weather” god you can say this about so much in corporate America
The concept of the agile business awards takes business agility forward by encouraging diverse organisations to measure progress and reflect on their journey. They take the brave and bold step of opening this up to external scrutiny, and in return get valuable insights how to make further progress, and inspire others to greater achievement.
*PromoSM*
Otherwise known as "Making It Up As You Go": No idea what you're going to deliver or when the customer is going to get delivery, and with every change in direction comes increased spend and changing delivery expectations. A total Mickey Mouse way to approach a project
Thank you for the presentation. But can we apply Agile for rural development projects.
Just saw this... thanks for making it!
Reminds me the desperate need of our suppliers to "get something signed off" to charge us.... but "that something" often stoppwd working when another feature was released....or another sprint. The integration testing showed it many times...and we ended up in a total mess of crazy backlog. THAN everything really bacame an urgent priority...
No, waterfall does not work as described unless managed really badly. We have WBS and Gantt to show WHEN and HOW much work is needed from particular people / resources. That gives you chance to identify clashes and than prioritisation comes into place in terms of assessment what is the possible delay and financial impact impact on particular projects with different scenarios. Easy to do a company priority than. Have seen that hunderts of times in telco. It works. 👍🏻
good one! but, is it really that we have this imperfect information at the beginning? What if we know the are well already? What if we are true professionals in the area? Even traditional approach enables change management, and ...it describes the goals to be met, not the way we meet them - so a great level of responsibility, freedom is available even in traditional management, just the control over the result seems to be much higher as the committment to the deadlines is always there. ....no backlog is planned to be present ;-)
One of the best teachings of agile planning
Great tutorial! Help me understand the concept of Agile Planning
Good simple explanation 👍tyty
After doing all research, this finally answered my question about sprints. THANK YOU!!
Very helpful
This is true how you explained. But you focused on the technical development part. Also other possible risk areas are easier to manage in iterative/incremental methods. E.g. budget, schedule, dependencies. Most important discovery contribute to business risk mitigation is: Ensuring building the right thing what customer wants.
Would this course be good for someone that has no agile experience?
This had no right to be this entertaining, when you did the voices for the hippy devs I just lost it
Well explained and good visual representation. Kudos.
kzread.info/dash/bejne/a6mgmbeCedi9fdI.html
I'm just getting started with the principles of agile and scrum, and I thank you for articulating this in such a crisp, clear, and visual way.
Very good content.
great video. I like the idea of mythical certainty. Mythical certainty assumes that people are rational. We know from behavioral economics that is myth. Mythical certainty also runs counter to the second law of thermodynamics and what know about the science of chaos and complexity. As Moltke said "all plans fail after the first shot is fired." I run a cabinet shop, and build kitchens, and one of my biggest problems is that my clients don't know what they want when the project starts. I have designed my whole process to move in flexible stages so that clients can adjust as they see things start to materialize. For example I do not make any doors or drawers until after the boxes are installed so clients can adjust sizes once they see the boxes in place.
@David Hawks Okay, so you manage to set up a cross-functional team that can cover UI + frontend + backend work. Now, about the shopping database story example, should it be implemented by each one of the three team members? I think that's the case you are representing here (unless I misunderstood), however you will inevitably face a high degree of interdependency between the three of them, and eventually this will end up requiring a lot of daily micro management. What would your idea be to tackle this scenario? Thanks for your time and congrats for your excellent videos!
Thank you, very helpful indeed!
Developers not liking people seem to be a common thing to say. Aren't developers people too?
Great video! Very valuable
Excellent !
Nice Video, helpful
This was extremely helpful and explains the concept of agile in very clear and concise way. Thank you!
Hello. Interesting Video! Can I ask you Which instruments do you use to Paint while talking?(ex: a specific tablet connected to PC with USB port?)
This was done using Notability on an Ipad with the Magic Pencil
Love the OKR format. Thank you for exposing me to that.
Great Video! Sorry for chiming in, I would love your opinion. Have you heard the talk about - Teannah Psychic Sucker (do a google search)? It is an awesome one of a kind product for finding the best project management and business templates minus the normal expense. Ive heard some awesome things about it and my work buddy after a lifetime of fighting got amazing success with it.
14:04 - Being an effective Agile Manager
Thanks for the helpful video. Just thing, in the Scrum Guide 2017 -Sprint Retrospective on page 14. it says "The Sprint Retrospective occurs after the Sprint Review and prior to the next sprint planning". - Thanks again
This is so helpful to see it visualised, thank you!
Great introduction! Love the visuals
What a great way to demonstrate self-organising teams!
2 Questions 1) What do Scrum Masters do when they are not running ceremonies (daily scrum, etc) assuming they are full time with one team? 2) How can Scrum be applied to marketing?
This was a great presentation! Is there a whitepaper available to download? I'm not seeing it on your website.
There's couple things I did not like about this video. One, the instantaneous assumption that developer will work on coolest,easiest, and self-beneficial features of the project. Sorry, while it may have been true in the past, nowadays developers ( even those coming out fresh from university ) are aware of agile, aware of taking into account stakeholder's desired features or functionalities. Assumption that developer will work on easiest feature should also be reconsidered: the goal of agile is to produce working software, and when you automatically assume developer works on the easiest feature, while they may reasonably prioritize the a feature that gets project working - that's gonna lead to unnecessary friction between management and developers. The two points in the end - shared ownership of the project and dialog with stakeholders - that's the good part, and probably should have been introduced right from the beginning of the video. Otherwise, I'm guessing with 1823 views so far, a lot probably did not finished watching the video and were just rolling the eyes by the middle of it all
To clarify in the first scenario (waterfall) I was stating that in the absence of management providing input into priority and just saying everything is high priority the developer is left with prioritizing based on non value based criteria, such as, coolest, easiest, etc. I agree that in agile (the second scenario) developers shouldn't work in this way.
Underrated video. Excellent speaker.
Great Scrum overview!
With test driven development this scenerio wont pop up
Agree, when the whole team embraces owning quality and developers use TDD it will help, however developers still need to learn to break work down into smaller increments. Otherwise you could still have all the developers working in silos for 10 days of the Sprint and not have anything "Done Done" until the end.
@@davidhawks2457 Agreed with not being able to having things done until the last 1-2 days of the Sprint. Unfortunately the team setup shown above, i.e. developers + testers (even when you split up the dev work into frontend and backend), is a common one you will encounter in most projects (not products) development, more specially in consulting industry. The above scenario is a recurring issue I personally have always faced in consulting, so in short one of the key questions would be: how to mitigate interdependency between the dev team members, right? Because that's what you have eventually; you are actually facing dependencies within the dev team (as a whole), because testing cannot commnece until development has finished (classic waterfall side effect). Unfortunately, for fixed price projects, where you as a vendor have to deliver certain scope by a deadline, you cannot always count on mitigating options such as TDD, automation testing, or even pair programming (although I question how efficient the latter can be if not properly prepped and executed). On the other hand, by breaking the stories down into smaller ones, you are indeed reducing the risk but not mitigating it. Testers will still have to wait until development gets done. Yes, you will get things done earlier, which should actually be one of your goals (I like this idea as long as it is feasible), and therefore the burndown chart will look better, and you will have better delivery predictability. Anyways, just wanted to share some thoughts as a Scrum Master. :-)