Brilliant Audio Presents. Coming through Slaughter by Michael Andace. Performed by Dion Graham. Buddy Bolden began to get famous right after 1900 come in. He was the first to play the hard jazz and blues for dancing. Had a good band. Strictly ear band. Later on Armstrong, Bunk Johnson, Freddie Keppert. They all knew he began a good jazz. John Robichaux had a real reading band, but Buddy used to kill Robichaux anywhere he went. When he prayed, he'd take the people with him all the way down Canal Street. Always looked good. When he bought a cornet, he'd shine it up and make it glisten like a woman's leg. Louis Jones. Three Sonographs. Pictures of dolphin sounds made by a machine that is more sensitive than the human ear. The top left sonograph shows a squawk. Squawks are common emotional expressions that have many frequencies or pitches, which are vocalized simultaneously. The top right sonograph is a whistle. Note that the number of frequencies is small and this gives a pure sound, not a squawk. Whistles are like personal signatures for dolphins and identify each dolphin as well as its location. The middle sonograph shows a dolphin making two kinds of signals simultaneously. The vertical stripes are echolocation clicks, sharp multi-frequency sounds, and the dark mountain-like humbs are the signature whistles. No one knows how a dolphin makes both whistles and echolocation clicks simultaneously. One. His Geography. Float by in a car today and see the corner shops, the signs of the owners obliterated by brand names. Tassan's food store, which he lived opposite for a time, surrounded by drink Coca-Cola in bottles, barks, or Lorelie's tavern. The signs speckled in the sun. Tom Moore, Yellowstone, Jax, Coca-Cola, Coca-Cola. Primary yellows and reds muted now against the white, horizontal sheet wood walls. This district, the homes and stores are a mile or so from the streets made marble by jazz. There are no songs about Gravier Street or Phillips or Furst or the Mount Ararat Missionary Baptist Church as mother lived next door too. Just the names of the streets written vertically on the telephone poles or the letters sunk into pavement that you walk over. Gravier. A bit too stylish for the wooden houses, almost falling down. The signs, the porches, and the steps broken through when no one sits outside now. It is further away that you find Rampart Street, then higher up Basin Street, then one block higher, Franklin.  Here the famous whore Bricktop Jackson carried a fifteen-inch knife and her lover, John Miller, had no left arm and wore a chain with an iron ball in the end to replace it. Killed by Bricktop herself on December 7th, 1861, because of his bestial habits and ferocious manners. And here one legged Duffy, born Mary Rich, was stabbed by her boyfriend and had her head beaten in with her own wooden leg. And gamblers carry and cocaine to a game. History was slow here. It was elsewhere in town, in the Bravo District of Storyville, that one made and lost money. The black whores and musicians shipped in from the suburbs and the black customers refused. Where the price of a teenage virgin was eight hundred dollars in 1860. Where Dr. Miles, who later went into the Alka-Seltzer business, offered cures for gonorrhea. The women wore Gloria de Dijon and Marshal Neil Roses and their whores sold goofered dust and bend over oil. Money poured in, slid around. By the end of the nineteenth century, two thousand prostitutes were working regularly. There were at least seventy professional gamblers. Thirty piano players took in several thousand each in weekly tips. Sample complete. Ready to continue?


Mae Gwbner yn sylweddol i'r gondol ei mh Gyllidau wedi'i ddenydd iawn, ac mae'n gwybod yn awr peonfa'r gyllidau, ac mae'n gwybod yn ystod ei ch hope mae ym erioedd ac yn ystod sefydig mae'n gwybod yn gyfan fyrdadau. Mae'r gwbl yn ei gynhyrchu ddweud hynny'n dweud yn dweud â'r awr ei ddweud. yn Emo State, com 2023. He said that no one would discourage him from his journey to actualise his dream. Well, joining us to discuss this is AIC Akarandu. He's a policy analyst. Thank you very much AIC for joining us. We're having connection problems with Mr Akarandu. We'll take a quick break and bring you a report from Nigerians and how they feel about the NSAS situation. Stay with us. There is nothing wrong in getting protection for them. But again, see, in Yoruba language, it says if you do not do something behind, as in something hidden, you should not be scared. You should not be scared of, okay, if truly the lawyers came out to say the truth about whatever the investigation or whatever happens during the NSAS which we all know or are aware of, you understand? I don't think they should be scared of maybe anybody threatening them, you understand? Or if there's anybody threatening them, they should be exposed. See, what they did is very commendable. I mean the panel, they did their constitutional duty, taking their time to find out the truth and they are probably the truth. Now they are getting its rights in the responsibility of the government to protect them.   A threat to life under the condition is a crime. So they have to be protected one way or the other by the government because they have done their job, a very good job for that matter. So there is no good thing about that, that's what ought to be done. It's necessary for them to be immured. Because if they are immured, it will help them to be able to perform very well. And because of the insecurity nature of the country Nigeria we are, I believe if they are protected, it will also help them. First of all, they are citizens of the country. The government should protect them. And it's a very, very sensitive issue that happened. And at this point, I think there's no reason why more lives should go down. Let's get to the bottom of it. Everybody should own their responsibilities, take actions for their responsibilities and we move on from it. Simple apologies reaching out to the families because, I mean, people actually died. To be honest with you, people actually died. So let's stop these jokes about people not dying or whatnot. And we can move on. If we know we want the next generation and the next two generations to know that we did the right thing as a government and as a people, then we should own up to the issues and face them. Apologies for the connection hiccups. We're still being joined by AIC, a car and do a policy analyst. I was still looking at the recent developments in emo state and of course the former governor is saying that nothing is going to get in the way of him actualising his dream of being the governor of the state. But then we're hearing that religious leaders, we're hearing the leaders of thought in the state and even political stakeholders are saying that he has one way or the other contravened the electoral act. Do you agree with this position? The truth is that the state government is just looking for a diversionary measure. They want a situation where people can be distracted from the real issues so that questions cannot be asked about what our pensioners are passing through till the last two years of this administration. They don't want people to notice that several servants have been passing through one verification or the other till the past two years. They don't want anybody to ask about what is happening with the local government forms and other maladistration that is happening. That is why they are using Iheidoha as a distraction and unfortunately for them the people are not buying into that. Imolite are wiser. They have shown that they know what is happening and they have shown that they cannot be deceived. Iheidoha has not declared for governorship and if you listen to his speech very well on that day he said he didn't come for comparison and there is no way one could have said that Iheidoha is violating electoral law. There is nothing like that. Every declaration was not a programme of a political party. It was not organised by any political party. It was organised by a pressure group and in that place that day you have the chairman of other political parties. I remember vividly I saw the chairman of Ab-Gaidimol State. He spoke at that event. So it is insensitive for anybody to say that the programme was organised by the PgD in the first place. It is all part of diversionary measures. Secondly, there is nothing Iheidoha. From governorship come 2024. You just answered my question because I was going to ask does he really have an intention to run for governorship? Yes, he has. But at the right time he will let him know about his ambition because the truth has today is that the vast majority of Fundimol are aiming for Iheidoha to come back. The ones, those things he started in his administration that come as the witness for several months. The pressure laws that are being paid, they were in their homes receiving a lot. I'm curious. Can you hear me? I can hear you. What things did he start? I remember vividly while he was still in... Let me hear you. You're saying that the people of Imo are yearning for him to return to continue the things that he started. I'm curious. What things did he start that he needs to continue? That is what I'm telling you. On that seven months when Iheidoha was the governor there was an absolute calmness. Confidence was restored among the people. Let me give you an instance. Within that period there was an incident at Obu where the police station was down. In less than 10 hours of that incident Iheidoha was in Obu to console with the family, to sympathize with the Nigerian police force and to calm the situation in the area. That is leadership. But we have a situation where issues happen in Imo's state. Over 24 hours nobody says anything. No government talks. Unless the people continue to shout on social media before you can see government talk. As of today there is a leadership vacuum that is being yearned to be filled. ImoLight cannot wait for this administration to end so that they can vote in a responsible government that can fix their roads and they know that this road is up to start that. Look at political truth. Look at political decision. That was where Bohare commissioned when he was in Imo's state. Is that something that I should vote for a person? Fixing of roads is what you should do with taxpayers' monies. It's not a project that I should plug in. Is it also something that you put in a scorecard because I think we have misplaced priorities now? Fixing a road is the job of every single governor. Fixing a road is the job of every single governor because taxes are paid for those things to be done. It should not be a reason why I should vote a person in because that's that person's responsibility, isn't it? That's my question. I want to get you clear. You're making a case for fixing roads and you're making reference to river states roads and I'm wondering to myself, fixing a road should not be a reason why I would vote a person into power because originally that's their job. I pay taxes for that reason. No, no, no. Let me educate you on that. Quickly. Because of the mad administration we have in Imo's state, a PC leadership for the past eight years, fixing a road has become a big deal for Imo.  But today in Imo's state, you will agree with me that for the past nine years, we've brought a PC leadership in this age, we cannot boast of one particular road without Portugal and I want to be proved wrong. So that is why fixing a road has become a big deal for Imo because you need to fix the road roads. You need to reduce over migration. So that somebody in the heat room bomber does not need to come to a wedding to do business. Somebody in our loop does not need to come to a wedding to do business. Somebody in the adjunction does not need to come to a wedding to do business. They can get what they want. They can assess their road roads. And they help their lookers unfortunately we're out of time. This is because of the hiccups that we had with our connection but we want to appreciate you. And we're hopefully going to have you back to discuss more on this. AICR Cymru is a policy analyst and he's joining us from Imo's state. Thank you so much for speaking with us. Thank you for blessing. All right. Well, thank you all for staying with us and being part of the conversation. We want to appreciate you. Don't forget you can watch a replay if you missed the whole show on our YouTube channels at Plus TV Africa and at Plus TV Africa Lifestyle. I'm Marianna Cohn. Do you have a good evening. See you tomorrow.


We got 88 red bulls and a hundred ice cream bulls.  Man, it's a nice one. It's my turn to work. Oh, my God. Get away from over here.  For the first one, I'll always be looking like me.   I need 81.


Hi everybody it's Sabah McStuffcraft, thank you for watching my tutorial. I've got a really quick card making project to share today, this is a card that I made for my cousin on the birth of her new baby boy. Now I actually made this last year and forgot I had the video so I thought I would share it. Last year I received my trim craft design team box and we had this huge bag of buttons. Now apart from making the men's little kind of t-shirt cards that I shared recently, I used the buttons on there but I hadn't really used them in anything else, so I thought they would be great for this. So basically I'm creating a hot air balloon for this nice baby card. So I'm just pulling out all the blues, the yellow colors, the kind of pearlized white ones, all kinds of soft colors to make this hot air balloon. That doesn't matter about the sizes, you can have all different sizes, in fact that looks better because the small ones can kind of fill up your gaps and this will also work with other materials so you might have metal bits of broken jewelry, that kind of thing, you kind of get the idea. So I'm going around and sticking them all down, I'm using my hot glue for one it's quick and also because they're plastic and just a different you know material that you're using, the hot glue just works really well. So now at this point they are all stuck down, you can see I've got my balloon shape there and I'm just pulling off a few little random glue strands. Now this piece of card stock is going to be for the basket and it's just a piece of, I think it was about three quarters by one and I added, put it through with an embossing folder and it was the knitted jumper one I think it was and you can see there it looked really cool for the basket and then I just drew in some black lines to make the rope and that was it. I feel like I've not spoken at all but it's that quick. Then I finished it with a lovely sentiment that says congratulations on your new baby and then as you open it it says boy you've got the little bow there and you can see it just looks really really cute and it's just fun to look at, it's fun to touch and it's just something different. So I hope I've inspired you, go rate your buttons or any other bits you might have lying around and see what you can create. I'll be back again next week thanks for watching, bye.


The 50 meter world record got obliterated by Juo Ying Chang in the Paris swimming games and look at his strategy. Everyone else is splashing. He's just still as can be. His legs are motoring. His head looks like a water balloon that hasn't burst yet but is about to burst. His torso has got to be as strong as ever. Headfirst into the wall, broke the record, finished under 30 seconds. The record for people with arms is 21 seconds. Incredible. You missed that. You did not watch it and this is everything you missed that you never planned on watching it. Ozzy football. We're back. Collingwood and Adelaide are facing off. Both are atop the table. If Adelaide wins, they will be tied for first. They are winning by three but the Magpies are the comeback team. They've won 12 of their last 16 games where they're trailing after the third quarter and that is a hell of a mark taken by Jamie Elliott. And I find it interesting that American brains would look at this and think that the feet have to be in bounds because that's how U.S. football works. Gridiron. But it's more like soccer where it's just the ball and I tweeted out about, you know, this catch. What matters? Does the foot have to come down like U.S. football? And they're like, no, it's kind of just, does he control the ball before all of the ball is over the line? I mean, so that's a fair catch. Because if you look back over here, this dude is running around with the ball but keeping the ball in bounds while his feet are out of bounds much like soccer. So that kind of interested me because it's different than what I'm used to, which made it stand out. Anyway, so because he catches that, takes the mark. Now he has a free kick from where he caught it. And it's kind of a tough angle. But if he makes it, they take the lead with three minutes to go miss shank it. Ah, oh, the kids are heckling. He does not care splits the uprights takes a lead turns around heckles back. Oh, they flip them the bird because they're upset and the pies win it. Both these teams lost their next game, but they're probably going to meet up because they're both very good. We had a 10 cup moment in the European Open and disc golf. Anthony Borella here looking real awesome. Love the outfit. He's currently in first place on the 16th hole for the tournament.  He's 12th in the US. He's got 11 top 10 finishes, six top five, but he overshoots the island on his first throw and his second throw.  Macbeth caddying for him and Macbeth just announced that he's having a baby. Congrats to Paul Macbeth. Congrats to Paul Macbeth. Anyway, so he lines it up. It's now his fourth throw.  I'm going on vacation. No, deep again, misses again. Uh-oh. Fifth throw and is he gonna, is it get down, get down? Come on, please get down. No, deep again. Sixth throw. Please get down. Please. No, deep again. Hand me another. I got it. Never fear. Seventh throw. Surely this one is it. And it is. Yeah, it is. Yay. All right. So we got on the island, but yeah, kind of a disastrous hole for him. He does finish strong. He makes the putt and then he had a nice Instagram post about how he always wanted to play there. He put himself in a bad spot. He's going to come back and do even better. He's having a good year. He's ranked really well. You know, it's not a failing moment. It's a learning moment.  And oh my God, we're back to the indoor football league. Eastern Conference Championship. The Frisco fighters are up on the storm 44-37 with 40 seconds left, but they are driving. Now, I'm super interested in football formations when you can have wide receivers in motion. If you see the very top of your screen, that receiver, they're playing like press on him, defenders right up in his face, and they use that to their advantage. The two wide receivers go in motion. They kind of crisscross and then they hand it off to 41. And he's just going to run right behind the wide receiver who is being covered tightly, who makes the gap, and they get easy yards. Seems like just do that all the time. Seems like defense is really hard because this time they run similar, but the quarterback keeps it and he runs into his own guy. Otherwise, he would have been a little more home free. The storm are storming down. Oh, West Indies cricket fan in the house. Darren Sammy, what up? What's that guy doing? He likes fringe sports like me. That guy better watch this show. Touchdown. Touchdown storm. Touchdown by the storm. All the Dallas Cowboys slash Frisco fighter fans are upset. They have to go for two rolls right little jump throw. Looks like he has him open, but then he kind of didn't. It was a real tight catch. Catches it. The storm when they are your East. Look at that sad Cowboys fan with the mullet and the belt on. I got dressed up for this. Shit. They are the Eastern Conference champions. The Frisco fighters are not the Eastern Conference champions. That's the indoor football league. And now finally, the secret and hushed about women's world. Watch the passing on this play by Germany. One touch. Got it. Boom, boom, boom. Fake boom to real boom to boom by the keeper. Why you can't do that? She's right. You can't do that. That's a yellow card. That's going to be a PK. Okay. All right. Fair, fair. Keeper says fair. I did come a little.  Germany ties it in the 88th minute. They're excited. We go to extra time. Six minutes of extra time. They're in the 96th minute. Who's going to kick this? Not me. I'm out of here. You take it. Okay. Corner kick for Columbia puts it up. Germany just watches. No one moves at all and it goes in the net. Damn. Should have covered someone. She does a hand symbol. I don't know what that means. She slides. That was everything you missed that you never planned on watching. Fan of the week. Who you got? Who you voting for? Make it count.   Not any other part of your body. Thanks for watching. If you enjoyed, subscribe.


Okay, so we're live great So hey everyone We moved the meeting One week after it was supposed to be so more of us could join and We're pretty close to Jenkins world and we're pretty close. I hope to official release so I'm gonna share the screen and And I hope you can see the meeting notes so Today during at the meeting we have well me Oleg and there's also a Yon or John I'm very sorry. I don't know like me spell your surname and I Don't know how to pronounce your name properly, but I will fix that after the meeting. It doesn't matter. Just John. It's fine Okay, perfect. Thank you. So well the agenda is pretty straightforward as usual. We should Check the action items from in previous meeting discuss or maybe decide about the Releasing and well any other business we might have and Of course Anyone can add anything to the agenda during the meeting as long as we have time for that No, okay. I have your surname here. So I can complete Yes, so let's have a look at action items. It's basically all on me First of all, I created some Some mess when I I was pretty sure that we all agreed that we're creating separate special interest group for a J cask and That was not exactly what we agreed on and I understand that well maybe at some point we will need that but for now we've decided to Stay as a part of cloud native special interest group, but we will still still continue with J cask office hours probably the same times that we have now unless we find out that there are people from different times zones that really want to Join and then we'll have to rethink that So the Jenkins dot a o and three regarding cloud native special interest group was updated with the information about J cask being a part of that or configuration is called actually not J cask only being a part of that We also agreed that every now and then if it makes sense, of course we will report The progress or whatever we talked about at the cloud native special interest group meeting But the main the main meeting for us is that one the one we're having right now and the next one was looking at the shading snake yamal issue and Well, actually yesterday I I had a lot of trouble with it I could not build a plugin because of that, but Nikola helped and it seems that he found some nice solution So it's already much as far as far as I remember When it comes to this issue for point For It's closed now. Yeah, so so that that's That is not applicable and more and the update invitation for the meeting I guess it was About shifting the weeks and it happened. So I can confirm that Well action items are more or less done So that's it about the I guess we should talk about the release status. So when we have a look at the release one milestone issues that are still opened we have Can't export configuration when easy to plug in slave is connected and it's only should have I Have a look at any moment Cannot install configuration is called plug-in. Yeah, I I don't exactly remember. What's what's in there So we'll have a look at the issue and then getting started documentation improved. It's like improvement in work in progress. It's not a stopper for us when it comes to releasing because it can Be part of a github repository, but what we can add it all days after the actual release happens I really hope to to have time to work on that today So, yeah, let's have a look at those two issues can't export configuration when easy to plug in slave is connected Yeah, this one is pretty simple When we have a cloud plug-in to to create a slave a dynamic slave It's added to Jenkins as a as a plain node and we have no way to know that this node should not be exported And in the specific case of the easy to plug-in Actually, we can't export because some of the of the implementation classes have The don't implements a standard Jenkins API for something that has you are binding and so on Because they are not designed to be bound to you eyes as supposed to be transient nodes only created from from the cloud provider So that's the reason. So there is a potential quick fix to enable This easy to reason return strategy for you are binding but that makes no sense for the easy to plug-in and And so there is a there is a challenge with within Jenkins core to to be able to mark So those nodes are being some way generated by sub-party components The same issue applies for our jobs. If I remember correctly, there is already a g-ray issue for it as that Intem is being generated by the branch source Multi-multi-brunch jobs should be flanked some way so that Jenkins knows that those specific items Are generated and are not first-class citizens So for this one, we don't have Any fix in in the pipe Yeah, so we hit this issue with agents a few years ago we don't call some more Tools for tracking pipeline usage workspaces and for us it was also a challenge to understand whether the agent is provisioned by cloud EPA or not So There were some ideas how to fix that, but generally we have never touched it in Jenkins core Yeah, I totally agree with you the fix is supposed to be there So changes in core are required to That Yeah, yeah Do we then consider it as a stopper for my release one zero I Won't consider anything related to export as a stripper Because we know there is lots of pitches with exports that's really best effort so far So there is surprise begins our issue with export and this one is yet another one But I mean, yeah, well It's it's it's not very good that we can't Fix it on our side and I if I understand correctly the huge in the core If if there there is decision to fix this it will take some time, right? Yeah, it would take some time There's a way to consider this is that you can export Jenkins instance that is used for Experiments and not to actually run jobs. So not actually provisioning stuff as As easy easy to slaves If the idea is to say I want to use the classic web UI and see The corresponding channel syntax by using the export and you can just bootstrap a test instance It's like this to say hi I have my heavy loaded Jenkins instance, and I want to expanse and we are Pretty far from being able to do this and not just considering the specific issues There is many other places where we still have issues to address and some of them will require some deep changes in Jenkins Okay, so well, I guess we have to we we should remove the the issue from my school one and maybe provide some some some more information regarding the way forward and Sounds like the the bidding core is the right way to go. So The fact that this specific case won't be supported Anyone has different opinion Assume it means no so Nicola can you drop a comment about Great, thanks, and the other one was Cannot install configurations called Plugging and there is some long exchange Yeah, this one I don't really know is so John just asked if I'm having audio issues and Can you elaborate on that because I'm not I'm not sure if you can't hear me or if you hear some strange noise Well, I can hear all the others you just sometimes sound like a metallic robot that just basically just fails Okay. Well, that's probably my Relatively slow internet that I can't do much about unfortunately But I hope it's good enough for you to understand me Sure But thanks for noticing anyway, so again Cannot install configuration is plug is code Plug-in well, I added it to the milestone, but it doesn't seem like it in forward And this is the only person that is Complaining about the not being able to install the plug-ins. So again, I I Know I might be might be totally wrong, but I wouldn't treat it as a stopper for is 1.0 and definitely have Have a look and I can try to Recreate the so I can like assign myself to that one Guess the most straightforward way you would be to try installing on the specified version Because you're taking the exception most likely it's an incompatibility result Jenkins core and we don't test A lot on it. Yeah, I so I basically want to have a look at what what he had and the recreate As similar as possible in stands on my own so I can I can do that But it's he's using two seventy three dot three And I noticed that somewhere we might regarding the HPA run issue Someone Nicola wasn't you that commented that maybe we just have to bump the supported version to the higher one Yeah, of course, it's easy And eventually you will have to bump versions anyway if you want to pick up new changes from the core Mm-hmm So it could be an option, but if such issue happens Like if something is wrong, so he's annotation indexer. So most likely it's again related to something like Yeah, but a API again Yeah, I'm not 100% sure to solve beta API. We are a running NB and you run with two dot one dot one that's something version, right? Right, but Jenkins users don't use maybe an HPA run. Yeah Without maybe an HPA run and should be working but type not present. Yeah, most likely links to this issue being I'm not sure why maybe it's something with Google injector Yeah, you may see that it uses some go over code inside I'm not sure why yeah, but anyway, I as I said I will I Will have a look and But does any of you consider it to be a stopper for release One that's zero Actually, I read the one of the last comments where it actually says that the issue seemed fixed and it's a related to the active directory plug-in instead It's a the moustache commented 22 days ago. Oh, okay So maybe it's just done So the export that which is unrelated, okay It's just Yeah But anyway, so well good to know I will Close the issue with our active directory plug-in then Okay, then while we decided that export next to pass I I want to have a look at the Yes, maybe it makes sense to express the mark exporter as experimental feature, but yeah, I believe that It will always have some limitations. Yeah, so that's another question to the documentation. So Export as an as an experimental feature. This is something that we can It's our final documentation. Is that what you said? We have some or do we have to mark it somewhere in the Yeah, I do not like Experimental tongue because exporter as a feature Works well the problem that we shouldn't be setting it expectation that export that we will be producing full configurations, you know Because yeah, it's not going to happen anytime soon So what a configuration exporter does it just generates a Sample where it exports everything it can But yeah, that's it Okay, I will Put some comments about it in the documentation. I am working on and I will I will Let you know when it's done so you can review it but I Guess I Nicola, do you agree with such approach? Yeah, yeah, I fully agree. Yeah, I guess we will so most of the recent Issue I seen reported are related to to failure to export our guests newcomers really wants his feature as a as a Fast path to adopt a more configuration But those are on the other side We know that there is many limitation and so clearly you have to to express these both on documentation maybe also Within the plugin Aside the export button on the web UI, which maybe we should have some warning here to explain that this is the best effort and not relevant for your Be consumed as is my config is Better for an inspiration That's something I can have a look today to to add a note at least a tip on on the web UI so that I Know people don't read documentation nor do they See warnings on the web UI, but Better safe than than sorry And it is When somebody comes to you and grumbles the export feature doesn't work at all Yeah, and you just reference to the ticket and kind of close it Yeah, all great follow-ups for particular cases Because yeah, this thing is active directory is definitely something We would be interested to fix The problem was that it shouldn't be blocked on the release and the hitchy itself, okay, so I I Hear you Nicola when you said that Maybe not everyone will read the documentation. It still won't hurt us what if we have it there But if I if I heard you correctly you said you you can have a look about the fixing the UI part of that so yeah, yeah, I can I can check the UI part I'd be a happy if you can check the documentation side. We clearly you need both of them and yeah for concrete fix for all those issue real accurate some significant change in values plugins just like Because I guess that's the first thing that people experiment said try to export for some reason fail and what they don't know is that probably it also would fail if they try to To configure with YAML because plugin hasn't yet been migrated to adopt UI binding best practices Yeah So that's really the first thing people know about configures code is this export button as a as a way to get get fast Make sense. So Do you think somewhere around like what the where you put the warning and you mentioned the documentation? So like check documentation in repository for more details and then we Sure we can I guess I will just include a small warning tip on the web UI and Once we have some concrete landing page for for this we can just provide the link to it. Yeah Do you agree that the Warning in UI is a small thing and we should be able to do it before we're releasing 1.0. I Think it should be enough. Yeah We we can clearly do a better job that for 1.0. It's I think it's enough people understand that this is only a partial feature and So there you that your own risk and all that sort of thing. Yeah Well, that was all we had in the milestone 1.0 in the issues are there any other issues that did not end up there, but you're aware of that So yesterday we discovered one regression in the release candidate Folluding jcask configurations from the war file When you package a jcask to work so there is a pending fix from JCB And it it should be Possible to be merged, right? Well Pull request build fails, but it doesn't look to be related to the fix itself Mm-hmm, and he he yeah, like confirm that it works on his machine. Yeah, it works So the the issue is probably the one we have in all the CA problems So when it comes to PR so something was terminated in Linux Yeah so I'm okay with merging it and Who approved Oleg and I can I could see the other issue that you mentioned you need this to be merged Yeah, that one Yes, he's good for merging Okay, so I'm merging Yeah, so I didn't notice it for a while because The demo I was using was still relying on alpha 0 8 But yeah Yesterday just right Custom work package for one of his cases he discovered that for common work packaging They think doesn't doesn't work. Mm-hmm. And so we found this regression And yeah, this is just the commutation to have it so it's not a release blocker. Okay, and Is this an issue you want to work? You can just assign it to me Anything else The list of open issues there are a lot about exporter mm-hmm plus some Compatibility concerns for plugins. Mm-hmm But yeah, I don't see anything specific which would be a blocker for the release so, I Want to release I mean I can't technically but I'm I would like it to be released a Any objections plus one I'll prove that one Go for release So you You all know that we impregnum messed up our our Jenkins installation or something. I don't know we we just could not fix for some time and mess showed me how to do it manually, but I was never like changing from This candidate to release and maybe it's super simple, but can any of you guys do it? I don't want to mess up the First I don't have a release permissions. Sorry. I don't have a release permissions for this play game Oh, yeah, so I will do it. No problem. Okay, so if you if you want to if you want to review when when you deal with this Warning regarding export just drop me a message and I will be on it. Okay. Yeah, like immediately so Yeah, so you plan to release one to zero after emerging Jesus change or before that I Will I will have a look at this one thing we discussed for exports and then do some last-minute testing on my side and probably will release This evening or maybe tomorrow. Mm-hmm. I Will I will try to do some I mean try to I have Will do some testing too as soon as we have it but as I understand the You are UI change is not really something very dangerous. So we can actually start this Anytime I'm writing some code.  I just didn't want to like say it loud No, it applies to everybody. Oh, yeah so Yeah, we're releasing. That's nice and tomorrow I Fly to San Francisco and my plane Take off around noon. So I'm available in the morning and then I'm out. I guess, okay And then we're all gonna meet in San Francisco. San Francisco. Yes, ma'am Is there anything else anyone would like to discuss today? Yeah, we wanted to discuss One topic is Nikola just a second. I'll put the link actually it's in the developer in my interest So a while ago Nikola started the threat about Jenkins file runner so tool which allows to Yeah, I have a kind of single shot Jenkins instances executing particular pipeline and shutting down and Yeah, there was a threat about the integrating Jenkins file runner and jcask plugin I did some experiment to work with that and We discussed that it may make sense to have a brief demo and discussion at this meeting when you do Explain it correctly Nikola. Yes, so the point here is to have some open discussion on Configures code in a general Jenkins ecosystem. So We have this Jenkins file runner thing as that can consume configs code We also have the web packages that has is its own logics to configure some Jenkins Flavor with some pre-installed plugins and All those efforts are Not competitive, but some way trying to address the same thing. So my point here was to try to understand how those project can collaborate and How to anticipate says Jenkins modernization efforts in this direction Trying to describe the picture of what Configure code should look like in in future and So typically something I had in mind considering the limitations of the plugin manager and the way we had to handle it in configs code and The way it has been addressed by custom walker cater And also re-implemented by Jenkins Fire Runner. So my values implementation for the same the same goal I think that that's something we should Implement directly within Jenkins code itself to have some way to pre-populate Jenkins at early start phases With a set of plugins based on some declarative Description of feature we want to install Yeah, so I can briefly show how custom work package works. Yeah The list of sharing Yeah, I'm sharing my screen now So yeah, I guess do you see my screen? So, yeah, a custom work package. So custom work package. It is a relatively new project So I've started it last spring the main idea was to enable integration testing of Jenkins components and since Jenkins test frameworks depend on Warfiles the idea was to create a warpackager which would be taking plugins some self configuration logic So that everything is packaged at the as a single war file So and this is a tool which does so that so effectively it takes a number of different configurations Packages everything as a war file or now as a docker image And then you'll get ready to fly it is a beautiful package which you can use And you may see that this tool already supports the configuration as put plugin So it looks something like that So here's a demo for cask. So there is cask yaml. This is cask yaml It's a bit outdated because Yeah, it was using colorful version So I'm waiting for the patch created by JC to be integrated before bumping into the recent version but the idea that you will get cask configuration and then Yeah, there is a package of conflict yaml. This is just I think which says what should be packaged Into our distribution. So here I built Warfile and I also can build a docker if needed And here I say that I take this particular list of plugins including G cask Then I set system properties if needed. I specify cask to be included And after that it just produces a single image and you can run it pretty much the same available for for groovy hooks So there is there are also demos using groovy hooks available And yeah, this is how this tool works So In groovy hooks and it's J cask in one installation. Yeah, you can So I don't have such demos here, but I have another demo for my project So I have Configure code and in this project there is a branch 4j cask, which effectively uses both configuration as code plugin and groovy hooks and Yeah, this Approaches work together and you can do the same in custom work packages as well. I just Don't have specific demo for that. I guess Maybe I do So, yeah, there is no limitation for that Yeah, but the reason for this discussion is actually Jenkins filerunner because the Jenkins filerunner is something which goes beyond common packaging so it's not Warfile, it's not Jenkins classic docker image, but it's another packaging A few weeks ago. I added support of that to custom work packages Do you still see my screen? Yeah, I switched the focus. So here you may see that I Can just build the image and you actually in this image. I have both cask and in it groovy.  This demo uses a C2 and What it does it actually builds Jenkins filerunner. It produces a docker image So it's a ready to fly image and it's uses a key case Repository, but there is some going discussion about how we would approach this thing is to Jenkins filerunners so there is a Packager config and again, there is cask. So this cask doesn't do much now I plan to do some real world demo because currently in my demo. I just Execute this simple pipeline But yeah, what's the idea the idea that I can Just go to the repository. So there is a make file there. So make clean build Yeah, so it installs Custom work package and then runs the build So yeah, this is a developer tool it uses maven internally, but yeah, finally it will produce us Docker specification and this docker specification will be also executed so that It will create a docker file image Takes a while sometimes when you don't have cash Yeah, so what it actually does Yeah, I'll let it. Oh, it's already in docker Okay, so now we are building a docker image So you may see that it explodes work file in order to improve performance out of the box It's feature available in Jenkins filerunners. Then it also copies some stuff. It copies plug-ins. It copes a groovy hooks sets up environment for jcask so that scripts are Surveyorable and then once you package it is built what you can do So just Lost the window again. So here you can just go to the Yeah to the demo And Oh, yeah, here's an example of command line. So effectively I just used use the produced image and I can execute this image. So it's ready to fly build it includes this Jcast groovy hooks system properties plug-ins. It's a static image. So everything is bundled and Kind of preconfigured There are some Performance tweaks applied but effectively Jenkins starts up and executes your pipeline and produces output to CLA So it's what the Jenkins file runner does in my case. I just package the docker image properly so that It runs Weekly and then it uses configuration steps so yeah, that's the idea of this prototype and It uses jcask and configuration as code in general. So I think it may be interesting to this audience Well, it is I'm definitely going to to try it. So You're okay with Sharing the demo with anyone who's interested. Yeah, it's public. Okay. Very good. Oh, I really like the idea, but so we started with We started with explaining the issue like we Implement the same solution in different places if I'm if I understood it correctly And then you have this demo So I'm wondering if this this prototype is is kind of solving the problem or or it's it's just next to the problem So it produces static images So that yeah, jcask itself is a really nice tool It can be used in different contexts But what I target in my Jenkins instances, I want to have static configurations So I don't want to have admin on my instance at all and I want everything to be kind of configured So that's why I try to package everything into docker. Yeah, this demo customer Yeah, Jenkins config works in pretty much the same way. So it produces a docker image We use everything bundled as a configuration and then yeah, it's what gets shipped as a single instance So that's the idea. Okay The plugin installation is being Done by the install I can say it's script In the case of Jenkins file runner. No, it's been so effectively a word custom word packages does is that it packages everything Into a word file going to docker. So it doesn't use plugins txt and it doesn't use Common docker image logic to do that. Okay, but yeah, it does everything internally Why it's own tooling now? Yeah, so I actually don't really care if it's using the Normal or the most common docker and plug-in solution what I'm after is if you want to have If you want to update plug-ins version, do you have to rebuild it and have yes, you have So this is a static image. So the idea that if you want to update Configuration of plugins you update the repository run through whatever continues delivery a process produce new image and then replace the image So this is an approach Yeah It's not applicable to 100% of cases, but yeah, this is how I would prefer to manage my instances Yeah, no, I know like I've heard about some customers that it's not possible for them to have Jenkins down for one minute even but I'm pretty sure those are very specific cases and what you're showing now is Used to be very interesting and we're checking so Well, thanks Yeah, so that's how it works Yeah, as I said, it's a kind of underdevelopment tool It would it works And then if it back will be appreciated Yeah, by the way, this is Docker file for Yeah, it's for configuration of school demo. So you may see that nothing really interesting. He just it's Warfile and Yeah, everything is packaged into the warfile including plugins and jcusk. That's why there is a resource loading for Jenkins file runner is a bit different because we need To comply this jinx file runner structure. So plugins I extracted Jenkins file Binary cells are produced. So the docker file. He's a bit different. But yeah, it also works Okay Nicola, what do you think? Yeah, that's a first. Thanks for the demo Right, so yeah, my my point here was to ensure that all those know but this project and Understand that with such tools Some of the imitation we have in configs code. I remember see how we had this discussion on managing Unbound viable and system properties and all that sort of thing in configs code and and define the boundaries of the project And then we here we have a sample to get one step further So I think this is very interesting. So As you say, this has been designed as a tool mostly for developers and as and testing purpose but probably the scope could be larger and Just be some more generic way to to to manage Jenkins Something I heard a few years ago about sonar source Is that they gave up support for all the service and gene and Only support running from common line just equivalent of running Java that are checking the wall And they stopped supporting deployment on ways for gbos and whatever because that creates lots of limitation in what they could do if they only have one target platform and And and with this package or and the feature it allows Here you have these samples to package could be hooks to enable system properties manage plugins solution All that sort of things. That's something that we can control from such a tool Without having to make some significant changes in Jenkins core and This opens some new opportunities So today if you have to just pass an environment viable to Jenkins You have to update a dozen document to explain how to do it on on Windows on Linux installed a service when running from common line when running within gbos when running from web sphere and so on and so on And I really like the idea that we have such a concierge document to describe the full service of the Jenkins master and Also being able to package in the docker image From my point of view that's some vision of what the future of Jenkins could be As as a standalone system where we can control everything at once Cool. Thanks for this feedback So, yeah, this project Is pretty much aligned with other activities we were doing so for example, there is incrementals delivery flow Of course custom work packages supports it as well So users also do not need to wait for patches for being released. So here use Jenkins file runner from the repository, but actually for every plugin you can define an incremental solution or just sources to be built So it also makes the thing pretty much flexible and actually if you don't like What's packaged in Jenkins core? There is also a way to update that so I guess this demo is a bit obsolete But yeah, what you can do that you can actually patch Jenkins core at libraries So for example, if you need a library to work for this Kubernetes resources You can just add this library to work package and it will be Available in the class loader as you may see that there are some bad idea warnings here, but yeah, generally it works and Yeah, pretty much the same if you want to replace any Library, it's also possible now. So you can rebuild your work file is a part of the deal flow You can add more resources. You can package everything. So yeah Generic work around for any feature missing in Jenkins for file And yeah, it works extremely well for packaging the demos So for example, there is external login the demo for elastic search. I also package package data with customer packages So a bunch of plugins which are not released then some configuration as code Self-configuration mostly so something like lockstash config and then it is docket compose you just get an instance Which includes elastic search and Jenkins everything runs Out of the box and the login happens externally and yeah everything is Written either in YAML or Guru so there is no VTXML patches So that's how it works Still under development But yeah, I think it may be useful in some cases So I'm pretty sure it can and well, I I don't want to give any feedback without actually looking at it I did really but I will I will definitely do that and I hope some of my colleagues From work will do the same. I'm pretty sure we'll find a lot of ways to use it. So Things are like It's not only thanks a lot. It's actually thanks Nikola. Thanks Kiki and others. Yeah, for example Mr. Jenkins file builder a pretty much Took it from the repository without any patches. So there was some voodoo magic around making it working But yeah, generally I just took it and it works So, yeah, there's a kind of combination of multiple tools because jikas as well Right Yeah, so looking forward how it plays and yeah, of course is very recent announcements. Yeah, there are Definitely some of huge exploratory work to find how all these two tools map together Yeah Yeah, that's why we go to the contributor summit exactly. Oh, I was just if well, this is my first contributor summit my first Jenkins world a Should we prepare something for this contributor summit or should we just assume it will? So you definitely you should prepare something because Yeah, there is an expectation of something like jikas start to submit in the vehicle of the summit that that that thing I'm aware of but Yeah, it's like some demos or what do you have so it's now I'm pretty sure it would be interesting audience to see yeah, right, so they will be I Don't remember how they called but after the main part of the event they will be Just some opportunities to pitch projects and to show small demos So they will be something for two hours for that and it will be on conference format So everybody who is interested can propose a topic and discuss that So if you have any ideas in mind just add them there and Just a logistic So will it happen? One presentation at the same time at the time or will we will we divided into smaller groups? Depend to I think it depends on the number of interested people So I don't know how exactly it's going to happen this year, okay Well, I don't have anything else for the meeting today We have five more minutes If Another topic that you want to discuss Actually, I had one topic about the contributor summit So they will be built or visa so something like to our discussions at project tables Currently we have cloud native seek table and also Equal to table is a separate one I wanted to make sure that this approach we want to follow I Think there's no topics to discuss Table I think you have things to talk about when they have the receipts and I really hope we will meet some Some people that are trying to use configuration as code so Separate in my opinion is a right way to go It's fine with me, right? Oh, no It is I just really received the stickers I just got it I just got a new laptop and I lost all my stickers, so I guess Maybe you can put all of them But let's see like I would like to give other people the opportunity to have some That's great Right so then see you in San Francisco. Yeah Thanks for the meeting. Okay. Thanks. I'm stopping the broadcast. Bye


Heading out on a business trip soon. Well, don't dread that time away. Rather look at it as your next adventure. Stick around to see what I mean. Hey friends, it's Leanne and I'm just back in the office now after quite a lengthy business trip. I was on the road for 10 days away from my home, my home office and my family. So I really needed to find things that connected me to being at home or at least being part of my routine. So the first stop on my business trip was Halifax Nova Scotia and I went for a run in this beautiful city. And running really connected me to being at home. Even though I was running in an unfamiliar place, it really connected me to things that are authentic to me. And it actually inspired me to do this post because we all travel for work, especially for in the meetings industry. And it can get quite tiresome. And we look at it as work. And I'm hopeful that if you do a lot of business travel that you don't really look at it as work, but rather look at it as an adventure and something that you can check off your bucket list with each destination that you hit. I encourage you to find your thing. And when you're in a destination, I want you to do your thing. Now your thing might not be running. I was very lucky. I got to run into destinations this past trip. I went to into Halifax and then into Toronto and just beautiful, just beautiful summer weather in both destinations and it really energized me. But if running is not your thing, maybe it's visiting vintage record stores, or perhaps you like to visit a local brewery or local museums.  Whatever your thing is, make it a practice of doing your thing when you're away on business travel. I think it'll give you a different filter on that trip. It won't look so much like business, but rather it'll look like an adventure and an opportunity to to hit up a bucket list thing when you're in that destination. So friends, do you have a thing? Do you have something that you like to do or explore when you're traveling for business? I'd love to hear what your thing is. Just comment below this video. And friends, if you don't yet have a thing, I encourage you to find something that you can start doing when you travel for business. I think it'll really energize you and give you a sense of belonging and being at home again instead of a foreign destination away from your friends and family. To get caught up on all my Two Minute Tip Tuesday videos and productivity videos, check out the link to my YouTube channel in the comments below this video. Friends, here's to staying healthy when you're on the road. Hope to see you soon. Have a great week. Bye for now.


I'm Dr. Rishina Hoda from the University of Auckland in New Zealand, and today I'm gonna be talking about some research to do with agile, specifically to do with the journey of becoming agile and how that might be different from simply doing agile. And that kind of fits in really well with the agile mindset idea, which we've been hearing about throughout the day. So hopefully you'll get some good insights out of this and there's also an interactive component towards the end of the session, so stick around. Okay, so before I get into the talk, there's something I need to get, sort of something I need to acknowledge, which is what's happened in Christchurch just a couple of hours before I took my flight out to agile India. I'm not gonna be able to say a lot about this without getting emotional, so I'm gonna stick to the basics, we all know what has happened, but I would like to focus on the positives that have come out of this, which is the huge support, the love and the generosity of the people around us in New Zealand as someone who is there and can feel it in the true sense. I can tell you it's been amazing. So one of the things I will point out is the fact that the Victim Support Official page for charities has raked up in excess of six million New Zealand dollars, and to give you some perspective, there are only nearly five million people in New Zealand. So that's pretty amazing. Our Prime Minister, Jacinda Ardern, has been an amazing role model at this time, standing up for us, not sort of, you know, beating about the bush, actually just taking stands and being really clear and calling people out and calling the act out for what it was. So I would just like all of us to maybe just take a moment of silence in respect for people who have lost their lives in this absolutely horrendous strategy. Sorry, and then we'll get on with the talk. You can keep sitting if you want to. Thank you very much. All right, so this is New Zealand and I love it. I mean, this is gorgeous. Look at it. Why wouldn't you want to be here? So this is the glowworms. This is how we do our rugby, although I'm more of a cricket person being originally from India. You can kind of understand where that's coming from. This is Hobbiton, which for people, how many Hobbit fans in here? Yay, so there's the set. The original set is still intact. You can go there and visit it and look around. Spoiler alert, you can't actually go inside the halls. Those are fake, but nonetheless, it's an awesome experience. This is the University of Auckland. In Auckland, this here is our clock tower and you will see how beautifully the two architectures, the old and the new meet in our university. This here is our engineering faculty and we've got a brand new engineering building coming up which should be finished in time for next year. Cool, so what's the connection between me and Agile?  So I go back, me and Agile go back a long way. I did kind of my PhD on the topic, specifically looking at the self-organizing team aspects and I've been studying and researching the human and social aspects of Agile for a really long time. Most recently, I now have two students who have graduated with their PhDs on Agile topics, one around Agile retrospectives and the other one around the role of the Agile manager and I've got two more currently at the moment who are looking at other Agile topics. So in this, all of this time, I've published over 60 research publications on the topic and I'll be talking briefly about how you can access them. And of course, I teach Agile, so I introduced the Agile course at the University of Brooklyn, that's been running in collaboration with the local industry for some time now, really well. Okay, so I thought I'll start off by asking on behalf of you to myself a few questions that people are always thinking about but never quite sure to ask the researcher. So here are some questions. How much do you earn for each research paper? You were thinking it, you were thinking it. Okay, here's the answer. Nothing, zero, zilch. It's ridiculously awesome because we do it as part of our job. And then the next question you might ask is, well then how come it costs me to access your research? And the answer is publishers, period. I'm not gonna say more about that, okay. The entire community of doing research, peer reviewing research, publishing research and getting it out there is voluntary and free and that's what we do as researchers and the access part is controlled by the publishers. Now, that's not all bad news. So if you want to access my research for free or other people's research for free, you can do so. So for example, what I do is I put all my publications up on my website and it's free to download, okay. And a lot of other researchers are increasingly doing this. So if you don't feel like you can't access it or it's too pricey, you can always try and go to their own individual websites and see if it's available for free. Now you might be wondering how and what am I doing this if publishers are supposed to be charging you money for that? And the answer is there's something called open access which is very similar to open source but for research. So you're trying to make science and research open and accessible as possible. And also the fact that we can share pre-prints of our paper which means it's the same content but it's not fancy, it's not been put into the publisher's sort of format. So if you're trying to read it in a draft version that's what we do, we just, it's the same content, right? So that's all available and this is not just me as I said this is most researchers out there so do feel free to sort of tinker with their websites and try find stuff. All right, so today's talk is based on a paper that I wrote in collaboration with Professor James Noble from the, from Victoria University of Wellington. And we wrote about the theory of becoming agile which was presented at the International Conference on Software Engineering 2017 in Buenos Aires and it also did receive one of the six distinguished paper awards at that conference and for me it was personally really, really awesome because it was, I've seen the whole journey to putting in my first paper about agile, getting reviews around what is this fluffy stuff to going all the way 10 years down the line and receiving distinguished paper award on the same sort of topic which is a full circle for the research community as well which is quite nice. All right, so I'm not gonna go into the details of the research method, this is not the audience and I do recognize that but I'll briefly share that it's called grounded theory and the reason it's called grounded theory is that it's an empirical method that's focused on practitioners and the industry. So we're really interested in looking at how things happen in the real world, not sit in some lab in a university and think up stuff. So we actually go into the industry, talk to people, observe the practices and that's why it's grounded from the bottom up based on how you do it, right? And it's a theory, theory is not, it's not your E is equal to MC squared kind of theory but it's a theory in terms of these are the findings that we finally come up, these are the common patterns that we find when we talk to a number of people across different domains and also a set of hypotheses which you will see in a minute. So this is my favorite slide because this is my state of mind before and after I finish a project. So when I start a project I have a whole bunch of questions, right? And it's a clean slate of, gosh, how does this work? So some of the questions driving what I'm about to present today were these. So how is it that teams do become agile? What's that journey like? So it's a really broad question. The other one was, how come some teams are more agile than others? What's up with that? Like, my agile is more agile than your agile. Like what's going on there? And then there's also the fact of is it just about the software development practices but it doesn't seem like it's just about the software development practices. What's going on? What are the different aspects that change in this transition? So that's kind of where it started. And of course what you do is as a researcher you look at what other people have done before so you're kind of not reinventing the wheel and in that what I did was I found that mostly the current understanding around agile adoption has been that it's a one-off sort of process or a one-off event even in some cases where you're going through a step-wise approach to becoming agile. Step one, do this, step two, do that, step three, do this and boom, right? So a lot of the research-based models were focused on getting to agility or to becoming agile by step perspective. And then also the fact that most of these models focused on either really the high level abstract value so they're talking about things like speed, flexibility, adaptability and you're not quite sure what that really, how can you quantify that or even understand that or the really low level development practices like, all right, let's start with prior programming or let's try TDD and other stuff. But as an individual we're starting on this journey. That's a mammoth gap to try and reconcile between the high level values and the low level practices like what's even going on? So this here is the theory of becoming agile. Just notice the colors look a bit weird so we'll see what the other slides look like in a bit. But this is the overall theory of becoming agile in a model, a picture or a diagram fashion. And we've got five dimensions that I found teams transition through, okay? So these are software development practices. That's a no brainer. This is one of the first things that happens. There's also team practices, the management approach, reflective practices and culture. So we're gonna break that down very quickly. So I'm gonna get straight to it. And oh, by the way, the edges that you see, those are the hypotheses and we'll get to that soon enough. All right, so what do I mean by software development practices? This was a little bit tricky to disentangle from the team practices, but I've given it a shot.  Are they still kind of the status reporting kind of meetings? Are they really your deep level daily standup like Shane mentioned before? And artifacts, are you using things like the Gantt charts or quite heavy weight documentation versus lightweight scrum boards and things? So very basic agile stuff. Now what I found was that different teams or different individuals were at different levels when it came to this transition. So if you were like for the teams that were really just starting off, a lot of these software development practices were very traditional. So what I'm gonna do is I'm going to bring in some of the quotes from the actual practitioners so you get a sense of what is it that I've been hearing as a researcher. And P numbers, it was a P25 or P36 is just anonymizing for confidentiality reasons. This is why people tell me all they tell me because I don't name them, right? So here's an acknowledgement of a tech lead in India and they said transitions happen slowly.  So in the beginning it's very much traditional software development. You don't just turn agile overnight. The next one what I saw was teams that can be said to be in a hybrid state. So they're kind of getting there but not really there yet. And some of the things to highlight in that case is people are resistant to changes. So when it's new it's exciting but when you have to kinda do it every day then it's like what did I sign up for? So some of the things you might start questioning again. And it does take time and it takes a while to get into the pattern and really absorb those practices. And finally when teams have embedded the basics of agile software development practices and that's when I'm saying they are further along on that maturity of the software development practices dimension and this is where you have a consistent use of the practices and you're actually deriving value from the use of that practices. So you've really embedded that into your culture and organization. So that one actually is one of the most intuitive dimensions we all kinda expect that. The other one was team practices and this is almost some of the teams Wednesday start transitioning into agile. They're like not sure I bargained for this but okay. So these include things like project management, activities like requirements, specification, estimation, clarification. Remember as traditional teams most of the time this was done by the BAs, the managers, that's right. And now suddenly the team is like whoa, we can do this. That's pretty cool, right? So that's what we found in this case. That's not me, I swear. And the other aspect is task management which is delegation versus self assignment. In fact in some ways this was a hallmark feature of self organizing team with their ability to self organize. So if the team was quite new to transitioning on the team practices dimension then they were largely manager driven, all right? So the manager is still doing most of the requirements specification for them or the facilitation or being the face of the team to the customer and definitely delegate still delegating tasks. So on this dimension you're still manager driven as a team, right? The next one was manager assisted. So you've moved on from being manager driven now you're kind of either looking to your manager for help or your manager is offering you help actively and hand holding a little bit to help you to get to the next point which is becoming more and more autonomous as you move on on the team practices dimension. So here's a development India saying oh we do get assistance from our scrum master to assign the task in the future we will be doing this ourselves. So there's a self awareness we're not there yet but that's the goal where we finally wanna be. And then finally for teams and these were rare to be honest and it because it takes time these are more mature teams that were further along on the team practices dimension and this is where you have a scrum master in New Zealand for example saying our teams are exclusively self assigning. They just work on their own in terms of the tasks but also senior development India saying we allow direct contact to the customers. So that you are free to talk to your customer you don't have to go through your scrum master you don't have to go through your BA to be able to do that. So that's the team practices dimension. I hope you see how it's different from the software development practices dimension. Another one which was really tricky to sort of disentangle was the third one which is management approach. Now I'm gonna say this I think honestly team practices and management approach are two sides of the same coin that's called self organization. You cannot have self organization if both of them are not moving in the same direction. So this is almost focusing on the same kind of things which is the management practices and customer collaboration but from the manager's perspective is the manager ready for it. And when I say manager I mean people like the scrum master your title may be a product owner your title may be a project manager, product manager all of those titles that we carry but typically it's your practical role is to facilitate the team on an everyday basis. So what kind of a manager are you? Now how many people managers in the room? Think about your management style as we're going through this and for others who have or know managers you can think about their management approach. So of course the beginning for teams that were starting to transition towards agile the management approach was of the driving kind. Okay so very traditional. I'm the leader, I'm the saint on the stage kind of thing I'm gonna tell you what to do here's even if it's agile, right? I'm gonna tell you what to do and that's fine that's kind of where you need to start because you can't just shove a bunch of people in a room and say go self organize, right? So that's that hand holding period right at the beginning was kind of important. So you've got somebody here saying all right the manager is the first point of contact between the product owner and the team and that's fine. When you were further along the issue is if you get stuck there you don't wanna be stuck there so the next bit is then adapting. Your management approach becomes adapting which means you have real good sense and feel of the level of autonomy your team is ready to accept and assert, right? So this is where you differentiate between you may be ready to give that autonomy but your team may not be ready to take it yet. So in this sort of hybrid state the managers approach is really one where it's adapting to the needs of the team and individuals within the team that are autonomous to different levels. So if somebody is really happy to run with it and self assign their task you let them do that whereas some people may still need your help and assistance and so you need to sort of be cognizant of their needs and adapt your management style. You can't have one management style for all at all times. So that's what I found with teams that were kind of in the evolving process and that teams that were sort of further along the management style moved to becoming empowering in the true sense and that's because the team also was ready for it. So here's a scrum master in New Zealand saying oh a self organizing team is something that wouldn't notice if I disappear. And it's just running on an autopilot I'm really happy with it. But here's a senior developer in Australia pointing out look actually that does not mean that you don't need no stinking managers kind of approach. That's not true, you still need them and some of the reasons you need them is for things like cutting off interferences from the outside, conflict resolution, sometimes people tend to revert to old ways of working all of that needs to be sorted out and facilitated. But so that's the sort of pinnacle of the management approach dimension is when your manager's approach has moved on to becoming empowering. Next one was reflective practices and we just had a lovely session just before on retrospectives as a by Mia, seeing at the back there. Talking about retrospectives as a way of reflection. So one of the interesting things I saw on this dimension and the reason that it's been put aside as a dimension on its own is that this was the hardest one to get right in some ways, okay? It was the hardest one to do in the true sense not just lip service, okay? So for newer teams that were new to the concept of reflective practice, their reflective practice was really limited. So you'll see it from this quote here. They say, all right, we might figure out how the whole team lacks a particular knowledge area. So we have got training session but the problem is time consumption. Okay, so you can see the attitude towards reflection there is you recognize you need the time for learning and reflection but it's still seen as time away from the main stuff which is implementation, right? It's stuff that is taking your time out. It can't possibly be good if it's too long, right? So the approach is not very mature yet. So that's the limited approach to a reflective practice. Next was a focused approach. So if you were further on that dimension you're kind of focusing on one process or practice at a time and starting to hone that a little bit. So for example here they're saying, all right, we've decided that we want to introduce planning poker and through their retrospectives they are starting to really track how they're doing with that estimation strategy and if it's working well for them. So it's really focused. It's not a full on reflection practice yet. And for teams that were further along on this dimension it was embedded. It was part of their DNA. This was just normal to be reflecting. It wasn't time taken out of work. It was part of the work, right? And you made time for it and everyone was comfortable with it and you recognize that this was truly important. So and that's supported not just by what the teams feel but on the organizational level by the initiatives from the organization. For instance a developer in India said we've got initiatives from the organization where if someone's learned a new technology or something they can come and teach it to the rest of the organization. So the organization, the company has set up a culture where why it's okay to take time out of implementation and spend time on learning and reflection and that's part of the culture. So that's the extreme sort of end of this particular dimension. Next up, the final one is culture. And as a researcher, this was one of the fuzziest ones to grapple with. It's like what is culture? And the sort of final definition that I came up with and I still need to sort of go into the details over time. I'm sure I'll do that. But for now my operating definition is this. It's the work culture or the operative culture is a combination of the individual's mindset, the team culture and the organizational culture. And the reason I came up with this is because I've seen two teams or multiple teams within the same organization that have different culture and different norms and values. So organizational culture as a whole, you cannot paint every team by that color, right? Every team has their own unique interpretation of that and then you come to the individual. Even within the team, you have individuals who have different set of norms and practices. And so you have an individual mindset that you need to align. So that's sort of this big mushy combination of these three is what I call culture. As I said, I'll need a bit more research to really sort of define that a little bit better, but for now that's the operative definition. The culture for teams that were quite new to Agile was really hierarchical in that you have, this one's really telling you need approval from the managers to follow it up with the product owner who in turn follows it up with the client. So you can start to see the communication channel and the information flow is really, really hierarchical. The next one was evolving. So again, that middle intermediary stage where it's evolving. So the communication hierarchies are being broken down but they're not really there yet. So what does being there yet look like where it's really open? Okay, so people can rock up to junior developers can rock up to the CEO with a new initiative idea and they're actually taken seriously. All right, so that kind of a culture of psychological safety and all of that good stuff where you are really feeling comfortable and able to practice the Agile mindset in a true sense. All right, so from there, derived a few hypotheses and some predictions of how might things go for teams that are starting on their Agile journey. So this, as I said, the software development practices is most of the time for software anyway. I mean, there's Agile beyond software but that's not what I'm talking about today. So within the software realm, the software development practices are the first to start transitioning and that's obvious because that's probably the first reason why you even thought of taking up Agile. Right, that's because you wanted to change how you do your software development. So that's the first one to start the transition. The team practices and management approach, as I said before, there are really two parts of the same coin. Both of them need to move towards self-organization if this is to work. Reflective practices and this is potentially controversial is going to be the last to mature and that's what I can say on the basis of my research because I've seen teams, it's not to say don't do retrospectives, by all means do retrospectives but by the time you can really get full value out of the retrospectives is when your software development practices dimension is further along, your team practices, your management approach is already starting to mature. That's typically when you start to get the real value out of reflection, when all the other ones are further along in your journey. As I said, the culture dimension is a mix of the individual, the team and the organizational culture, not just one or the other and it is indeed the most critical dimension that influences all of the other dimensions and that is to say if you had a agile, conducive culture at your organization, all of your other dimensions are probably gonna move faster and smoother. All of your other transitions will happen quicker and smoother and vice versa. So if it's not conducive, then your team may be wanting to become autonomous and it's not gonna really happen or happen really slowly. So that's one of the most telling and most important influencing factors. Okay, so the main takeaway here, the big sort of difference between becoming agile and doing agile is we're wanting to move away from thinking of agile as a one-off sort of stage progression of practices with whether it's software development practices or those abstract values. That's really what I call doing agile.  You're not looking at the holistic picture. Whereas becoming agile is when you're looking and acknowledging the fact that this is going to be holistic, it's going to be complex and it's going to be ongoing. You cannot really define an end point. All right, as of first of Jan, we're all agile, right? It's a journey, it just keeps going. So that aspect is becoming agile. And an example I'll take here is of child development. So as a mom, I mean we and as parents or as people who have kids in their lives, you know that you often get into issues of comparing two kids of the same age, right? So you've got two five-year-olds or two five-month-olds and oh, mine's walking, mine isn't walking yet or he's talking and he's not talking yet. And that's not the true sort of marker for progress or growth just because they're both five months old. And you can take that to the agile teams and say just because they've both been practicing two teams for five months or one year doesn't mean they're both there exactly. Why? Because we can't just judge them on the basis of their physical growth kids, for example. There's a whole lot of other things going on. There's the social, there's the emotional, there's the cognitive, right? And similarly for agile teams, it's not just the software development practices. Oh, I know pair programming and we're sweet. No, there's all of these other dimensions that they need to transition across. And that's why it's so important to have that holistic picture. This is another view that's really, really light. It can't just, okay, that's meant to be an iceberg. So right at the top, you've got doing agile as just looking at the software development practices, for example. And underneath, you have to use your imagination here because the font's really light. All of the other stuff that also needs to transition if you want to really become agile, not just be doing agile, right? So all of these other dimensions. Cool, so I've got time. I managed to finish the theory part. So in theory, there is no difference between theory and practice, but in practice there is. So we're gonna try and apply this theory of becoming agile. And you have to bear with me. This is the first time I'm gonna be trying this out as in an application of the theory. So if this doesn't work, I'm gonna do what Deb did or recommends around the failure bow to be ready for it. Thank you. Okay, so with being handed out to you, my attempt at trying to make this theory practical, yeah? And while that's going around, I'm quickly gonna walk you through this. This is an exercise I did with a couple of teams that participated in the research. What I did was I used a spider chart or a radar chart to track their progress or their current status across the five dimensions. So you will see you've got five dimensions, the software practices, team practices, management approach, reflective practice and culture dimensions, yeah? And there's blue is team one and green is team two, that's just one example. And you can see these are two teams in the same organization. One of the things I'd like you to notice is that culture is not exactly aligned even though they're in the same organization and their reflective practices are really far apart. So one of them was further along on their reflective practice than the other. So for the moment, what we're gonna do is, I would like you to, I'm sorry if not everyone has it, I was prepared for a smaller group and there was, you know, very graciously, a lot of interest and we've been moved into this bigger room so I apologize if there's not enough printouts. But on the front half, what you will see is the five dimensions, all right? So we're gonna take five minutes and for each of the dimensions that's about a minute and then rank your team, or you could do it individually, but think about your team perhaps, rank your team on how they're doing on that particular dimension at the moment. Now if some people are from the same organization of the team, they might wanna team up and do this together. So for example, the software practices dimension, if you thought that you were really iterative and it was really agile and your team meetings were kind of getting there, not really getting the essence of agile yet, you might give them a five, which is a hybrid, a 10 for where it's on the extreme end of the dimension and a one if it's really still traditional. One left, I've got just this one, but you can have it. No worries. So there's a little bit of maths to be done here. If you're in the far end, which is all 10, under each dimension there are five questions, right? Five aspects. So you can score between a minimum of five to a maximum of 50. Okay, I see people turning their pages. Are most people done with the first half evaluating your teams? Yes? Move on to the next one. Some people still doing, but just give them maybe one minute if you can refrain from the visualized part, that would be awesome. Okay, cool, is visualized. So I've used that, remember that radar spider chart. And what we wanna do is if you've scored on a particular dimension as between five and 15, that's a low. So we can do rough estimates here. You don't have to be exactly accurate. But between 16 and 30 is a medium for that particular dimension. Between 31 and 50 is a high for that particular dimension. So what you can do is you can chart out, say what your software practices look like, team practices, management approach, reflective practices and culture, and then just connect them through the dots. We'll get a picture of something like that. And that will show you which areas you are really doing well in, whereas which areas need a little bit more work on. Do you wanna connect the dots? Awesome. There's one other way to visualize this in terms of the journey of becoming agile. So I'm gonna take the theory diagram we saw earlier, and what you can do is you can sort of color out the areas in terms of percentages of where you are in your journey on that particular dimension. So as an example, if you think you're about intermediate in your software development practices dimension, that's about half of it.  If your management approach is actually fairing a little bit better than the team practices dimension, you can reflect that. Same for reflective practice, I've shown that as one of the most needing a lot more work and then culture similarly. So you can shade it out for your current standing of your team at this point. Awesome. So as you can tell, this is something you can do again with your team in three months. You can do that again in six months time, a year's time to see how you're tracking on those dimensions. At this point, would anyone like to share their experience of evaluating this and charting out the journeys of their team? And I can tell you from where I'm standing, every radar chart is different, right? And that is why every agile team has a unique experience of becoming agile. It's not just the one step, two step, boom. So do people wanna share their thoughts on this process?  So Shane said a useful tool for initiating a conversation with the team. I couldn't agree more. So in fact, a good reminder for me to sort of comment on the fact that metrics, all metrics are really starting point for conversations, right? Any other, yep. Quick and simple, so a really good quick way to assess where you'll pick it up really well. Yeah, so the main thing of doing this is like to ensure for the managers or the leaders to ensure that this is a psychological safe environment. Because if it is always a kind of goal-driven, people will kind of tend to keep always high and which is not willing to reflect the right picture. So it's very important for the managers or the leaders to tell them it's always good to fail here to show the transparency because then you will understand like where you are standing in terms of what this looks like. That's right. So that will give you the right view. That's an absolutely excellent point and it reminds me of a similar comment I got from Scrum Master, I was sharing this with and what they said was for new teams in particular, one of sort of a related concept is they don't know what the whole journey is supposed to look like. So it's difficult for them to tell where they are which means for newer teams it's probably best if your agile coaches are facilitating this because they've seen all a lot of teams go through this process and they can help you a certain way you are right now. And your very critical point about psychological safety because this can easily turn into something around oh, we're the best or worst case within the organization my team is more agile than your team, right? But that's not what we're aiming for. So indeed the culture around that needs to be conducive. Thank you for that. And the last bit, what we're gonna do with this sheets of paper, if you wanna keep it by all means you can keep it but it would be awesome if you can come up to the front I can take pictures of it for my own record or the other way around you can take pictures of it and give me the printouts back. Please don't forget to put your job title on there because it'll give me a sense of how teams or people, team members are perceiving this versus for example managers are perceiving this and how that might need to change. So last bit is would you consider using this as an assessment tool for your team? No and that's fine, yes as it is or yes with these improvements. So welcome your comments on improvements. And as I said as a researcher sometimes it's really comforting to come up with a theory and get an award for it and let it stand there cause it's so beautiful and untouchable. And then to step out of that comfort zone and say well actually it should be helping people so I'm gonna push the limits and try and see if it's actually practical. So that's what I've done here today and I hope that's yeah I really welcome your comments so please do make sure you give me some comments on that.