Right, welcome back to the final session of the FOS in Research part of this mini-conference. Our final presenter is Julius Baxter, who's an Australian spy currently on mission over in Stockholms, where he's, Alias is a student studying a masters in the system on a chip design. So I'll hand it over to him and we'll learn a bit about the open risk platform and stuff. Yeah, excellent. Thank you. Hello. Yes, my name is Julius and I'm here to talk about the open risk platform, which is hardware, silicon kind of level stuff. So hence the chip. Just quick outline, I'll do an intro, explain what the project is, then I'll talk about why I'm talking about it, which is the recent work we've done on the platform. Then I'll talk about why I think it's a worthwhile or useful thing and why I'm here presenting it to the, like the open source crowd. And then I'll talk about what we plan for the project coming up and hopefully get some questions in at the end. But who am I? I'm from the Gold Coast and went to UQ, did a bachelor of engineering and afterwards through a recommendation of someone in the department there, I went over to Stockholm to the Royal Institute of Technology in Sweden, or Kungliga Tekniska Högskolan, which explains the acronym. And I started working there in April 2008 while I was still doing the masters for a company called Orsoc. And I'll explain about them in the next slide. I primarily work with HDL, so hardware description language, Veralog is my main weapon of choice. I do a lot of low level software stuff, assembly, C stuff. And then I put together lots of systems with make files and bash scripts and stuff. So I do a lot of that as well, to synchronize tools. And I've worked basically on all levels of the open-risk platform from the parts of the tool chain port through to the RTL. I'm the main contributor and maintainer of the RTL for the open-risk chip now. And all the way up to software and UC-Lib C stuff. So I've done a lot of stuff with it. So Orsoc, my current employer, they are a consulting company. And they make open-risk system on chips, I guess, which explains the acronym. And they use that as a platform. So people will come and say, oh, we need this done and we'll use an open-risk processor on an FPGA. Like I have here today, hopefully I'll get a few minutes to do a tech demo at the end and just show you it booting the kernel and doing NFS and stuff. But yeah, they do, so they develop products based on these boards. They also run the open-source hardware community called OpenCourse. I'm not sure if many of you have heard of OpenCourse, but they are, I don't know, what's the equivalent, like SourceForge or something, where they host projects for you and they have a bit of a directory and the emphasis is on open-source RTL level kind of stuff. So open-source stuff that you'll either put into a silicon chip or on an FPGA. So they bought that and I'll give a bit of a history of how they came about to having that in the next slide. But yeah, they do platforms, debug cables, things like that. Yeah, we have a question, but I believe we have to wait for the microphone. Sorry. Just following orders. So when you say RTL, is that the same as HDL? Or is it a higher level of things than HDL? RTL level is basically you're describing what's going on on the clock edges. So you're describing the transfer of signals between different blocks of logic. And when you do RTL design, you can do it in a more abstracted way and hope that the compilation tools or synthesis tools as they're known will infer the tricky stuff you want. Or you can go down and you can describe this as an AND gate and we hook it to an OR gate and we hook that to a flip-flop. So there's a range of abstraction you can have within RTL design with HDL. Maybe I'm not just explaining this correctly, but HDL is a language and RTL is the kind of extraction level at which you're designing. So yeah, just talking about the relationships of signals and some timing information and that as well. An introduction to the OpenRisk project. So OpenRisk stands for Open Reduced Instruction Set Computer Computing. Currently the first implementation of it is called the OpenRisk 1000 and that defines a 32-bit microprocessor architecture. So things like the instruction set, what all the special registers do, what they control, caches, MMUs, bus, or no, not bus interfaces, that's not really part of the architecture space, but then a software ABI as well. And we have, sitting in our repositories, a simulator, so like a transactional level instruction set simulator, an actual RTL level implementation. So that's the thing that you can take and then put into a synthesis tool and run it on your FPGA or do a full ASIC flow and send it to Taiwan with a few million bucks and they'll send you back some wafers. We also have some tools, full GNU GCC toolchain port and NewLib, UCLib-C and the Linux kernel as well as various other real-time operating systems. And a brief history of the OpenRisk project. It was started in 1999 as a bit of a university project by a Slovenian guy called Damian Lampret. And over the next couple of years they got it up and started a little bit of a community around it who developed other things like peripherals that would also go into a FPGA. And if you're not 100% on what an FPGA is, it stands for Field Programmable Gatoray. So it's just a set of logic that you can go in and you can define what is connected to what.  So they targeted it for that at the beginning, but they did do ASICs with it. In 2003, I think it was the FlexTronics company got on board with them and funded them for a full ASIC flow and they fabricated it and demoed it and it was used in a couple of products. So it's proven in industry and it's proven in silicon. But then the core of the developers there spun it off in 2005 to their own company and basically dropped all development on the OpenCores website and supported the OpenCores website. So in 2007, they said, look, we're going to sell it. And a couple of engineers from FlexTronics who had worked with it and knew the potential of it, they said, well, we'll buy up the website and we'll support it. And that's what ASIC do now. They build platforms and systems based around the open-risk technology. Yeah, so I started work there in 2008 and they'd been kind of running with it for about a year since then with ASIC. But since I started, there's been a lot of kind of fix up in the project. So when the original development team went to FlexTronics, they didn't really keep maintaining stuff on the website. There was an odd patch for the toolchain, I believe, by some people related, but it was really left by itself. And there wasn't an active maintaining community, really. So it also took on that job, really. And I took on that job as well. We cleaned up the simulator and a lot of fixes, the RTL level implementation. So the thing which goes onto the FPGA has been fixed up. I personally did the FPU implementation. A lot of cache fix ups and various bugs in the process. So it's quite stable and sturdy and well done. We've also made it easier to get at it. So this Orpsoc thing is like a reference platform. So you just download it, hopefully have all the right tools installed, press a button, and after an hour or so you get a little programming file that you can put onto your FPGA and run the CPU and run the system. This year, well, this last year, 2010, was a big year. We had a lot of fix up for the toolchain.  So that was quite cool. There's a couple of things. I'll explain it again. I'm really wanting to bring this project to the attention of people and hopefully garner some interest and maybe get people to look at lower level designing and open source projects. And of course the Linux kernel port for open risk was basically re-implemented. And I'll talk about our plans to hopefully get that upstream one day and what we're doing with it. So I guess I have a lot of reasons for why you would choose the open risk platform. Maybe from a commercial point of view or even if you're just a researcher or something. There's a lot of reasons why. Oh, I think it's good. This kind of went overlapped it. That's meant to say technology constrained. So I'll go through these other alternatives. There are a lot of other soft core microprocessors out there that you can get. So this is a thing where you can just get it and put it on your FPGA and run it, give it code, give it a program and it will execute and do things for you. And there are alternatives to the open risk. There's a company based in Sweden, started by a guy called Jerry Geisler and they developed the Leon for the European Space Agency about 10 years ago maybe. And they've been continually developing that. So that's actually open source. You can go and look at it. And it's licensed under the GPL. That's all very good. So you can use it for research and whatnot. But kind of closed shop. They don't really foster an open source community there. And also the LeonTuber's LGPL and I think that had a few people playing with it. But they switched to a model where the open source stuff is GPL. So if you're an ASIC company or if you're doing products and you want to then use that on your FPGA with proprietary modules, the stuff that adds a lot of value, the whole thing needs to be GPL. So it's not really an option for proprietary or commercial use really. Or it is if you pay them a lot of money, they'll change the license for you. So we'll give you a version that is licensed differently. The LM32 is written and maintained by the Lattice Micro Semi, another FPGA company. And that, the toolchain have not heard good things about and the license is questionable. Whether you can truly go and do what you want with it after it's, after you've started using it. Then there's MicroBlaze and Nios. Maybe you guys have heard of those ones. They're the big FPGA vendors solutions to soft core microprocessing. But again, they're not really free and open source. Well, they're not open source in the case of the MicroBlaze. Definitely not free if you want to do anything commercial with them. And again, they're technology constrained, which is what that thing's meant to say. There are clones of them, but they're in varying states of decay and half implementation. Well, I think the open risk is good. It's open. So as an engineer, I was always curious about what is underneath? What is going on underneath my code? What, oh, okay, and then why is this stream of instructions doing this? And then, oh, why is the bus doing that? And then, I was always curious. And so the open risk is a good way to, you know, spend a lot of time looking at, well, the open risk project and working with it is a good way to spend a lot of time at staring at wave form dumps and figuring out what's going on there, which is usually pretty hypnotic. It's basically a late 80s MIPS architecture, so very similar to the DLX architecture that Hennessey and Patterson had in their books and very similar to the power PC, the early power PC stuff. And it's an easy platform to get up to speed with. It's not overly complicated. I wanted to say something about RTL-IP, but, well, I guess for maybe for people who aren't really sure of what it is still, it's basically software. It just takes a while to compile and put on the chip. How much time do I have left? Have I gone, like, fifth? So, like, ten minutes left. Yeah, yeah. Anyway, so I think there are challenges facing open source RTL-IP. And yeah, we haven't seen a lot of it, so open cause is the main community for this stuff in the world, right? And sure, it's a reasonable level. You do get some good cause on there, but it's not really the community around it that you see with other open source software projects. And I'm kind of jealous. I want the interest that occurs in other open source projects to occur for this hardware world stuff. And I think there's a lot of attractive elements to it. So I kind of have two reasons why I think it's, or two people that I'm talking to here when I say there's not enough adoption. There's people who do ASICs for a living and there's probably not many of you in here who do that, but it's a very risky business. It's expensive to send your design away to Taiwan to get away for back and then test it. So they don't want any risk. And open source stuff, yeah, sure, it probably works for the most part, but you don't want to get your stuff back and find that there's a bug in it, because it's very expensive. And from the software engineers point of view, so perhaps people like yourselves, I guess traditionally there's been an approach of, well, I can't play with the software. I'm here, I'm just writing the code and it will run on the hardware, but if there's something wrong with the hardware, if I don't like it or if there's a tricky behavior, I can't really debug that. So I have to solve it another way. But now you don't have to. Now you can actually take the thing you're working with, the underlying hardware, and you can go and have a look at what it's actually doing. And you can change that, or you can fix it, or you can improve it. So I think there's a lot of interesting things to be done with that. Did I say it on that one? Like the hardware software co-design. So I think open source processes and IP and that level of design really opens up that world to you. Yeah, I have a bit of a winch here. I say open source EDA is not the best. There's not enough people who do RTL design. And Who at Home has an FPGA board compared to Who at Home has an x86 PC. Not many people. So I think that's why we're not really seeing the big pick up. Motivations for free and open source RTL design, I think FPGAs are becoming better, bigger, faster, more versatile. I also think that there's no reason why a equivalent to what's gone on with the Linux kernel or other equivalent big open source products that have been developed can't occur for the processor industry. I really don't. And like I say, if that was available, and people like Apple or whatever could just go and pull in a free processor from somewhere, or mostly free, just pay for the engineering, but no royalty costs, it would allow them to free up money to do other cool things with their hardware or their phones or whatever. So it's just continued commoditization of this thing. A couple of roadblocks here, I think with this whole approach, if you just want to process and you want to drop it in, you don't care how it works, you're doing something else interesting on your chip or your FPGA, fair enough, maybe this stuff isn't for you. And like I said before, if you're happy to pay our millions, fine, do it. I'm just saying the whole platform now has been rejuvenated, better tool chain, good kernel ports, pretty sturdy. And I really don't think there's too many big roadblocks anymore to having a big, successful open source hardware project succeed. And so I've been working on it for two years and oh, he wants to have my password. I've been working with it for two years and I do think there's a lot of potential with not only this platform, but the idea of doing open source hardware design and having a big collaborative community, engineers in companies, like proprietary companies, or companies doing work with open source stuff, but for proprietary means contributing back to the project, which is basically what all of this Linux kind of world or how it works, right? It's people employed by companies to do something else, leveraging open source, but giving back to the community and everyone benefits. So a bit of a bit of a spiel about what we have now. We've got a kernel port, it's kept up to date with mainline. A lot of useful debugging architectures in there so you can like, I know that's mainly for me, but you can sit there and you can step through a program with that P trace thing. That's pretty handy. Use your libc port so you can run user space stuff pretty well, busybox, gdb server. So it's mainly targeted at embedded kind of use. We do have our simulator working with networking and stuff, which is kind of cool. And open source, I've completely failed to mention the whole open cores, open source hardware, like actual physical hardware thing going on. There's, you know, these boards, the schematics and Gerbers and bill of materials are all on open cores for you to download and you to fabricate them yourselves if you'd like. And there's push button synthesis builds available for this platform. More will come as I get the time. Just a quick mention as well, if you want to know more or see more about open cores or open risk, I'll beat the open day on Saturday hosting a booth. So come along and talk to me and play with the board and crash our kernel. So what's going on in the future is I hope to do more board ports, make it more available to everyone, make it really easy to use because I think that's what you want. We need better testing and everything, but that's so big thing we need is dynamic shared dynamic linking, loading support in our linker. That's one thing we don't have in the tool chain at the moment. And I guess we'll be scouring for a while because we're a bit busy doing lots of other things and it would be great if we could have some enthusiasts or contributors wishing to help out with that. Another one is a QEMU port, which is a really good simulator if you don't know what it is, and that helps us kind of and it helps you as well. You know, if you don't have hardware, you can compile stuff for open risk and play with it on your PC. So we were going to rewrite the actual processor RTL this year, but we figured we would fix a couple of the problems with the architecture as well. And while we were doing that, we thought, well, why don't we add smaller instruction support? Why don't we do this and that? And it kind of bloomed and now we're thinking, all right, next generation open risk processor architecture. So we're really kind of polishing off original open risk, making it a cool viable open source hardware platform, but focusing on the future. So it's a late 80s risk design. We think it's a bit dated. It's still usable, but new things are occurring. Multicore processing is occurring. A much better implementation. So probably no one would use a kernel if it was a big, if it was one C file or something, a big monolithic thing. It's kind of what you're dealing with with the original open risk. I mean, we're improving it, but a much more modular design is required, makes it easier for people to look at it and use it and fix it and test it. An extension friendly. So I think a lot of this FPGA stuff is really only worthwhile when you can add on your your secret source or whatever into the FPGA and have the software easily take advantage of it. And we would want it to, you can do that now, but we want to make that even better. So, do I have time to boot the kernel on the board? If you do it while we take some questions, that'd be great. Does anybody have some questions for Julius? This is downloading the kernel from my computer to the board and then it will boot it. So it's like some bootloader built into the hardware you just power on. Julius, what's the kind of minimum dollar cost of entry for people who would like to hack on open risk? These boards? When you consider, you know, you can buy a Beagle board for 150 bucks, for example, and people can go nuts on embedded arm Linux. Yeah. So, you know, can you use free versions of their of the Achtel tools, etc., etc., so if someone wants to get into it, how much money they've got to spend before they can go play? Just the board cost, which they can fad themselves or you can buy them from OpenCores, which, I don't know off the top of my head, I think it's about 200 euros for the full board, door-to-board with Ethernet stuff and USB debug cable. But then you may have to buy the Achtel program, which is about 40 US dollars. But then all the tools are free and of course you can sit there and you can play with all your, all the low-level RTL design stuff. So, kernel's booting. Yeah, I don't know. There's some weird UI corruption going on there and the DHCP server isn't running, so I've got a manually configure the IP when it comes up. Cool. Anyone else got a question? Cool. We have, anyone want to see CPU input? And then we can do a bit of a mount. Yeah, yeah. So, I've got a Spartan 3AN starter kit from Xilinx, which has got the Spartan 3A 700,000 gate equivalent chip. Do you know how much of that one of these cores would take up? That's a good question. I actually have a similar one and I've been meaning to port orpsock to it. I do have a vertex 5 board and I know that the processor takes up or less than a third, about a quarter maybe? Okay. Fully blown though. That's to run Linux and that's with huge caching. I've increased the cache ability on it to run up to 32k now. So, but hopefully on those Spartans it's not too big and you can optional stuff you don't need like the multiply unit or the FPU and things like that. Okay. But it should fit and should run and you should be able to boot the kernel and play with stuff. That starter board was only about $250. Yeah. I was looking recently. They're about that $100, $200 maybe US but we're a parody now so it doesn't really matter. Cool. Anyone else? Digital and have just put out a Xilinx FPGA board for 200 US for educational use and that's that thing I mean they kind of built it to run microblazer Linux but that would be a really nice platform. It's like a you know brand new Spartan 6, modern FPGA, Ethernet memory that's fully programmable over USB so you don't need to buy a JTAG port and yeah they're $200 if you're buying it from a .edu domain. Supported by the Freesilinx tools. Yeah. So if you're looking for a target for your kind of push button builds if you can do it nicely you also get the digital and guys on board because they're totally up with supporting education etc etc so you might want to have a look at that one. Yeah we've got a lot of requests to do that Spartan 3a starter and I've got the DSP version I presume they're not too different I was going to work on that but in the future hopefully but I just really want to attract people to the project and get people thinking about lower level stuff you know you're not stuck just pushing a compiler and an execute button somewhere so yeah. So what website should we go to to find all this stuff? OpenCores.org that's where it all is yeah maybe I should have put a big ad there. Cool so you want to tell us what you've just done on the screen? I've just booted and I've just catted Proxy pu info and you see a bit of UART corruption there then I've mounted something over NFS then I've executed a hello world over NFS. Cool okay so everybody please thank Julius for his talk. Thank you.


All right, well, Frantisek did introduce me as his colleague, Hina. I am an agile practitioner at Red Hat, and pretty much, I hope that this is something that is a very foundational information, but a lot of people are missing it. So let me see if we can change your minds between Domi and I. I'm Hina's friend, as you heard. And I'm seeing a lot of familiar faces here in the audience, many folks that we are working with on the daily basis. And throughout our sessions, we'll be asking you to participate with the feedback. So I just wanted to set up the ground rules. We'll be asking the questions, but we'll be not passing the mic. So I will be repeating your answers. There might be prizes. I think we're ready to start at this point. So let's dive in. All right, let's get started. So before you have success factors for agility, you have to become agile. And often, how does someone become agile? Does anyone practice scrum or kanban in this room? All right, how many scrums and how many kanbans? All right, there's gonna be a quiz at the end, so I remembered all of you. Okay, I would like someone to volunteer their experience. If they switch to agile, how did it happen for them? Did they get any training? Any life lessons? Tell me. All right, so that's very promising that there was minor training and attempts and of course hesitance. That's quite the formula for coming to agility. Oftentimes, when people say that they are gonna move to agility, they're actually told, hey, we are gonna deliver perfectly and we're gonna use something called scrum. But I'm not gonna really tell you much about it, right? So when people go and they move to scrum, what happens? Now that we've had enough people practicing scrum, there is quite a bit of a reputation. And nine times out of ten, people who are doing scrum will tell you that it's daily stand up, right?  Okay, and it's also meetings all day. Is that correct? Yes. Yes, okay. And then there's my favorite. The misunderstood child Kanban, the anti-scrum, something with less process that will still let you be agile. And what is Kanban? Creating cards? But what is a card? We don't really know because we don't have a process, so we don't care. And also what is Kanban, right? They just say it's the anti-scrum and let's do this magical thing. So let's get into actually becoming agile. Teams go from this and then they have a little bit of education. Or maybe they don't and they find something that works for them. But step two to becoming agile is learning that it's just a mindset. So when you think about scrum and you think about Kanban, there are ways to deliver software. They fall under the agile methodology, but they're frameworks. There's a set of steps. So when someone prescribes you to do agile, they're actually not telling you how to do work. They're telling you how to think about approaching your work. And often that is the foundational piece that's missing. How many people got that message when they started their agile journey of, hey, it's not a set of rules, but here's kind of the mindset we want you to approach when you're working? Anyone? Okay. Well, a very underwhelming amount of people. I think that was four and this is quite a large room. So let's tell you a little bit about it. And then hopefully when you get back to work, hopefully not until Monday at least, you'll take a look at what we tell you today. All right, so we as agile practitioners, I think we skip one slide. Agile practice team is growing in Red Hat. We as agile practitioners are trying to focus with our teams that they understand principles first. But what is that they are doing on the daily basis is that some team use scrums, some teams use Kanban. Many of them after testing it for themselves, they're coming up with some hybrid approach that works for them the best. I would like to talk about how this looks, how the methodology looks from the perspective of scrum, how it works. He now dive into more details of Kanban just to create a shared understanding of what are the ground rules for play with scrum and Kanban. So scrum is very popular because it's a lightweight, easy to understand process. This is why many teams would be adapting that. This is perfect for executing complex knowledge work. So if you are working in the complex environment, scrum will probably work for you. You need to keep in mind that there are specific rules for play. So they are team roles. There are specific ceremonies. There are scrum artifacts like product increment, product backlog and sprint backlog. All of this is focusing on interactive change in the time boxed pieces of periods of time. So we go in the interactive cycle of improvement here. On the back of all of that, the most important is that this methodology is focusing on three pillars. It's empirical process. So therefore we have inspection, adoption and improvement. The process has to be transparent to work and people who are using this process at the back of their head should remember what are the core values of scrum and one of them is very similar to what Red Hat believes is openness. Then we have courage, commitment, focus. We share, we have a common, as an organization we have common values to those scrum values. Therefore that mostly works for our teams. Now we'll move on to details of how Kanban works. All right, here's Kanban. I'm gonna give you a quick overview. Keep in mind this is not everything. If you have questions, I'll be here all weekend. The quick overview of Kanban is you are visualizing your workflow and you are moving things across that workflow. So you have to define work because they're units of work and here's a big, big thing that a lot of people don't know. And this was recently proven when I mentioned this. All of these things, these units of work should be of similar size, ideally the same size. Has anyone heard that before? Does anyone practice that? Okay, and I know he does. The one that raised his hand, he does believe it. So why do they have to be of similar size? You're moving things through a system kind of like a factory because this is all inspired by the Toyota production system. And what you do is you define how it goes through the factory just as you would build a car. You start with certain pieces and you move it down the line, the production line. And so with Kanban, you're doing the same thing.  And you're keeping it very, very simple. The only thing that I'll add to this because I can go in for about the next two hours to talk about Kanban is if you look at the top, you'll see numbers. So if you look at the word pending at the first column, there's six. That's something called a limit. So what we can do is we can overwhelm ourselves by putting in every kind of work that we can or we can do the Kanban style and limit ourselves and that'll allow us to focus. That number at the top is called a work in progress limit and you'll see why that's helpful in a little bit. So now I'll hand it over to Dami. Yeah, so we work keeping in mind agile principles like I mentioned before, many teams adopt scrum. Some of them convert to Kanban in the middle of the way because they feel this is more suitable. In some cases they go back and forth because they wanna retest the approach. I see Thomas smiling. And we have so-called hybrid approaches that teams are working on. We as agile practitioners are fine with that and we're observing these teams work and being successful and we mapped out some success criteria among these teams. And I'm very excited to present on these success criteria today because this is hopefully something you can take home and apply to your work with the teams starting from Monday. Those are like little changes that can be made and checkpoints that you can keep in the back of your head to refer to later on. So to make things even more straightforward we'll be talking about five criteria of success for the teams that are working with agile methodologies and the first one of them will be transparency. Then we look into the priorities and prioritizing of work, scoping of work, creating a shared understanding within the teams and incremental improvement. We'll be presenting these success factors using the metaphor of the coffee cups because this is main team of the DEF CONF this years who got their coffee cup already.  Great. So we will be presenting the success factors based on the metaphor of the coffee cups and just one thing to keep on back of your mind is that one cup represents one unit of work. All right. So transparency means being open and honest, not only about our progress and achievements but also about our issues and our setback. Okay, what does that mean? First, step one is looking at the photos because this is a very cup oriented presentation. We're gonna have a little bit of fun with this. If you look at the top photo, that is day to day work. And what can you tell me is going on there? Anyone? Do we know what we're working on? No. Well, clearly someone did the dishes because there's nothing there. Okay. But the reality is we're actually working on a lot. If you look at the bottom photo, that's everything that's going on. And we only know that because we see it.  We can visualize it. It's displaying our work. I can see with my eyes. I know that I can have real time status updates. I know if there's an atomic cup in the queue or a fedora cup in the queue, right? Because it's there in front of me. And when you know what's going on, what do you not need to micromanage? Does anyone like being micromanaged? Show of hands? Okay, this one, this time I got none. Oh, I got half. I got half. But also that knowledge and that open communication makes a trustful environment because our cards are out on the table. There's nothing to hide. There's nothing to be anxious about. I know exactly what's going on. So I don't have to wonder, are you working on this PR? Are you working on that PR? It's already there, I already know. And that awareness improves communication. Because I know I'm able to facilitate the conversations I need, which is really important. So the one thing I do wanna add because I had this thought while brushing my teeth in the morning was all of these principles that we were teaching you, all of these ideas, they apply to both individual work and teamwork. Often people say, I work by myself, I don't have to worry about this. But the reality is, someone who works by themselves, it's still important for them to be organized, to scope their work, to be transparent. The only thing they're not doing is working together with someone. So they're talking to themselves when they communicate. The difference between individual work and teamwork is just talking to someone. So that communication part is gonna be very important. But remember, if you just work on stuff yourself, everything in this presentation will apply to you as well. So now, now that we know what transparency can look like, I'm gonna ask everyone who has a little bit of familiarity, and if you don't know, that's fine. Well, we're here to talk you through it about how scrum can show you transparency. Do we have anyone who wants to take a shot at telling us? How does scrum give you transparency? Daily stand-ups? How so? All right, I'm gonna rephrase that because it was pretty spot on. Everyone shares their status, so everyone on the team knows what's going on. That's absolutely correct. Anything else about how scrum shows transparency? It was still- Brendan. Oh, Brendan. I'll take that. And let's move over to Kanban. How does Kanban give you transparency? All right, I'm hearing common trends about you can see things. One more? Absolutely. All right, and so, to keep it simple, yes, all of your work is visualized in both scrum and Kanban. You can see it. Ideally, if you keep it up to date, please keep it up to date because I'm an agile practitioner. And then, also the little addition from scrum. Great one, our first answer. I didn't actually anticipate to hear that is stand up. You're putting everything on the table because you're keeping it very simple and updating everyone. On usually a daily basis, we'll talk about how it's okay to tailor things a little bit later. Next up. The second factor of succeeding with agile during your work with teams is prioritization. Agile teams use prioritization to confirm that they deliver the value. And that means that we are not prioritizing just at the beginning of the project when we get the project chart. We keep prioritizing through our project. So it's very important to go back and reprioritize that to-do list that you have when you have more work coming because it is most likely that some of these items that you might be already working on have a lower priority than what is currently brought to the table. Paratization is one of very important aspects of the agile process. And we need to remember and ask ourselves when delivering daily work, how is that bringing value to the customer? From experience, we heard feedback that, well, my team doesn't have customer. I don't have a direct interaction with the customer. So how would I know these things? There will be other people who should be knowing how to prioritize. I'm just working on what is given on the table. Then our advice will be, if you don't have a customer, you most likely have a customer of your work, somebody who is depending on your work. Then it's important to make a note that, hey, am I blocking with somebody with that work that I'm doing on the daily basis? Is there anything that we can do differently to bring the most value? And this is driving the point that, driving the point to the second agile principle that agile teams welcome change also late in development. They are not getting frustrated. Oh my God, we work on all of that work and now this is wasted. This is not their point. If we know how to prioritize, we know that if we work on something that we are no longer going to use, first of all, we learn something. But second of all, we also know that this is not a big deal because something goes from the file of todo items and something is replaced by that. And if everybody in the team have a shared understanding of this, we can move on as a team and complete the most viable work. And talking about Scrum and Kanban, do you have idea how is that represented in the specific methodologies if we would talk about Scrum first? Where is that prioritization factor coming to importance? All right, so we are grooming the backlog in Scrum. I heard backlog order, which is also applying for Kanban. The items that are most important will be on the top of your list. So they should be a person driving this backlog and looking into the items to do on your boards to make sure that they are prioritized. The challenge is that sometimes we are so busy creating the items to work on that not necessarily the most priority items will be work on first, right? Because we are like, okay, we have this cart, we'll go and work on this, but it was that the cart that should be done first, the dependencies mapping and priorities might be challenged in that aspect. So make a mental note before taking a new task to do, ask yourself, how is that bringing value to my team and other teams that are cooperating with me? Could something be done better? All right, so let's get into something called scoping to read the quote, cause it's always fun. This scoping is necessary in order to come up with the right number of software releases, the right sequences of those releases, the dependencies among the requirements and thus the deliverables and scope for each release. Without this crucial step, the process of breaking an application into software releases would be completely arbitrary, which means pretty much useless. So let's take a look at the cups again. I'm gonna ask for your help. At the top, remember, this is our work, this is our work queue. First, can someone tell me how that top list of work makes them feel? All right, you know what? I can see where you're coming from because now I'm thirsty as well. But do they think that, let's say for two people, they can drink all of those cups within a day, maybe? Ideally, if you're hydrating well. But often not, no. So then, let's go to the bottom. Do you think that's easier to consume? All right, so scoping work basically is exactly that. You're understanding how much can be done within reason. No, I can't drink all of those cups in a day. Maybe not even two days, they're big cups. You're also focusing on short-term progress and it's gonna help you with long-term predictability. It'll allow you to collect metrics, so maybe I drank these two cups and then I realize I could fit in another cup of tea and I'll be able to understand that because I collected that metric and it'll help us forecast our work and that means, all right, so if I know that, on average, I drink three cups a day, how many cups do I think I can drink tomorrow? Probably three, right? There's always a little bit of wiggle room, but that room for error will decrease the more I get to know myself, the more I test this metric out. So let's talk about how these cups relate to. Scrum and kombon. I'm not gonna go one by one, I'm just gonna ask, can someone tell me how do they think that this scoping work is built in to scrum or kombon? Okay, anything else? Absolutely, all right. And to show you, because we've created these slides, in scrum you have sprint cycles and in kombon you have work in progress limits. Remember I mentioned all work should be of the same size. I do wanna continue to drill that in your head because it's something that's the unsung hero of kombon. That's why kombon is the misunderstood child. But the easiest way for me to describe why there are sprint cycles and why we are trying to measure. In kombon you use throughput, which is how fast one of those units of work can get through the system. And in scrum you have sprint cycles, which are a defined set of time, for example, two weeks, three weeks, four weeks, and they are repetitive. So those sprint cycles will continuously be what you've defined as two weeks, three weeks, four weeks. And there is a big ask to not change those boundaries unless you have practiced it and you see that there is a need for some level of flexibility. And I'm gonna go to my friend, physics and math for this. So can someone tell me from a physics perspective what velocity is? Unless you forgot, that's okay, I can remind you. Absolutely, everyone is thinking of it, but we're a little shy, that's okay. Velocity, the measure of distance traveled with respect to time. So why do we have these sprint cycles? We wanna collect our velocity. Why do we have our throughput? Because we wanna measure how much work we do with respect to that time. And that'll essentially give us a number that we can then measure against every time we repeat the process. In Kanban, your process is how fast it takes you to get one unit of work through the system. So every time I drink a cup from the start to the finish, that is that measurement, that's my metric for that one. I'll take everything, I'll sum it up and I'll use that as data points to help predictability. And for Scrum, it's pretty much the same thing, but you're forecasting how much you can drink in, let's say, the week. And then every week you take it, you go, all right, this week as a team, we drank 20 cups. We thought we could drink 30. Let's talk about why we couldn't drink 30, but then we'll go ahead and we will make a new forecast for our next sprint. And the beauty of it is that time doesn't change in the sprints, so we'll be able to now have yet another data point. And the more data you have, the better you can make predictions, right? Yes. Okay, and now I'll hand it back to Domi. So let's dive into what is the shared understanding. The shared understanding is the thing that is missing when the project is failing. Because everybody's thinking that they kind of know what the other person is doing, but maybe they went on PTO and didn't update the cart, or maybe they work on one project instead of the other one. Maybe they had some kind of the customer support case in the interim, so the stuff that was projected to be worked didn't get touched. So the best way to grasp shared understanding is to consider what happens when it's missing. And this is where we are starting to have a problem. In general, diving back to how the shared understanding looks like on our CAP metaphor, we see the CAPs on the top picture, there are five CAPs. Can you tell what kind of projects is the team working on? You might have educated guess, right? If you are familiar with this type of swag, or you are talking closer to somebody on the team because you are particularly close to each other, so you had this discussion, but at the team level, you are not sure. You really have to have a closer look and have it explicit what is going on, right? I see silver bruise in progress. We are compiling specific things. We are working with the PNT DevOps, so there are improvements done to the team. Shared understanding is important to the team from the perspective that every single one of us is different and we are coming with the knowledge that we gained through our life. This is a knowledge that is not written on module pages, on any kinds of directories in our company. This is, those are the things that we learned throughout the life. Then we have the expectations and the knowledge that is learned when we start onboarding to our teams, like we read specific guides, we read the documentation that is provided by the team. And those two combined make us the team members for the specific teams, but it's important to remember that there could be a lot of confusion. So the discussion is needed on the daily basis and we need to make sure that we create the room to have and build this shared understanding within the team. If not, the testing team will be working on something else than the development team. We are being requested different thing. Then we're delivering final item of work and this is not what was expected from the people who requested that from us. So when you are not sure what is that you are going to work or how that fits, it's good to have this kind of discussions. And now let's, like, how are we applying that with Scrum and the Kanban? So with Scrum we have acceptance criteria and workflow definition of done. The same goes to Kanban when we are looking at the task description. And the most important is that we are building awareness. Do you have some tips how to make a better shared understanding within your teams? Planning poker? Anything else that your team might be using that might be of use for other folks in the room that works well for you to create this shared understanding on the team level? All right. And this one I had to plug in one of my philosophers. If anyone knows me, I love philosophy. So knowing yourself is the beginning of all wisdom. And that's from our friend Aristotle. Why am I bringing this one up? Because we're gonna talk about incremental improvement. And instead of giving you two photos, I'm giving you one. So I'm gonna ask you about this cup. Is there anything different about this cup? It's broken. Kind of like other things. In tech, what would be broken? See, I didn't say anything. Okay. So it still works. Well, let's see. But I have another question which often we forget to ask. You said the blanket statement of it's broken. But let's make sure we all are on the same page. Why is it broken? What makes it broken? You can't use a handle, absolutely. It seems obvious, but in the beginning I heard you can still use the cup. Which there's truth in that. But to be honest, if I saw the broken handle, I'd be like, you can't use this cup. What do I do now? What if it's my only cup? Or what if I don't have time to go to the store and buy another cup? How can we fix it? Is it fixable? Will I have to dehydrate? Any ways to fix it? Glue it. All right. So, we just did a retrospective. Surprise. All right. We reviewed and we reflected. We took a look at this. And it was small, it was easy. We didn't philosophize at the meta level because that one takes a lot longer to find out about, right? We're setting small attainable goals. Glue it. Absolutely. I'm gonna try that. I'm gonna try gluing this cup. It's a real cup. We took these photos. But if I heard something like get some clay, go ahead, adhere it, see if that helps. Maybe bake it in the oven, see if it solidifies.  But that's a lot harder than gluing, right? And oftentimes in retrospectives, we hear the go get some clay and then we're gonna put it in the oven and then we're gonna bake it. And guess what? What we tried because it was first of all, very complicated and unqualified, also didn't work again. Right? The good thing is if we tried the small glue and it didn't work, we didn't waste much time. Probably everyone has glue in their kitchen, in their office. And if you don't, text your friend and if they're coming over for drinks or a cup of tea, just ask them to bring some glue. It's a little bit of a weird request, but they're your friends. They should understand. And we also focused on what we can control. For example, if more than the handle was broken, is it even worth having a conversation? What if this cup was shattered into pieces? You think I should think about fixing it? No. And in retrospectives, the main topics are what's shattered into pieces. That's out of our control half the time or we just know that it's gonna be a long time. So you can put that thought into the universe, let the people who can maybe fix it over time or re-strategize or help you out, go ahead and tackle that. While everything else is shattered into pieces and of course that's extreme verbiage, but while everything else is in chaos, say you're going through a transformation, it's totally okay to be hectic and disruptive and uncomfortable, anxiety, having a lot of anxiety about it. But the reality is, you just put that thought into the universe, you tell someone, hey, this is why this is so uncomfortable and let them go forward and you can focus on what you're doing today. Take a look at the cup handle and glue it back together. So now I kind of gave you what's in scrum. There's something called a kaizen in Kanban. It's pretty much the same thing.  But improvement comes from inspection. I looked at my surroundings, I looked at what's going on. I looked at what's making my life difficult. But I asked myself the more of questions about what's in my control that's making myself difficult. And then I made guesses about small ways to fix it. How many people have retrospectives like that? How many people have more meta-level retrospectives? Everything is broken, I can't do this. Just one? Come on, on a show of hands, if you're listening, I understand it's after lunch. How many people have retrospectives to complain about things that are not in their control? All right, we woke some people up. So what I'm gonna tell you is the next time you have one of those retrospectives, cut it out because it's a waste of your time and there's too many meetings in the day to have those discussions every two weeks. Once a quarter? Yeah, go for it. Every two weeks, it's not worth thinking about how do I glue small pieces of ceramics back together that will shatter in two seconds anyway. So we're gonna close out pretty quickly because we wanna give you time for our questions. Hopefully this is a very simple understanding of what's going on but I wanna leave you with the fact that changing practices is one thing and changing minds is another. This is important because your mindset is often the blocker to this idea of agility. You're using scrum and you're using Kanban but we're focused on these rules. Scrum and Kanban took those success factors into the process and put it in there so you didn't have to think about it. So that transparency is already there. The discussion and prioritization is already there. Making sure you have a shared understanding is already there. Incrementally improving is there and scoping out your work is there. But if the way that these frameworks have defined how to do that doesn't work for you, I'm distributed, I can't meet that often, I'm spread thin, I'm gonna say have a conversation about it because if there's another way for you to get transparency without using a board of some type, I haven't given it much thought but if someone has a good idea, try it out. If you know everything that's going on without asking without pulling your hair out and you can still get transparency, maybe you're gonna go and create the next scrum and Kanban for people to use. The same as priorities, maybe one person does it. Try something different. When the scrum principles or the scrum process or the Kanban process that you defined doesn't work for you, take a look at that last step that we talked about, inspection. Think about how you can make it easier for you to get that information and try it. You don't need to compromise the integrity of the process but you can change how you're doing things and the big joke is breaking that, you didn't do anything wrong, you actually were agile. So on Monday, everything that kind of frustrates you and you think there's things that you can do easier as a team or as an individual, bring it to the table, communicate it with the people that you're working with and maybe make a plan to try it out. If this does resonate with anyone, tweet us, email us and let me know how it worked because this is my field and my goal is never to make someone's life difficult. My goal is to try to make everyone's life easy. We're a team and I mean, I gotta work, I'm not super rich, I have to pay my bills so might as well have fun and do something productive in an easier manner. So that's a thank you for me. Dami, any closing statements? And thank you for me. I hope that everyone got something for themselves from this presentation and I'm happy to see all of you guys here. The room is packed full so I hope it was good use of your time. Thank you. All right, now we're gonna have time for questions or if you wanna share some horror stories or lessons learned. So first, questions. Yikes. That is a tough question. So, the question was, what are your recommendations and experiences for practicing scrum without a dedicated scrum master? Hi Ed. I used to be a scrum master and then I left him. So what I'm gonna tell you is it's very tough to do this stuff without someone to help you guide yourself through this process. Scrum essentially is a way to help teams become self-organizing and it's a way for you all to remind yourselves and work together. So that scrum master really is crucial to teaching those principles. You'll get to a point where it's comfortable and that scrum master's kinda just there to observe while everyone self-organizes. But as the scrum master goes in all honesty, the habits start going. It's like if you have a personal trainer at the gym. That personal trainer is there to train you and remind you. But oftentimes when people stop having that personal trainer, their practices start diminishing unless they're really, really good. And if they're really, really good, they've essentially become the equivalent of a scrum master. So the void isn't really there. Practicing without a scrum master, my experience is it's very difficult. If you have someone to jump in occasionally to continue consulting, that's not a long-term engagement. They'll be there to help slow the process of getting back into bad habits. But when you don't have a scrum master, it's very difficult to do this stuff because you need someone with an objective outside point of view to say, fine, if we don't wanna do that this way, that's cool. This is why we're doing it. Give me a better way to do it. Let's make it easier. Aureka Wodnil said he's saying that a lot of discipline is needed and the team can do it if they really want to. And you guys have each other. So going back to the scrum values of the respecting each other, of committing, of having a courage to call each other out. Sometimes this is what is missing within the team.  Yes? It's the beginning, but maybe up to some time comes soon. All right, so we had a valid point raised that some teams have scrum masters and it feels like the team feels like they need to report to the scrum master. They are not doing that for themselves, but they will ping just the scrum master. Hey, I'm missing a stand up today. Just FYI. Nobody else knows what happened, right? So that was the point, very well made point. So just to bring back the question because not everybody could possibly hear, it's like what to do if you don't have 100% buying within the team. Some people are having a better understanding what does it mean to apply the agile practices and mindset and other would just do it their way because this is faster. This is how they were doing for years and it's proving to work for them better. My advice will be to try to touch on this point during the retrospective, but if that doesn't work and we don't see improvement for several weeks, let's say, and we are trying to be very gentle, it's time to have a one-on-one discussion with the specific person. What is that we can do to support them? And this is coming out if you are working with scrum, maybe from the scrum master if that person is there, maybe from the product owner, or you can meet together with the person that is, I would say a role model to that engineer or tester, and they believe in what that other person is doing to show how can we do things better together. That is what I would recommend in this case. Hina, do you have anything? Just one to add is sometimes you have to kind of gauge the field. We like to listen to people that we respect, and if someone that you respect, or that they, sorry, they respect, it doesn't matter if you respect them or not, has the values that you do, you might wanna bring them into the conversation because nine times out of 10, this is someone that you trust or someone you look up to, you're gonna hear that message much better than someone that you don't give any significance to. We have a question for what is the personal method, our favorite method for scaling the scrum? All right, that's a very tough question because it's something I struggle with every day, and inspection and adaption is really important here, looking at what the lowest common denominator of needed information is, and saying, hey, all we need is this, this, and this. We can teach you how to get these basic things, and then the rest of it, we're not going to enforce because we're not here when you're scaling to tell you how to breathe. We're here to ask for common criteria, so we're all on the same page, and that's pretty much it, so it's a very vague answer, but I'll say if this is a real world question where you're looking today, go to your organization and say, what tools are important for them to have from me or from the team, and then everything else, see if it's really valuable, if it's not, throw it in the trash. I will add to that that usually the scaling will be the most successful if it's starting from the bottom up, so there are people in your team that are particularly excited and they want to try with the team, so they will get them buying, then you might be felt lost in the field in Red Hat who support you with the training as a job practice team, so you're always welcome to ping us and tell us what you need. If there will be enough interested people who will be providing training on the specific topics, there are a lot of ill-learnings, and then comes the time when you probably need the support from your manager and you just go up, and then the other team sees, wow, they're doing great, we want to be similar, and that repeats in the cycle, so you're cross-populating basically, that will be the most successful strategy there. We're out of time, but I'll be here in the corner, so if you have questions, feel free to reach out, and like I said, if you think about this and really want to brainstorm and experiment, you can ask for our advice, Twitter, and then if you have any success stories, please do share. Thank you for coming. Thank you.


What's good y'all it's your boy Ross back again with another video. So today I got something different for you guys I'm gonna be doing my updated version of my shoe collection Now I did this video maybe a few years ago I'm not sure if you guys even seen that or whatnot, but I did do a My collection video at the time of the shoes that I had or whatnot And I know a lot of you guys have been asking over the years for me to Do some more Collection or for you guys to you know check out the collection or what not behind me And I have been putting it off because I've been trying to get other videos done But I I decided that I want to start getting back into showing you guys my collection and also I'll put a poll on Instagram and Twitter about me doing Shoe unboxing videos or what not and I've been getting quite a quite a bit of shoes off Camera or whatnot. I'm not sure if you've noticed or paid attention different shoes have been moving around back there So I wanted to start doing Unboxing of shoes that I end up getting and and talking about the quality and and you know How I lace them up and stuff like that and just go in depth with you know The particular shoes that I like to wear and a lot of you guys have voted for me to do that on Instagram and Twitter The polls haven't even ended yet, but it's a landslide in votes honestly So I think that's gonna be some of the new content. I'm gonna be bringing to the channel I mean my name does have kicking it with Ross in the title of my YouTube channel It's my channel name. So it only makes sense to bring, you know, talk about Some of the kicks I have and show off, you know Some of the kicks I was able to purchase and maybe it could be a situation where some of the kicks I am in of getting it may, you know, you may want to get it for yourself So you're not sure and maybe you come here you get to check out You know my impressions of it and it may be something that you may want to get later on down the line So definitely I think I'm gonna get into that but the best way to start that off is to show you guys my updated collection So far what I have now I have to make a Statement here. I don't know if you guys notice, but the collection is much smaller than what it used to be Originally, I had Jordan's on one side and Air Max's on the other side But as I realized as time went on I wouldn't really wear my Air Max's. I barely won I'm talking about I had over close to 40 pair of Air Max's different ones like Air Max 90s 95s 97s like, you know, the newer Air Max's that they were dropping like I had a Whole bunch that I weren't even wearing like shoes. I Weren't wearing for years. So I was like, you know what? I've always been more of a Jordan guy to be honest with you and you know, I was like, you know what? Let me go ahead and give these shoes away and that's exactly what I did So shout out to the people that was able to get the shoes from me. I didn't charge nobody for them I could have sold them but I just gave them away to people that you know could use them and benefit them And I kept them all clean and I barely wore them. So I was like, you know what? Let me go ahead give them away and kind of revamp my collection to build this Jordan wall that I'm trying to build back there So all of this collection you see now for the most part is all Jordans So I'm gonna show you guys what I have show you some of my favorite pair and the pair that I usually wear the most and Then we're gonna go from there. So, yeah, let's get right into my shoe collection All right, y'all so we're gonna check out my Jordan collection and what I have so far Before we do that, look at these trophies man. Look at look at look at the championships Look at the plaque, you know I'm saying you're under speedy YouTube wrestling champ of the world And also you're in the clutch world everywhere champion had to had to you know check these out real quick But yeah, look at that beautiful Thank you guys for all the love and support but enough of that Let's get to the shoes because we know that's what y'all here for so Let's start with the ones now in total the amount of Jordan ones I have so far in the collection. Let's count one two three four five six seven eight nine ten eleven twelve thirteen fourteen pair of Jordan ones man I'm I ain't gonna lie to you I wouldn't always a fan of Jordan ones coming up, but and in recent years I've definitely been loving the colorways that they've been dropping there's still more that I'm trying to get That I missed out on but you know, if I'm able to get them, I'll definitely get them. But right now Let me show you some of my favorite pair that I like rocking these taxis. I love rocking these man I love rocking ease love the quality on these shoes. I don't know It's just something about this this taxi yellow. I've always appreciated and I don't really see too many people wearing them But I love these man. These are some of my favorite pair to put on the feet. I Recently just got the reverse Laney's these come in women's sizes. I love the colors on these I love the you know, the love the way it looks Love this bro. This is the the Laney colorway is always a nice one Especially, you know, just on a Jordan one. So I and recently just got these so They they may be coming becoming my new favorite pair of wear Recently just got these as well Rocking with these. I love the the suede material on the back here the nice material right here So overall good looking Jordan one another one. I'm like I've been recently wearing a little bit more Now these right here These it's tough. These are the twist two planos. They only come in women's sizes But look at the fur look at the the material That's why I had to get these all around the shoe is this fur It's real fur if you look in the shoe, I don't know. I think it may be in the other shoe There is like a I don't know if you guys can see that It's a sign right there. See if the camera will focus. You see this shoe contains real fur Died natural adult bovine fur origins is from Italy. Yeah So this is real fur on the shoes and look at the wings right here. It's metallic now I've definitely become a fan of when Jordan brand puts like metallic A jump man on their shoes or anything metallic related I love the quality of that and this just sets it off even more but not these Bad boys right here or just beautiful bro. Look look at the quality on these. I've only worn these I believe twice, but I love the quality on these except they only came in women pairs women sizes So all right next pair I have Now these right here. I I looked up on these. These are the Georgetown ones The high 85s. These are my first pair of high 85 Jordan ones, bro But these bad boys is nice. I love me to Georgetown, Kola way When I say I looked up on these shout out to one of the homies. He actually He knows that I do YouTube or whatever. He's one of my shoe plug He hooked me up with these bad boys for a very good price I know they're pretty expensive aftermarket, but he wouldn't even tax them even that much for these and Love these bad boys right here, man. So definitely had to get these Another favorite pair of ones I have that I definitely love when the bubblegum ones right here These are for women. I love the material on here with the patent leather I love these bro. These these bad boys. This is always an attention good or any time I wear them I love these bad boys. These are beautiful. Love them. Love them. Love them, man Only came in women sizes, bro.  They be having the best colorways. I promise you right here is the These are the prototype ones What I like about these ones is the fact that they come with multiple shoelaces Multiple different color shoelaces. They're all in the in the in the container I don't feel like but now I'm trying to get them, but they come with different Shoelaces, I think are like three pairs. So I love these right here nice nice I like the the material on this side. It's more of a suede material right there sweet new book material love it Definitely a cool pair of ones. I got Right here the brotherhoods. I Definitely like wearing vibrant color Jordan ones So definitely out of the brotherhoods and warning these a few times definitely need to clean them up a little more It's a little spot of smudge right there. So we're gonna clean that up, but love these I mean can't go wrong with this colorway. So definitely glad I got this pair These right here the patent leather ones This self-explanatory look at look at the fat leather looks beautiful love the quality on these shoes Yeah, it's self-explanatory and I love the black and red colorway. So yeah got these bad boys Now these right here These are nice These are the the handcrafted ones now what I like about these is this is all one shoelace But is is set up where it looks like two Different shoelaces, but it's all one shoelace is just the bottom half is black top half is this like neon Neon orange, but what's also nice about this and I'm not sure if you guys can tell But I'm sure you probably won't be able to tell but you can tell about the the Stitching you see the stitching on inside the shoe. That's also on the sole So it's like this comfortable stitching on the sole as I you know as on out on On this layer of the shoe and it feels real comfortable when you're walking in them I will say Jordan ones are not the most particular comfortable pair shoes to be wearing for a while But those aren't because of the way they set up the sole in the shoe with that quilted fabric Love these right here other pink laces that come with it Definitely is a cop if you're able to get them I believe a lot of people passed on these next is my my red and white joints right here. I Rock with these I've only worn these I believe maybe twice Maybe twice. I have a fit for them. I just haven't had the time to actually pull them out But I definitely am rocking with these bad boys right here something slight none too crazy Now these right here. I call these the cool gray ones I know it's not the name of them But I call them the cool gray ones because these bad boys is birth They're basically just cool gray ones love it anything cool gray related color-wise. I'm a big fan of so definitely had to get these and And My last pair of ones happen to be another female shoe is the silver top ones right here now the material you got this silver Silver like material, but what's cool is to shoe inside? You see how it's smooth and shiny That's how it feels all the way inside the shoe. I love that material I'm not sure the name of it, but it's this silky smooth material on the inside of the shoe and These only come in women unfortunately, but I love these bad boys I love love that silver Metallic chrome look they got around the outside of the shoe. So I've only worn these a few times as well All right now that we're done with the ones Let's get to the 13th and we're gonna start with the playoff 13s Just got these a couple weeks ago. I was able to hit on the sneakers app for the earth They did a shock drop. So I was able to get a pair of these bad boys. They have not been worn yet I have not worn them. You can see the plastic is on the bubble. I've always wanted some playoff 13 So the fact I was able to get some is awesome. I've always loved like the bottom of the shoe I always thought that this part was always cool for me growing up as a kid in the bubble here The holographic little bubble right here always loved this as the kid So the fact I was able to get a pair finally. I'm very happy about that. I can't wait to pull these bad boys out Now these right here these right here, man, I Definitely definitely more knees a lot. I've had these for a few years now and I love them, bro It's funny. I went to Walmart made me like last year or whatever and some dude was at what who worked at Walmart He's like, yo, bro, these shoes is you know, them kicks is tough I was I appreciate it, but I was just chillin man, you know, Sam But these definitely do look nice depending on what fit you have You don't even have to go crazy with it or whatnot. I love Love the material on here definitely needs to get cleaned up, but I'm definitely more knees a lot and the next pair These right here. I've definitely worn these quite a bit. I kind of got these around the same time I got these their teams right here You can see the scuff marks definitely got to get cleaned up, but I mean I love 13s They're very comfortable if you haven't had a pair of 13s definitely get you some they're very comfortable for me I've always like rocking with them. So these are another pair. I wear a lot The red flint 13's is just I mean it's pretty much just a red version of the flint 13's Love these love the gray love the suede on it raises one of my favorite colors for those who don't know So I when they initially drop I had to cop some so love these bad boys right here Now these the obsidian 13s I was able to get these under resale because they were sitting a lot Many people weren't buying them I know originally I wasn't gonna get them But I decided to get them because mainly because of so like the light blue under the soul and it's a nice I have a lot of a lot of things I can match with this. So I end up getting it under retail Stop brand new hadn't been worn. I think I paid like maybe From the person that was selling them. I think it had to be like Maybe 160 or something like that 170 it was definitely on the retail. I didn't pay Full retail price, but it was it was worth it the del so 13s love It's like something with yellow in Jordan depending on what the yellow is It pops on a lot of shoes for me personally and these are Beautiful love wearing these out on a bright sunny day. People can see you a mile away. Love these babies right here and of I Think personally These may be my favorite 13s only because I always wanted them and I was able to get them these are the flint blue 13s man the flint 13s man These are the 2020 version. I was able to get these at a good price. They weren't taxing for them got them Believe dead stock or whatnot. Love these bad boys always wanting them never had a chance to get them When they when they came across my path, I had to get them all you know, let me go ahead and get these bad boys I always wanted the flint 13. So here you go. Love these babies And My last pair of 13s right here. He's right here all the Court purple 13s love these bad boys. These need to get cleaned up too, man. Some of these shoes I'm sorry y'all. They're not as in pristine condition, but I can they let you know that I be wearing them a lot more I actually definitely need to get these boys scrubbed up. So I got some cleaning material I'm gonna definitely scrub these bad boys up But I mean the purple on the black people slept on these in my opinion I don't really see too many people wearing these but these bad boys is nice I'm rocking with these man. And they match my alma mater of school color shout out to Privilege A&M use university PDA and you man shout out Panthers, you know, and one of our colors is purple So Anytime I go to preview back to you know, homecoming related or anything I anytime I just go back up there Well, I feel like repping my alma mater then I put these bad boys out with like a purple fit or something like that All right now This right here this whole row I call this the trophy section now The trophy section are the shoes that I feel like deserve to be showcased in a trophy case man. These don't deserve to be in the container So a lot of times these shoes end up getting rotated out So either they have some significant value to me or I just feel like they're super dope and they don't deserve to be in the container, so These right here cool grayer leavens were a must have for me I will say I Remember missing out on a cool gray 11s many years ago I wouldn't then have the money to get it or whatnot So when I heard that they were bringing them back out I said I had to get them now the crazy thing about this and I probably never did this again. I Got these early the shoes weren't supposed to drop into December. I end up getting these shoes in September So I guess you can say You know we getting shoes early got to pay an early tax fee. I paid $500 for these I kind of regret doing that only because when they originally dropped a there was a lot of pairs that I could Got for way cheaper, but I had them in September. So I just you know, I had them months before they dropped But I'm not doing that again I paid too much for these damn shoes $500 for these joints to get shipped early, but I love these bad boys I think I've made of warnings maybe four times man four or five times as I've had them Love the cool gray 11th man. I love this shoe. Love the material I think they did a good job on a re-releasing these now these right here all my pride and Joy, if you guys remember I just said I love when they do the metallic jump man or anything metallic related These midnight Navy Jordan 11's only are for women. Look at the buttery Sweet look at this. I had to get it just off this alone. Look at this beautiful This why this had to go on the case. Look at the just it's the material I had to get these these are some of my favorite pair of leavens and I love it just off the material alone Look, oh my god that beautiful now These right here It only makes sense that the trophy room sevens belong on the trophy case Like the once again love the metallic feature on the back the metallic jump man I love the metallic tips up brother. I love this shoe, bro This is one of my favorite shoes to wear. Ah man They did a very good job on these bro.  It says new sheriff in town and these are the new sheriffs in town I love wearing these shoes the box that it came in is dope as hell as well It's like a basketball court. Love these shoes. So it made sense. They were on the shelf now these The DMP six is pretty much even though it's not part of the DMP pack I call them the DMP sixes because that's basically what they are now shout out to my cousin Patrick man He's one of the people that got me into Jordan's I remember when he had the original DMP package the gold box package that came with the DMP sixes Jordan sixes and And it had the DMP elevens with the gold jump man Which is supposed to be re-releasing this year. So, you know, I had to get it. No, I had to get this love it Look at the Jordan dog tag on there, man I just the metallic back ring The back on the Jordan sixes. I love this shoe I will definitely wore knees in the buttery slate love this shoe man one of my favorite So, yeah, and for those who don't know Jordan sixes is my favorite number of Jordan and Since we got the gold we got the silver and gold combo Even though these are called the chrome sixes what I like about got like the the prominent 23 on the back with the chrome or whatnot. It's pretty much just you know, the silver and gold collection That's what I like to call it and the boxes reflect the same way. I have some of the boxes in my closet But this is part of the trophy case and at some point there's gonna be some rearrangements I usually rearrange the trophy case Just depending on, you know, what new shoes I get and I feel like deserve to be there. All right next The electric green Jordan sixes for love this colorway barely wear these Especially, you know, when I'm out and about somewhere and the shoes just be glowing in the dark These bad boys is nice. And like I said, Jordan sixes are my favorite number now When they decided to put the border of the border of colorway on the Jordan sixes It was a must have for me. These are the border sixes. I love the border sevens I used to have me appear, but they got torn up. I love the border sixes again Love Jordan sixes even the inside looks beautiful. They did a great job on Recreating the border colorway on the sixes and apparently they're supposed to be dropping like the aqua colorway on The Jordan sixes as well this year.  I know they released some with the jump man on the back I've always preferred the Carmine sixes with the Nike air in the back. It just looks better to me I'm my honest opinion, but these bad boys is tough. Love them. God. I was able to get them barely wear them But still love these bad boys Now these right here I Happened upon these once again They pretty much put a seven colorway on a Jordan six. These are the hair sixes man I've always wanted a pair of the hair sevens I think they did a good job with these as well inside of the soul looks great the outside material with the With the suede looks good and I like the bubblegum bottom, you know, it's kind of dirty looks very good They did a good job. I love when they for whatever reason put seven colorways on the Jordan sixes They always kill it. So love that Back with another pair The Georgetown sixes love the all suede. They did a really good job on this All suede around it man Love it. It's just you know, George kind of Georgetown colorway can't go wrong with it. Looks good. I've worn these maybe twice I love the box that it comes in the box that it comes in. It's pretty cool as well We're getting to the UNC sixes Love these love and love me a UNC colorway love the suede on it Love the little stitching on the back love the insole have the designs in there And also, they're supposed to be dropping the UNC fives next month in March. So, you know, I'm definitely gonna be checking that out And I'm getting those and I'm definitely probably gonna do a Unboxing for you guys if you guys want that man. All right, and I think that is all of my sixes Um, I didn't get a chance to count about the pair of 13s I got I got one two three four five six seven eight pair of Jordan 13s how many pair of sixes I got one two three four five six seven eight pair of Jordan sixes Not bad. No, these are only pair of threes. I have the cardinal threes These are actually my first pair of threes I've ever owned. So I like the quality in here. I like the quality within the shoe how it feels like inside the shoe or whatnot. Um, I Do need to get another pair of threes I think there's some threes that I definitely want to get this some more threes this year But I do like the cardinals haven't worn them too much, but these bad boys are nice now These right here These means something to me if I can open it up. I don't want to break it y'all I'm gonna get the there we go. I ain't trying to break this the citrus Sevens people slip on these. I don't know why but I remember in high school always wanted a pair of these These were a pair of Jordan sevens. I always wanted and when they dropped I had to get them I don't know why people are sleeping on them. Love the buttery slag swayed. They did a real good job on Re-releasing these these citrus sevens to me. I love them. I love them And if you have a chance to get them go ahead and get them bro. I love the citrus sevens They did a fantastic job on this shoe. Don't know why people slept on them, but yeah, love these sevens All right, and we're almost done with the collection What not All right, let's start with the the last year's Christmas release the cherry elevens Love these man. Love how they look the red on there looks good quality on these look good I think I've only worn them maybe twice I was able to get them for a little bit over retail But no the quality on these are very very good man So I love these not much to say about them. He's a nice pair of elevens, but my favorite pair of leavens are these right now Of course I had to talk about these right here these joints right here have you know done me well the jubilee Jordan 11's man. I remember when I got these I got these I got a pair from me and Man, I happened to get them on release day or what not But the metallic jump man, like I said a lot. I love I love more of the metallic finish on the 23 Like like what they did with the the straps Like on as you can see like on the straps or what not on the shoe. I love this This is just this I really wore this shoe so many times Love these bad boys. I'm gonna always keep these these bad boys Have a special place in my heart. Love them. Love them. Love them now these I like to call the The the Easter the Easter Sunday Jordan 5 now these are tough Love the material on these I love the sway material Well, what makes these dope is they glow in the dark say for example, you're walking outside you come inside They this part Just lights up and it glows in the dark. Oh my god. These are so cool Gotten so many good compliments every time I pull these out But only wear them like twice twice maybe three times love these fives man. Glad I was able to get them when they released them right here Concord fives I was able to get them on sale when they did a Re-release last year for Christmas or whatnot pretty simple. I love the concord cutaway I had I was like, you know, they're they're on the store So, all right, let me go ahead and get me a pair man. Love these bad boys right here as well These are the bluebird Jordan 5's love the material all the way around these only are for women This was worth the purchase man Love the the the satin material as you recall it on the inside love the way that feels I get a lot of compliments anytime I've worn these I get a lot of compliments love these bad boys Love them. Love them. Love them man.  They be having some of the best colorways and it's not even a joke Of course I got these as a birthday gift shout out to the homie dub and true billy They got these for me the raging bull fives man. Love these always one of them. Glad I got them Uh, they're supposed to be dropping like some um, I guess you can they're like Raging bull sixes pretty much or you know tour bravo six is whatever you want to call them They're supposed to be dropping them and y'all know I love me some six So I'm definitely gonna be getting these with these love the material love the box that came in Can't go wrong with it raging bull fives is a must have in any Jordan collection if you do got them and Last but not least playoff 12s rock with these man I was able to just happen to get them at one point or whatnot Love them these are actually I want to say I haven't had a pair of 12s since I was kid Since I was a kid my first pair of 12s happened to be the 12s they planned on releasing this year the cherry 12 So I can't wait to get those but these are like my second pair of 12s ever in my life playoff 12 So I was happy I was able to scoop these bad boys up And that's pretty much it for the jordan collection. Um, I have Check how many pair of fives I have one two three four got four pair of fives. I got Four pair of 11s two pair sevens one pair of threes. So yeah, that's that's pretty much a one pair 12s That's pretty much the jordan collection Also, I got these right here You gotta always have you a pair of some icy white forces, man Got me a pair of icy white forces, you know, nothing too crazy. That's they just been chilling in the box I pulled them out whenever I feel like wearing them. I'm only worn them like maybe three times If that so, uh, got me a pair of icy white forces. That's about it Just sitting off to the side and that's it man. Uh, I plan on putting Uh, some shoes there, but I can't tell you what it is though. But uh, yeah, that's pretty much the jordan Uh shoe collection that I have right now Well, I hope you guys enjoyed the tour of the shoes that I uh have recently acquired in some of the shoes I've been had for a while. Hopefully you guys enjoy checking them out. So like I said, uh, during the showcase of the shoes I do plan on doing some unboxing, uh Videos of some new shoes that I I plan on getting and I can't tell you what the next one The next unboxing is because I already have the shoes I'm kind of keeping it hush hush, but I definitely do plan on recording that for you guys and uploading it On the channel, man, uh, I definitely wanted to venture out and do some other video content I'm still gonna be doing the wrestling reactions because that's you know, I love me some wrestling So don't think that's not gonna happen But I'm gonna be incorporating some more shoe Unboxings and I'm also gonna be incorporating some other stuff I I can't tell you yet But I think a lot of you guys are gonna like some of the new content I have on the way, bro I gotta keep everything under wraps. But hopefully you guys Enjoyed this video, man. Let me know if you guys are excited for me to do some more Uh, um, uh, well for me to start doing some shoe unboxing videos I know like I said, I posted a poll on twitter and on instagram And there's overwhelming support from you guys that follow me there Saying that you want me to do some shoe unboxing videos So be on the lookout for that if you enjoyed this video you like the Checking out the shoe content you want me to do some more shoe related content hit that like button It really means a lot and let me know what pair shoes a pair of Jordans or Nike Nike shoes or whatever pair you like. It doesn't even have to be Jordan or Nike It can be whatever shoes that you like to wear. Let me know down below. What kicks do you guys like to wear?  So let me know what shoes you guys be rocking down in the comments below And if you do have some uh some Jordans or whatnot, let me know Do you have some of the Jordans that I I've shown in this video? Let me know on what not so but I appreciate all the love and support you guys have shown on the channel Road to 150k. I appreciate y'all kicking with me. See y'all next one. Peace