Lecture 1: Free Short Course: Agile Project Management

Register on the IT Masters website for access to the free course materials: www.itmasters.edu.au/free-shor...
Lecture 1: Introduction -- Agile Definition and Application:
- How Agile places among the project management methodologies
- The different methods of Agile
- Where Agile is most relevant
Presented by Brenton Burchmore and Kelsey van Haaster

Пікірлер: 11

  • @ventriloquistkaterinasopid6939
    @ventriloquistkaterinasopid69393 жыл бұрын

    I absolutely love this course and the teacher!

  • @Mindrage9
    @Mindrage910 жыл бұрын

    Brenton is a fantastic teacher. Thanks for the videos...late one!

  • @JCNegri
    @JCNegri4 жыл бұрын

    Just accessing this Course. Excellent. Thanks for all the info.

  • @vagafu.jvfonlinestore
    @vagafu.jvfonlinestore2 жыл бұрын

    Excellent teaching.

  • @JustinShaedo
    @JustinShaedo3 жыл бұрын

    12:05 Plannists or Reactivists? What are plannists? (max calm during planning process) Why do we want planning? Expectations, surprises and chaos Joining the dots avoids stress Acuity, alacrity, celerity (intent, investment, achievement) What stresses you? Agility requires audacity 20:46 Who are the Reactivists? I don’t exactly remember the plan… - Just in time - over - Just in case Decisions come from foundations of understanding, wisdom and context Planning and plans are not the same Agility requires preparedness 29:04 Questions (course related) 35:21 Appeasing Stereotypes Plannists: (cold/pre planning) - Our best decisions will be based on the most current information which we don’t yet have - Our most important objectives are only as stable as the predictive certainty of our client/customer - The same important decisions but in a different order Reactivists: (hot/just-in-time planning) - We need a strong source of alignment for the team to contextually contribute together along the way - The journey may be flexible, but the fundamental outcomes can (and must) be defined, understood and shared - The same important decisions but in a different order 39:30 Empirical Project Challenges 1. The client doesn’t know what they want ("needs analysis", poor stake holder engagement etc) 2. The client thinks they know what they want but are wrong 3. We don’t understand what the client wants (Communcation errors) 4. We think we understand but we are wrong 5. We don’t know how to do it 6. We thought we knew how but we were wrong 7. Changes to external factors alter the objectives (GFC, Covid, etc) 8. The client has learned along the way that they now want something different 9. We have learned along the way that we can offer something different 10. The budget (and therefore scope) has changed 46:10 Questions - determining budget in agile (with the budget, what can we build?) 50:41 Strictly Agile - Sub-methods developed to bring some process and even rigidity to Agile - An artificial strictness to a fundamentally flexible philosophy - Before we can pick and choose we need to know what they offer and why - Before we can apply we need to understand and engage the team - How does any method affect the decisions? - How does any method affect the team? 54:50 Content and Context for Decisions Alignment - shared undestanding Agreement - on course of action 1:01:29 questions - get client onside: What are their key fears and key elements of certainty/most important elements (eg budget and schedule/dead lines) 1:07:18 intro II 1:15:35 So you want to run an Agile project Getting started -Software governance structures -PMO’s In Flight -Organisational planning -Reporting -Software development practitioners Delivery -Dev-Ops 1:28:50 Summary 1:32:50 Questions

  • @falmonacidc

    @falmonacidc

    Жыл бұрын

    Thank you Justin

  • @dougosborn5435
    @dougosborn54356 жыл бұрын

    I think the decision-maker buy-in is less of an issue now than it was 5 years ago. 'Agile' has almost become the default approach for IT projects, whether it's the best suited approach or not. Also I think it remains poorly understood. Try, for example, simply stating that Agile isn't a delivery methodology but an approach or philosophy and see what reaction you get.

  • @NickParenti9150
    @NickParenti91509 жыл бұрын

    I am exploring Agile for operations outside of software development. As a Lean trained leader, I see some parallels. Oddly enough, so far, Agile looks like the training I got as a Naval officer, especially follow-up/status updates. It also reminds me of a lecture I heard from motivational speaker Zig Ziggler. He created a competition between 2 teams, "bring me a freshly baked loaf of bread". Team 1 sat down and made a shopping list. Team 2 headed to the grocery store without a list. When team 2 got to the grocery store they realized it had a bakery and made fresh baked bread. Instead of buying ingredients, they bought the bread and won. Where else can I do some free learning before I decide to commit to anything else:?

  • @triplea007

    @triplea007

    6 жыл бұрын

    Not to be confused with Dirk Diggler.

  • @DxBang3D
    @DxBang3D11 жыл бұрын

    00:00 ?

Келесі