Emergence
Key Takeaways
The video discusses the concept of emergence in Scrum and its application to project management, highlighting the importance of adaptability and taking advantage of opportunities in complex environments. It also covers the fundamentals of Scrum, including design patterns, organizational standards, and the definition of done.
Full Transcript
welcome to the bait sighs I gel CDs brought to you by adaptive limited follow us on social media subscribe to us on YouTube and hit that bell to get notified whenever we post new content hello and welcome to another video in the bite-size agile series I'm Alice McLeod professional scrum trainer at adaptive and in this video we'll be discussing emergence and the various ways it applies to scrum let's start by defining emergence and looking at the dictionary definition and not three statements come to light the process of something becoming visible the process of something coming into existence and the fact of something becoming known are starting to exist all of these statements describe something that becomes better understood as time progresses using the butterfly as an example it goes through four distinct evolutions of emergence it starts as eggs made on a leaf as the eggs hatched a caterpillar is born ready to live the second stage of the butterfly's existence if a bird was to eat the caterpillar then it would have no knowledge that it was ever to become a butterfly for stage 3 the caterpillar rests within the chrysalis in this transition to becoming the butterfly finally for stage 4 the caterpillar emerges from the chrysalis as a butterfly ready to meet lay eggs and start the life cycle all over again other than genetic triggers no solution design document is given to the caterpillar it simply reacts to triggers in his periods of growth when responded to these result in its development through the complete life cycle so how does emergence relate to scrum and at least four fundamental ways emergence is a relevant topic within scroll by delivering a potentially shippable product and feature slices a scrum team emerges a product from the vision of the product backlog as a product backlog goes through the refinement process from idea to deliverable this emerges knowledge and understanding of the feature the recommended manner of design in scrum is not big design up front but emergent design an architecture emerges to support that design the profit emerges via sprint goals developing a complete slice of the product each sprint this emerges a complete feature of the product incrementally it emerges understanding of the value the product will give to users and customers it emerges feedback giving you a chance to take advantage of opportunity and it emerges an understanding of what does not provide value refinement is emergence of understanding each stage of refinement allows the understanding of the product backlog item or PPI to emerge this enables the scrum team to decide if or how they can deliver it and when they shoot the PPI well first added to the product backlog item I just stayed a strategic goal our customer need in the first refinement of the PPI you might impact their story map to understand where it fits within the overall product the second refinement might look to understand whether there is an epic or large item of work that needs to be further broken down either then or through more refinement it will eventually be considered a deliverable piece of work that can be taken into a sprint emerging architecture provides just enough architecture just in tight in order to create the feature that is being delivered in that iteration or sprint this does not prevent this Grum team from visualizing the emerging architecture through a diagram using a tool such as draw or a team can diagram the functionality they are currently working on this sprint using a color such as red then it sprint to recolor the previous work into black or any other color chosen further work for the current sprint can then again be added to the diagram using red in maintaining the required drawings of architecture in this way a record of decisions is kept the drawer always represents the current true state a less waste is created by having to redo full drawings with every change design pattern standards and reusable components providing neighbors to emergent architecture on design if you have a set of good guidelines then using this it provides guidance to the scrum team when they have decisions to make the use of design patterns such as the single thing the factory method and the model-view-controller facilitates the emergence of architecture and design have an organizational and common standards with any group has grown teams helps guide the emergent architecture more effectively than a big design drawing created up front in an environment of multiple scrum teams having a library reusable components will facilitate the use of common design patterns these support the quality contractors growth which is achieved through a waterfall of implicit artifacts this starts with the organizational standards which apply to all the products or services that the organization produces the next is the common standards which have been agreed between the teams or individuals that are involved in the delivery this might even include an element of the organization of management agreeing to these common standards next will be the definition of done which will be the agreement between the development team and the product owner on actions that will apply to every piece of work that is delivered before the item is considered done this is formally accept his criteria which describes the attributes of each PPI in relation to its fitness for purpose organizations and regulated environments often claim that the one the full design up front because they need a secure robust solution the passage regulatory audits when the focus of the need which is a second part of the prior sentence then as often as realization that is the standards and design patterns that will deliver this upfront diagram and solution design all fringes forms are constrained that actually introduces more risk when workarounds are applied for those working in non vigil or technology-based IOL transfer nations we often hear that this doesn't work and then they need the fool Prime I would suggest you that the plan that you think will work is actually what is limiting you having a predefined upfront planet prevents the ability to take advantage of opportunity when an issue requires understanding deciding reacting to then the big upfront plan will limit your decisions to those you have already considered can't waiver likes to refer to two different spores both baseball and chess the rules are defined on the scrum team placed within those rules however the outcomes of each game depends on the interplay between individuals or teams if you open in chess fixated on the idea you're gonna beat your opponent in seven moves then you will most likely miss their attempt to beat you in five if your strategy and baseball is to hold a no score game until the last inning and then win by one run how will you react if the opponent's score three runs in the first innings in football or soccer the attalia game has traditionally had a view of putting it safe and keep the opponent from playing their game score one goal and then defend if this plan was the most successful then you would have expected them to won every tournament that they have ever played it yet a team like Brazil or Real Madrid who play an attacking kid has been successful does this mean that teams cannot score against Brazil or Real Madrid no what it does mean that they have a culture of taking advantage of opportunity when they see the chance to get an advantage they take it they don't turn it down because it doesn't fit the plan in conclusion the big design up front plan does not provide guidance to create a great product it only creates the box of constraints that your product and all these decisions must fit with it although it feels like a familiar route to success we're challenged to see a previous delivery means without change requests we realize that the big upfront plan is not a successful way to deliver products in their complex and changing environment rather it merely provides a familiar process to understand what failed under the end what we get is no longer valid in order to fully succeed the organization needs to look beyond Planet how to be the best possible caterpillar let go big plan or learning how to merge into the butterfly if you have enjoyed this video like subscribe and hit the bell to be notified when new videos are uploaded thank you for watching
Original Description
Vlog on emergence and how it applies to Scrum
Learn the fundamentals of Scrum and working with Scrum Teams over two days while being an active member of a team in your learning group. Includes an assessment password for Professional Scrum Master level I that will provide a good start for anyone actively working with scrum teams in their career.
Applying Professional Scrum - https://scrumevolution.com/applying-professional-scrum/
Learn how a Scrum Development Team implements advanced practices in Scrum including the complementary practices not described in the Scrum Guide that enable Teams to deliver Done increments of a working product.
Applying Professional Scrum - Software Developer - https://scrumevolution.com/applying-professional-scrum-for-software-development/
Learn how to own a Product as an entrepreneurial Product Owner in a Scrum Team. Provide the vision to your Team through active ownership, ordering and prioritisation of the Product backlog. Engage with stakeholders to ensure you are delivering value through customers journeys and avoid building random bits of a product that delay value until a big bang release.
Professional Scrum Product Owner - https://scrumevolution.com/pspo/
Are you responsible for managing delivery environments of agile teams? This course goes in-depth into building an empowering environment where self-organising teams can thrive while delivering products of the highest possible value.
Professional Agile Leadership - https://scrumevolution.com/professional-agile-leadership-essentials/
Watch on YouTube ↗
(saves to browser)
Sign in to unlock AI tutor explanation · ⚡30
Playlist
Uploads from AdaptDev “Agility Hour” · AdaptDev “Agility Hour” · 7 of 24
1
2
3
4
5
6
▶
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Why Scrum?
AdaptDev “Agility Hour”
Stacey Complexity Model Explained - Alasdair Macleod
AdaptDev “Agility Hour”
Get Scrum - The Scrum Process Explained
AdaptDev “Agility Hour”
The House of Scrum
AdaptDev “Agility Hour”
3 amigos - Complementary Practice in Agile
AdaptDev “Agility Hour”
Module 1 - Agile vs Waterfall
AdaptDev “Agility Hour”
Emergence
AdaptDev “Agility Hour”
Introduction to Scrum Mastery Online Course
AdaptDev “Agility Hour”
Acceptance Criteria vs Definition of Done | Thinking Agile
AdaptDev “Agility Hour”
Identifying and reducing bugs | Thinking Agile
AdaptDev “Agility Hour”
A Day in the life of a Scrum Master | Thinking Agile
AdaptDev “Agility Hour”
Online tools for Story Mapping | Thinking Agile
AdaptDev “Agility Hour”
Cutting the User Story Cake | Thinking Agile
AdaptDev “Agility Hour”
Thinking Agile | Using Jira & Process Management tools
AdaptDev “Agility Hour”
How to determine an items complexity | Thinking Agile
AdaptDev “Agility Hour”
How does a Scrum Team decide which items to work on? | Thinking Agile
AdaptDev “Agility Hour”
Remote Working for Scrum Masters & Can they continue post Covid-19? | Thinking Agile
AdaptDev “Agility Hour”
The Scrum Process Post 2020
AdaptDev “Agility Hour”
An Introduction to our PST Alasdair Macleod
AdaptDev “Agility Hour”
Module 5 Success as a Scrum Master
AdaptDev “Agility Hour”
Module 5 Stances of the Scrum Master
AdaptDev “Agility Hour”
Module 4 Reporting Progress
AdaptDev “Agility Hour”
Module 1 - Agile Manifesto
AdaptDev “Agility Hour”
Applying Professional Scrum
AdaptDev “Agility Hour”
More on: PM Basics
View skill →Related AI Lessons
⚡
⚡
⚡
⚡
Building with mini, Part 3/9: Capturing ideas with todo
Dev.to · Stanislav Kremeň
The Case of BYJU’s Fall: Poor Project Management?
Medium · Startup
Controlling Scope Creep at Scale
Medium · Data Science
Final Fantasy VII Revelation was built in three years because 95% of the team stayed
The Next Web AI
🎓
Tutor Explanation
DeepCamp AI