POPULARITY
This week on The Future of Security Operations podcast, Thomas is joined by Prima Virani. Prima is a security engineer who worked across industries as varied as oil and gas and Fintech before becoming Principal Security Engineer at Twilio. With over a decade of experience spanning infrastructure security engineering, incident detection and response, and forensics, she's also shared insights at countless security conferences around the world, including SecTOR Canada and Agile India. In this episode, Prima and Thomas discuss: - The unique challenges of working in forensics - Her transition to detection and response and cloud security - Building a security detection framework at Segment - Reducing mean time to resolve through automation - Using data to prioritize which processes should be automated - Merging teams and technologies when Segment was acquired by Twilio - Joining the securing platform engineering team at Twilio - Designing a challenging and varied career in security - The influence of mentorship on career growth - Democratizing security through knowledge sharing - How security will change in the next five years The Future of Security Operations is brought to you by Tines, the smart, secure workflow builder that powers some of the world's most important workflows. https://www.tines.com/solutions/security Where to find Prima Virani: Twitter: https://twitter.com/secnerdette?lang=en LinkedIn: https://www.linkedin.com/in/primavirani/ Twilio: https://www.twilio.com/en-us Where to find Thomas Kinsella: Twitter/X: https://twitter.com/thomasksec LinkedIn: https://www.linkedin.com/in/thomas-kinsella/ Resources mentioned: Hosting Fleet on AWS EKS by Prima Virani: https://segment.com/blog/hosting-fleetdm-on-aws-eks/ Fleet Device Management: https://fleetdm.com/ In this episode: [02:22] Prima's introduction to cybersecurity career opportunities as a teenager [06:30] The shift from forensics to detection and response [09:15] Gaining experience in vulnerability and patch management, and network security [14:15] Building a security detection framework at Segment using SOCless [18:10] Using automation to reduce alert noise and improve response times [20:30] The impact of automation on security team burnout [22:50] Merging security teams, practices and technologies during Twilio's acquisition of Segment [25:30] Moving to the securing platform engineering team at Twilio [27:40] Growing her knowledge of AWS, Kubernetes and GCP [32:40] Prima's plans to embrace machine learning in detection engineering [34:20] The importance of mentorship and knowledge sharing in career growth [37:30] Prima's all-time favorite projects, including hosting FleetDM on AWS EKS [39:36] The future of security operations through Prima's eyes [42:01] Prima's advice for security practitioners [43:58] Connect with Prima
In this episode, Naresh Jain, Developer, Consultant, Conference Producer and Startup Founder of Xnsio shares his insights and experiences related to - Starting his career 20 years back building Neural networks for ISRO, and how he got into corporate life- His experience reading the paper “Test infected” by Kent. How it helped him see the value behind extreme programming- How he and his friends put together the first Agile India conference from 2004- Challenges that comes across while organising different community- based conferences- How to build communities using conferences- His approach to put a good program/conference together- How to balance the aspiring and the experienced speakers, which gives equal opportunities to both- How he landed up as a coach/mentor and influence people while working in Thoughtworks- Differences between roles of coach, mentor, trainer and a captain- His love for coding and difference between code room (one step at a time) and board room (quantum leap)- How he handles a board room coming with expectations and big transformations- How to unlearn what you think is the best practice and how it helped him. Re-evaluate yourself- What you can expect in the upcoming “Agile India conference” - How Ward inspires him as a great speaker - His view on full stack - His advice for aspiring coaches/Mentors- Agile India conference to be held : Nov 18th-20th a 3 day conference More details at: https://2021.agileindia.org/ Naresh Jain is an award-winning, internationally recognized Technology & Product Development Expert. Over the last 15 years, he has helped many Unicorns and fortune 500 companies like Jio, Google, Amazon, JP Morgan, Hike, Directi, HP, Siemens Medical, GE Energy, Schlumberger, Shell, Dell, EMC, CA Technologies, etc. to streamline their product development. His hands-on approach of coaching teams by focusing on product discovery and engineering excellence is a key differentiator. In 2004, Naresh started the Agile movement in India by creating the Agile Software community of India, a registered non-profit society to evangelize Agile, Lean and other Leading-Edge Software Development methods. He is responsible for creating and organizing 100+ international conferences. In recognition of his accomplishments, in 2007 the Agile Alliance awarded Naresh with the Gordon Pask Award for contributions to the Agile Community.You can find more about him here: https://confengine.com/user/naresh-jain Contact handles:Twitter: https://twitter.com/nashjainLinkedIn: https://www.linkedin.com/in/nareshjain/Website: https://nareshjain.com/
https://go.dok.community/slack https://dok.community/ ABSTRACT OF THE TALK Prima and Tammy join us to discuss the bridges between Security and SRE. How can these two teams work best together? What can they learn from each other? Prima is a Security Engineer and Tammy is a Site Reliability Engineer. They are both Australians living in the USA with 10+ years of experience each working in tech. TALK TAKEAWAYS 1.You'll learn tips for SRE and Security teams to work together 2.You'll learn what SREs can learn from Security and vice versa 3.You'll learn about the new field of DevSecOps and how it can help your organisation improve BIO Tammy Bryant Butow is a principal SRE at Gremlin, where she works on chaos engineering—the facilitation of controlled experiments to identify improvements. Gremlin's enterprise Chaos Engineering platform makes it easy to build more reliable applications in order to prevent outages, innovate faster, and earn customer trust. Previously, Tammy led SRE teams at Dropbox responsible for the databases and storage systems used by over 500 million customers and was an IMOC (incident manager on call), where she was responsible for managing and resolving high-severity incidents across the company. She has also worked in infrastructure engineering, security engineering, and product engineering. Tammy is the cofounder of Girl Geek Academy, a global movement to teach one million women technical skills by 2025. Tammy is an Australian and enjoys riding bikes, skateboarding, snowboarding, and surfing. She also loves mosh pits, crowd surfing, metal, and hardcore punk. Prima is a seasoned Security professional who has worked in a variety of industries such as Consumer Tech, Oil & Gas, Media, and Fin-tech. She is a Senior Security Engineer on the SIRT team at Segment where she enjoys creating automation tooling for Incident Response and occasionally dabbles in Security DevOps. She loves sharing her experiences with the industry and has spoken at many meetups and conferences globally including, but not limited to, Agile India 2020, MacDevOpsCon Vancouver 2019, and Grace Hopper Conference 2017.
Raghu Kashyap is the Co-Founder and CTO of Intentwise, an AI-based technology platform that is helping a large number of brands, agencies, and sellers worldwide to optimize their Amazon advertising spend. Advertisers in over 11 countries are leveraging the Intentwise platform to drive their Amazon growth. Raghu has spoken at conferences such as Gartner, Techweek Chicago, Agile India, and The Fifth Elephant. In this episode, Raghu shares his thoughts on the following topics: Entrepreneurship journey Challenges and Learnings Helpful habits and routine Gaps in the education system Handling competition Words for the youth Being cheerful Connect with Raghu Kashyap:LinkedIn: https://www.linkedin.com/in/raghukashyap/ Connect with Intentwise: Website: https://intentwise.com/ LinkedIn: https://www.linkedin.com/company/intenwise Connect with me: LinkedIn: https://www.linkedin.com/in/gautamsrikrishna Twitter: https://twitter.com/gautamhs Facebook: https://www.facebook.com/gautam.srikrishna I'd appreciate it if you can leave me a review. Thanks for listening! --- Send in a voice message: https://podcasters.spotify.com/pod/show/gautam-srikrishna/message
In this episode, Shahin and Declan talked about Agile Alliance. Some of the topic covered are as follow: Agile Alliance history Best Job Ever, Agile 2014 (Diana Larsen Dance) Agile Alliance Certification Post Agile XP Conference (and other conferences) Agile India OnAgile Deliver Agile Conference Agile Coach Camp Worldwide Agile Alliance Initiative Lean Agile Network Agile Alliance Board of Directors Agile 2020 Agile Alliance Volunteering We mentioned the following people: Diana Larsen How to contact Declan: LinkedIn Twitter Email For more details please visit http://podcast.leanonagile.com. Twitter: twitter.com/LeanOnAgileShow LinkedIn: linkedin.com/company/lean-on-agile
In this podcast, recorded at the Agile India 2019 conference, Shane Hastie, Lead Editor for Culture & Methods, spoke to Maartje Wolff and Fennande van der Meulen. Why listen to this podcast: • If you want to transform organisations and make them future-proof, then happiness is crucial to success because happy people get better outcomes • When people feel they have a meaningful job that contributes to meaningful results, feel connected to their colleagues and are able to have fun at work they are more engaged which gives better results for the individuals and for the company • The drivers for happiness are different for each person – there is no single recipe that can be applied to every organisation • Happy companies have formulated their purpose very clearly and have translated that purpose to values and linked those values to behaviours • The four pillars of a happy workplace are: o Purpose – having a meaningful job o People – feeling connected, belonging to the group o Progress – making progress towards meaningful goals is the best motivator at work o Play – being able to have fun at work More on this: Quick scan our curated show notes on InfoQ https://bit.ly/2QBD6Ru You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq Subscribe: www.youtube.com/infoq Like InfoQ on Facebook: bit.ly/2jmlyG8 Follow on Twitter: twitter.com/InfoQ Follow on LinkedIn: www.linkedin.com/company/infoq Check the landing page on InfoQ: https://bit.ly/2QBD6Ru
In this podcast, recorded at the Agile India 2019 conference, Shane Hastie, Lead Editor for Culture & Methods, spoke to Dave Farley about what it means to build a real profession of software engineering. Why listen to this podcast: • At the very hard end of computing you need genuine engineering disciplines to be successful • Most of the previous definitions of software engineering have got it wrong because they tried to be too prescriptive • In many ways software development is a fashion industry – we chose technologies, languages and approaches based on who if the most persuasive orator rather than empirical evidence • Extreme Programming and continuous delivery have the characteristics of genuine engineering disciplines because they are focused on the engineering practices that enable you to build high-quality products fast • Pair programming unlocks the capability of individuals and teams to learn More on this: Quick scan our curated show notes on InfoQ https://bit.ly/33B2YAz You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq Subscribe: www.youtube.com/infoq Like InfoQ on Facebook: bit.ly/2jmlyG8 Follow on Twitter: twitter.com/InfoQ Follow on LinkedIn: www.linkedin.com/company/infoq Check the landing page on InfoQ: https://bit.ly/33B2YAz
This is the Engineering Culture Podcast, from the people behind InfoQ.com and the QCon conferences. In this podcast, recorded at the Agile India 2019 conference, Shane Hastie, Lead Editor for Culture & Methods, first spoke to Jeremy Kriegel about design innovation and then with Doc Norton about why Tuckman was wrong and how dynamic reteaming makes organisations more resilient. Why listen to this podcast: • Working to bring the design and agile communities together because there is a lot of synergy between and unfortunately there has been a lot of antagonism between practitioners in the two fields • Agile done well compliments UX and design, however some of the agile anti-patterns have burned UX designers • UX designers think holistically because customers experience products as complete things, they don’t experience them in pieces and if the product is built in pieces and those pieces don’t form a cohesive whole then the user experience is compromised • When developers watch someone struggle with their product there’s a dramatic change in the way teams approach their work More on this: Quick scan our curated show notes on InfoQ https://bit.ly/2nQUi9h You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq Subscribe: www.youtube.com/infoq Like InfoQ on Facebook: bit.ly/2jmlyG8 Follow on Twitter: twitter.com/InfoQ Follow on LinkedIn: www.linkedin.com/company/infoq Check the landing page on InfoQ: https://bit.ly/2nQUi9h
This is the Engineering Culture Podcast, from the people behind InfoQ.com and the QCon conferences. In this podcast, recorded at the Agile India 2019 conference, Shane Hastie, Lead Editor for Culture & Methods, spoke to Deb Preuss about life coaching, creating joyful workplaces, diversity and inclusion.
In this podcast recorded at the Agile India conference Shane Hastie, Lead Editor for Culture & Methods, spoke to Nigel Dalton, Chief Inventor at REA Group about his experiences and the need to take back management as an important practice in today’s organisations Why listen to this podcast: • There is a science of invention – deliberately combining things that you might not have thought of combining before • What matters more than having an agile process is having a resilient organisation – bounce-back-ability • The four elements which need to be present for sustainable success are good management, resilience, creativity and agility • Management as a profession and practice has become tainted and unpopular, yet good management is critical to organisation success • The more organizations that can apply humanistic values, lean principles, value focus, flow of work and continuous improvement the stronger the economy will become More on this: Quick scan our curated show notes on InfoQ hhttps://bit.ly/2HQNoJW You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq Subscribe: www.youtube.com/infoq Like InfoQ on Facebook: bit.ly/2jmlyG8 Follow on Twitter: twitter.com/InfoQ Follow on LinkedIn: www.linkedin.com/company/infoq Check the landing page on InfoQ: https://bit.ly/2HQNoJW
Craig is at YOW! Lambda Jam in Sydney and speaks with Naresh Jain, co-founder of the Agile Software Community of India (organising body of Agile India), conference organiser of many other software conferences in India and creator of ConfEngine and they chat about: The original Test Infected article Cruise Control started as an idea to write … Continue reading →
In this episode we talk about (00:39) the problem with calling Agile adoption being done and letting go of the coaches; (05:59) story points being a time estimate rather than a relative size estimation. How can a coach change this mindset?; (21:03) How to encourage continuous development in a company that is already doing agile?; (27:49) As a coach, are there any concerns you see with organizations implementing SAFe? Is there anything you would caution others to be wary of?; (34:30) How much of agile is the team structures Vs work methods/approaches?; (40:17) Wrap up join me at Agile Open Northwest in Feb and Agile India in March. More info: http://https://2019.agileindia.org/; take a look at ING bank http://https://vimeo.com/312152257 Support the show (https://www.agilealliance.org/membership-pricing/)
Esther Derby (@estherderby) and Faye Thompson (@agilefaye) and Amitai Schleier (@schmonz) joined Ryan Ripley (@ryanripley) to discuss how to respect the agency of agile and scrum teams. [featured-image single_newwindow=”false”]Respecting the Team[/featured-image] In this episode you’ll discover: Why Retrospectives are critical to continuous improvementHow maintaining a teams agency can boost morale and performanceWhy respect is critical to an agile practice Links from the show: Powerful Retrospective by Esther Derby – https://estherderby.teachable.com/p/retrospectives/USE THE CODE AGILE4HUMANS for 15% off!Technology of Participation classes: https://icausa.memberclicks.net/Agile 2019 Submissions – https://submissions.agilealliance.org/agile2019Agile India – https://2019.agileindia.org/Mobodoro – http://barneydellar.blogspot.com/2018/05/mobodoro.htmlDevOpsDays NYC 2019 – https://www.devopsdays.org/events/2019-new-york-city/welcome/Amitai’s Consulting Company – https://latentagility.com/services/ How to Support the Show: Thank you for your support. Here are some of the ways to contribute that were discussed during this episode: Share the show with friends, family, colleagues, and co-workers. Sharing helps get the word out about Agile for HumansRate us on iTunes and leave an honest reviewJoin the mailing list – Check out the form on the right side of the pageTake the survey – totally anonymous and helps us get a better idea of who is listening and what they are interested inTechwell events – use the code AGILEDEV when you sign up for Agile Dev East in Orlando, FL November 5th – 10th.Leadership Gift ProgramMake a donation via Patreon [callout]This pocket guide is the one book to read for everyone who wants to learn about Scrum. The book covers all roles, rules and the main principles underpinning Scrum, and is based on the Scrum Guide Edition 2013. A broader context to this fundamental description of Scrum is given by describing the past and the future of Scrum. The author, Gunther Verheyen, has created a concise, yet complete and passionate reference about Scrum. The book demonstrates his core view that Scrum is about a journey, a journey of discovery and fun. He designed the book to be a helpful guide on that journey. Click here to purchase on Amazon.[/callout] [reminder]Which topic resonated with you? Please leave your thoughts in the comment section below.[/reminder] Want to hear another podcast about the life of an agile coach? — Listen to my conversation with Zach Bonaker, Diane Zajac-Woodie, and Amitai Schlair on episode 39. We discuss growing an agile practice and how coaches help create the environments where agile ideas can flourish. The post AFH 103: Respecting Your Scrum and Agile Teams appeared first on Ryan Ripley.
In this podcast recorded at the Agile India conference Shane Hastie, Lead Editor for Culture & Methods, spoke to John Le Drew about solving technical problems by addressing the people issues. Why listen to this podcast: • Very diverse teams will naturally have conflict, but they still produce better outcomes despite the journey being more of a struggle to get there • Cognitive biases are real and are an evolutionary survival tactic and we need to be very mindful of them • We all like to think that we aren’t biased, but the imbalances in team formation and hiring practices are still perpetuated • We can’t reprogram our brains to remove biases, the way to overcome them is to be aware of them • If you address your people as unique human beings with individual needs and work out how to support them in the best way possible for their needs then you will get better outcomes More on this: Quick scan our curated show notes on InfoQ https://bit.ly/2x79tfD You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq Subscribe: www.youtube.com/infoq Like InfoQ on Facebook: bit.ly/2jmlyG8 Follow on Twitter: twitter.com/InfoQ Follow on LinkedIn: www.linkedin.com/company/infoq Check the landing page on InfoQ: https://bit.ly/2x79tfD
Tammy Gretz and Wendy Jacobs discuss their talk "From Self Obsession to Self Selection: A Scaled Org's Journey to Value Reorganization" at Agile2018. Transcript Tammy Gretz Wendy Jacobs ‑ Agile2018 Bob Payne: "The Agile toolkit." [music] Bob: Hi. I'm your host, Bob Payne. I'm here with Tammy Gretz of [inaudible 0:25] ... [laughter] Bob: ...and Wendy Jacobs. We've chatted a bit before this, but this is the first time you guys are doing a podcast, I think. Wendy Jacobs: A live podcast, yes. Bob: A live podcast. Wendy: Correct. Bob: This is recorded. [laughter] Bob: You still have had to come. Wendy: This is the first live or recorded podcast for me. There you go. [laughter] Bob: You are doing a talk and it's related to team self‑selection, From Self‑Obsession to Self‑Selection. What's that all about? How do you two work together? What's your back story? What's the talk? Wendy: I work at AEP, American Electric Power ‑‑ this is Wendy ‑‑ and Tammy and I work together there. She is a Scrum master on one of the teams working through our Agile partner, Cardinal Solutions. We started working together when she joined the team that we actually talk about. Tammy Gretz: I was coming from it from a prospective of, it was a new team and I was there to teach them Scrum. They had never done it before. Bob: Is this new to the whole organization or just to this team? Wendy: We are in a multi‑year Agile transformation. The self‑selection and scaling, which is another aspect of the talk that we're doing, is new to the organization. This was the experiment. Bob: How long have you been running Agile teams before you hit scaling and self‑selection? Tammy: Before I came to AEP, I had been working about two or three years in an Agile environment. The AEP transformation, I believe, has been between seven and nine years. Bob: Usually teams don't get to self‑selection until they've been doing it for a while. Wendy: The group of teams that we're talking about, one of them was new when Tammy came in, newly into Scrum. The other two had been Scrum teams for a couple of years. Bob: What was the self‑obsession portion of the program? Tammy: [laughs] My team specifically was new to Scrum. The intention wasn't to go to scaling or do this whole self‑selection when I first started. It was teach this team Scrum and figure out how to get them working with the other two teams. We quickly realized that there were a lot of moving parts that need to have some kind of an organization or some framework to work with. Wendy: The self‑obsession aspect is just human. We're worried about ourselves. When we're talking about having to all come together and do self‑selection event that involves trying to figure out how to deliver the most value to the company, you have to shed that self‑obsession, that selfishness and become selfless, because you have to see, where can I help most? This was a journey to take the individuals into teaming, into the ability to do self‑selection. That's where the... Bob: Also, there's team identity, which you blow up with self‑selection. What is the event that caused you to say, "Hey, we need to kind of shake the snow globe here?" [laughs] Wendy: We took a scaling class with a very experiment‑tolerant manager, we like to call her Andrea. Bob: Because that's her name. [laughter] Wendy: Protecting the innocent, whatever. Anyway, there was a kernel of it in there. One of the gentlemen on my team, he had a white paper on self‑selection for teams. We had begun talking about it. He sent her the white paper. We like to call him Greg. He sent her the white paper to just wet the whistle. Get the juices flowing about what does it really mean to do that, and she loved it. She loved the empowerment to the teams to be able... Bob: It wasn't by Amber King was it? Wendy: I don't recall. We can check. [laughter] Bob: That would be interesting. She's a good friend of ours and she did a white paper on self‑selection at Cap One. It's possible. Wendy: Very well possible. That was the kernel of it. She got a hold of that and really embraced it, and thought, "This could..." We were in a scenario where we wanted to make sure that the teams were formed in a way that delivered the value best. We were focusing on the value delivery. She worked with her business partners to define what those value streams were. Instead of just saying, "OK, you're on this team, and you're on this team, and you're on this team," she decided to let the teams decide, "Where does your value heart sing? Where do you want to put your focus?" thus lead us to self‑selection event. Bob: How many people? Tammy: Thirty‑four. Bob: How many teams did you end up with? Wendy: Six squads. That was a very critical word in this. We went from three teams to six squads because we're all part of one team. In a scaling event, you're really part of one team. She was really very specific about wanting to call these squads up to the general team. Bob: How did it go? I'm sure some people were the Cookie Monster characters for the self‑selection. Some people... Wendy: People were people. [laughs] Bob: ...wanted to be told where go. "Tell me where to sit." [laughs] Wendy: Exactly. It's all human. Think about being here at this conference. This is something we're going to talk about tomorrow, is that, how do you even select what session to go to? How do you figure out where you're going to sit? There's all sorts of reasons in your head. Tammy: Nobody has the same two reasons. People pick things for weird reasons. They pick them for very specific, concrete reasons. You can't plan for that. Wendy: The event went well. It was a two‑day event. The self‑selection took place the first day. We had some teaming main events on the second day to try to make sure that they were ready to go. Team agreements and let's talk about the definitions. During the actual self‑selection event, Andrea took care to really plan this. We helped her. We met for a couple months to plan this event. She made it fun. She made it seasonal. [laughs] It was right near Valentine's Day. There was a Valentine's Day theme to the whole thing. I was very impressed with what she came up with. Just the creativity that came out of her. Tammy: For me, I was more of a participant during this. I was embedded in the team and Wendy was a coach with the team. She was working with the manager. It was very interesting to experience what maybe my other coworkers on the team, my other teammates, what they were experiencing, even though I knew what was coming. I still had that knee‑jerk reaction to be a human, and be like, "Oh, you want me to...? Oh, I got to do this? I don't care. Just put me wherever." [laughs] Bob: Did you end up with any value streams that were starved of folks and then have to re‑negotiate? Wendy: Interesting you ask. [laughter] Wendy: Have you seen our talk? No. [laughter] Bob: I've seen self‑selection events. Wendy: That was actually the exciting moment. One of the exciting moments of this experience is that there were five total iterations to get to our final teams. It was after iteration four, and we had a starved squad. There wasn't anyone on one of the value streams. The managers stood up and said, "Hey, how are we going to deliver this? How are we going to deliver this value?" It was there that the Scrum value, courage, popped up its head. A couple of people were like, "We want that. We can take that on," and got up from where their friends were, where they felt comfortable, walked over that table and planted themselves, and said, "We got it." It was awesome. Bob: Was it just Andrea? Wendy: Yeah. [laughs] Bob: Was she the advocate for each of them, or were there value stream owners that were...? Wendy: The product owners were there and they come from the business. They were participating in this. Their management was there, too, watching, helping, and answering any questions if we had any, but Andrea was the manager of most of the people in the room. The answer is she advocated for all the teams and wanted to make sure that we came out with something that would benefit the company overall. Bob: Is this a one‑time event or are you periodically revisiting as the demands on value streams change? [laughter] Tammy: Actually, part of the agreement was that if they didn't like where they were, they had a chance to do it again in six months. We're right about at six months right now. They have come back and said, "Maybe we didn't think about this in the right way, necessarily, and we were still self‑obsessed a little bit." Now they're starting to see where, "Oh, maybe it might have been better if these two people were flopped," or, "This value stream might be a little better tweaked." They're learning from it. We're hopeful that they'll get to do that again here shortly. Interestingly enough, we have another group here that is going to be talking about another way that they did it. I've moved on to a different team and I've just completed another self‑selection there [laughs] with that team because they were growing. They were a smaller team and they realized that they needed to hire more. They hired four more people, which made them a massive team. We had to have discussions around the same kind of thing. We learned a lot from the first one, [laughs] applied it to this one. This one went really smoothly. It didn't take quite as long, but it was... Wendy: The whole company's very supportive of continuous improvement. That's part of our culture, we're a continuous improvement company. I've helped with another self‑selection event not long after the one we did in February, and it was different. We've done it a couple different ways and we're learning each time from it. Tammy has the benefit in her current team to apply all the learnings we had and munge some of that together so they would have a very smooth event. Bob: One of the things that I've seen in some places, as the business demands change, certain value streams will become higher in priority, where more work needs to flow through them. Have you guys experienced that yet or is that a future event? Tammy: We might be going through it pretty soon. [laughs] Wendy: With the current team you're on? Tammy: Yeah. Wendy: The current team that she's on, they are going to be sized a little differently based on the amount of stuff that's going to come through them. It is possible that that team may split again, the larger team. We're really looking at what makes the most sense. We're doing these experiments to try to understand what's working, what's not working, how can we tweak it? The managers are just very open and very wanting to try these things to make it the best place that they can. Bob: One of the things that I saw one client do is quarterly, when they would do the equivalent of a cross‑program planning event, would then allow people to swap chairs, or they would shuffle demand, and say, "We need more folks over here, who would like to come join?" Then people would come, and they were like, "Oh shoot, we're too short over here." I don't know if they did five rounds. I don't remember exactly, but some number of... Tammy: It's funny you said shuffle chairs, because that was almost more important than which team they were on, is where they were going to sit. Bob: Oh yeah? [laughter] Wendy: "I want the window. No, I want the window." They're, again, human. [laughter] Tammy: It's all about the humans. It wasn't about the work. It was... Bob: The soft stuff is the hard stuff. [laughs] Agile's easy, people are hard. [laughter] Tammy: It's especially the different personality types. Even if we go really high‑level, introvert, extrovert, some of these things could be very hard for introverts, I think. You're speaking up and saying, "I want to go there." There's that shyness that they don't want to ruffle any...make any waves or do anything like that. All of these events, we've been very purposeful in thinking about that, making sure that there's no one really uncomfortable to a point where... Bob: They could be uncomfortable, but not really. Wendy: Self‑selection is uncomfortable. [laughter] Wendy: We don't want to push them so far. Bob: I wouldn't pick me. [laughter] Tammy: You should always pick yourself. [laughter] Bob: That's really exciting. Hoping that you'll get a good run of folks at that talk. It'll be very interesting. What else has been exciting about the conference? I know it's only day two. I believe you were at the Women in Agile. Did you do any of the camp before that, or just the Women in Agile? Wendy: I actually didn't know about the camp before. Now that I know that they happen... [laughter] Bob: They don't always happen. Wendy: I know there's one happening, I believe, in Chicago in October or something like that, I was told. Now I'll be looking into this because it sounds like an interesting place to share ideas, get some new thoughts about how to do some things. Improve the toolkit. Tammy: I'm really enjoying the Audacious Salons. Bob: Good. Tammy: Really enjoying them, a lot. [laughs] Bob: Were you there yesterday? Tammy: I was there for the leadership one, Agile Leadership. Today is The Next Big Idea. Wendy: We did hear the afternoon session was quite interesting. Quite charged. Tammy: I missed that. [laughs] Bob: George said they went hours over the slot. I know Lisa and George very well. George has been on the podcast many, many times. [laughter] Wendy: We are in good company. [laughter] Bob: We have the "Tips and Advice" series on Agile Toolkit Podcast. How was the Women in Agile event? I know you met Amanda there, my colleague. Wendy: Yes. Bob: Big Pete was there. I don't know if you met him? Wendy: I did not meet Pete. Did you meet Pete? Tammy: No. Wendy: Women in Agile, I enjoyed it. I like meeting people. I like meeting all kinds... Bob: You seem very shy. [laughter] Wendy: Believe it or not. [laughs] Tammy: She's the connector. She knows people, and she's like, "Hey, you guys should know each other." [laughs] Wendy: I do. I make sure everybody meets each other. I liked hearing people's stories about where they were in their Agile journey. The table I was at was a table that had no question to answer. We got to make up our own question that we wanted to answer, which was nice. We had a couple of folks at the table that weren't very far in their journey at all, and wanted to understand, what's the benefit of Agile over Waterfall? Those types of things. It was really very enjoyable to hear their perspectives on where they are and to try to share where I've been and where my enterprise is. It was a good event. I really loved hearing the new voices. There were two speakers that came in. They were reasonably new speakers. They had such wonderful stories. Tammy: They were really great. The two new speakers, the new voices, that was a great element to that conference piece of it, is having these new people get up and speak. Bob: Do you remember who they were? I wasn't there. No? Tammy: I talked to them last night. Bob: [laughs] They're super new voices. Real super nice people as well. [laughs] Wendy: Their story was really great. Tammy: Their stories were amazing. The things that they went through and now the places they've been, it's inspiring. I wish them all the best of luck and hope to get to do some of the...they've gone internationally and spoken, and that just sounds really cool and really fun. Just listening to how they did that was neat. Bob: There's a decent conference ‑‑ Agile India is quite good. The European conferences, I've not actually gone to those either. I'm looking forward to going internationally. Wendy: Maybe we should all go. Tammy: Yeah, let's go. [laughter] Tammy: What time does the plane leave? [laughs] Wendy: Let's do it. Bob: It's a red‑eye. [laughter] Tammy: That's what she's on tomorrow. Wendy: Yeah, I've got to take a red‑eye back. Bob: I'm sorry to hear that. I can't do it. I'm staying till Friday morning. Tammy: I'm staying the weekend. I wanted to get a couple extra days in just to enjoy the beautiful weather. Bob: The farmer's markets are actually fantastic if you like that sort of thing. Tammy: Absolutely. Bob: We had the Scrum gathering out here. I had my favorite breakfast ever, which was a sea urchin shell that had been cleaned out with micro‑greens, tuna pokÈ, more micro‑greens, and then the sea urchin laid out. Tammy: That is a very specific breakfast. Bob: Yeah. [laughter] Tammy: It's not waffles. Bob: It's not waffles. I had an iced coffee with it so that made it breakfast. Tammy: She wants waffles. Wendy: I'm obsessed with waffles right now. Tammy: She is, yes. Bob: I don't know that they make sea urchin waffles, but they might someplace. Wendy: I'm not sure that they should. [laughter] Wendy: Just saying. Bob: They should. Wendy: You do? Bob: Maybe a keto egg waffle with some sea urchin on would be good. What else are you looking forward to at this conference? Wendy: Speaking. [laughs] [crosstalk] Wendy: Actually getting through that. [laughs] Yes, the speaking would be a number high on the list. Honestly, I'm just looking for new ideas. I'm focusing more into the product space, the talks that are going on. I'm looking for some of those new things that I can take back. In my role, I am the product owner coach and I focus on the business side of things. I look for new tools I can use with them to help them understand why to do some of the things that we do, or just ways that they can do it better. Bob: The product discovery space, it takes almost a completely different tool set. The mechanics are relatively straightforward, but it is the divergent thinking. How do we winnow down these many ideas? How do we get it into that convergent process? Agile is a delivery process and it's a convergent one. I love that interplay of when you can get it going. A little bit of experimentation, divergent thinking. Let's build it, test it. Let's get some data out. Let's have that drive our next set off experiments or experiences. I'm assuming you've looked at Business Model Canvas and stuff. Wendy: Yep. [laughs] Tammy: Yep. Bob: Impact mapping. Wendy: Yep. [laughter] Tammy: It's all good. When I approach the coaching of product owners, I don't just dump, "Here. Here's all the tools. Try all of this at once." I layer it in, where, "Hey, I'm having a real problem with trying to figure out how to prioritize. Hey, I'm having a real problem deciding what should be our far‑afield thing? Where should we be heading towards? How do I lay it out for my stakeholders?" Things that people are probably listening to this and saying, "Well, duh." When you're new you don't know about this stuff. You can't overwhelm. Trying to find new tools that make it easier to embrace it and understand it, and may play on things they've done before, that's the things I look for to help them out. Bob: I'm sorry, you were... Wendy: No, go ahead. [laughs] Bob: Do you guys have user experience embedded in with your product teams or are they a separate agency kind of model, or a little bit of both? Wendy: A little bit of both. I'll say a little bit of both. Bob: That's great. Tammy: I was just going to say that I really like the Audacious Salon stuff because it's talking about a lot of the things we've already talked about in a new way or in a new light. I appreciate that. For me, working with the teams that I'm working with, I think they have been inundated with Agile and Scrum. How do we talk about it in a way that they can hear it, and not that stance of, "This is the only way." Bob: I've always thought that was a ridiculous notion that Agile was a thing to concentrate on. It's a tool. Toyota Production System wouldn't have rested on a single process for very long without changing itself. [laughs] It's a means to great product outcomes. Tammy: I try to break it down for them as much as possible. Obviously, we care about the frameworks that we're using, but I try to break it down into simple questions. Answer these simple questions and that will help you get to that thing you're trying to produce, your vision. That'll help you develop that vision. That'll help you develop that, "what's the next big thing?" I look for trying to, using Agile principles, break it down as small as possible to help them break through. Bob: Thank you very much. I really appreciate you guys coming in and chatting. I hope you have a great talk. Wendy: Thank you for asking us on the show. Tammy: Thank you. Bob: Although I think it's right at the same time as mine. Wendy: It is exactly the same time. [laughs] Bob: I hope it is not terribly well‑attended. [laughter] Tammy: Wow, I was going to say I hope you have a full house. [laughter] Bob: Thank you. Me, too. [laughs] No, I'm sure there are so many folks. We've got 2,300 people at this conference. We're both going to have the right...whoever shows are the right people. Wendy: Are the right people. Tammy: Exactly. Bob: It's open space principle. Tammy: Thanks for inviting us. Bob: Yeah, no problem. Wendy: Thank you very much. Bob: The Agile Toolkit Podcast is brought to you by Lithespeed. Thanks for tuning in. I hope you enjoyed today's show. If you'd like to give feedback or be on the show, you can ping me on Twitter. I am @AgileToolkit. You can also reach me at bob.payne@lithespeed.com. For more free resources, transcripts of the show, and information about our services, head over to lithespeed.com. Thanks for listening. [music]
Woody Zuill talks about Mob Programming and NoEstimates at Agile India 2017.
Kent McDonald, author of Beyond Requirements and co-author of Stand Back and Deliver, sat down with us at Agile India 2017 to talk about the differences between effectiveness and efficiency.
Steve Porter from Scrum.org talks about the myths and misconceptions surrounding Scrum at the Agile India 2017 conference.
In this edition of the Agile India Podcast, Chris and Sean will be discussing an upcoming talk by Jez Humble titled "Why Scaling Agile Doesn't Work" - https://confengine.com/agile-india-2017/proposal/3551/why-scaling-agile-doesnt-work Chris and Sean explore some of the challenges of scaling agile and what can be done about it. Below are some of the various resources discussed during this podcast: Scaling Lean & Agile Development - Craig Larman and Bas Vodde - https://www.amazon.in/Scaling-Lean-Agile-Development-Organizational-ebook/dp/B001PBSDIE?ie=UTF8&keywords=bas%20vodde&qid=1483152241&ref_=sr_1_3&sr=8-3 12 Signs You’re Working in a Feature Factory - https://hackernoon.com/12-signs-youre-working-in-a-feature-factory-44a5b938d6a2 Jez Humble - Principles of Lean Product Management - https://www.youtube.com/watch?v=cH6bnQzJojo Dynamic Reteaming - Heidi Helfand - https://leanpub.com/dynamicreteaming Team of Teams - General Stanley McChrystal - http://www.amazon.in/Team-Teams-Rules-Engagement-Complex/dp/1591847486/ref=sr_1_1?ie=UTF8&qid=1483152096&sr=8-1&keywords=team+of+teams Bridget Kromhout - Containers Will Not Fix Your Broken Culture - https://www.youtube.com/watch?v=UjhIA6QTy5k Nicole Forsgren - Continuous Delivery + DevOps = Awesome - https://www.youtube.com/watch?v=EuYS5NF1Uaw Agile Scaling Frameworks: Scaled Agile Framework (SAFe) - http://www.scaledagileframework.com/ LeSS - http://less.works/ Nexus - https://www.scrum.org/Resources/The-Nexus-Guide Disciplined Agile Delivery (DAD) - http://www.disciplinedagiledelivery.com/ Agile India 2017 will take place 6-12 March in Bengaluru. For more information, please visit 2017.agileindia.org/
Chris & Sean discuss the concept of Agile Mindset and what the means and how it contrasts with a focus on processes and tools. Agile India 2017 will take place 6-12 March in Bengaluru. For more information, please visit 2017.agileindia.org/
Chris & Sean discuss how thinking of work as firm fixed price contracts is at the root of many agile dysfunctions. Agile India 2017 will take place 6-12 March in Bengaluru. For more information, please visit http://2017.agileindia.org/
Chris Edwards and Sean Dunn discuss the topic of innovation. What makes companies innovative? What is it about the cultures and environments that allow people to explore and discover? What happens in organizations that prevents people from discovering new ways of working, new technologies, and new product ideas? Agile India 2017 will take place 6-12 March in Bengaluru. For more information, please visit http://2017.agileindia.org/
Rails Remote Conference 1:20 - Introducing James Shore Github Flow for Javascript Screen cast Email: jshore@jamesshore.com 1:40 - Freelancing and Consulting 5:20- Co-opting Agile and the movement away from technology/software Agile Alliance Technical Conference Agile Fluency Model 16:20- Evolutionary Design in Agile Ron Jeffries Sudoku Think Like A Git code visualization built with Gource 24:15 - Evolutionary Design for Beginners James Shore - Evolutionary Design Illustrated Stack Overflow 32:30 - Technical Practices and Agile Architecture Procrastinate on Purpose by Rory Vaden 39:10 - Engineering on a Team Level “No Silver Bullet” by Fred Brooks James Shore - Rethinking Scaling 52:10 - Redesigning Team Responsibilities Joy, Inc by Richard Sheridan Picks Sandi Metz “The Wrong Abstraction” blog post (Sam) Why Are Computers podcast by Tom Stewart (Sam) Netstat (Jess) Wood Badge (Charles) Remember the Titans (Charles) Rick Sheridan’s Agile India talk (James) Liftoff by Diana Larsen and Ainsley Nies (James)
Rails Remote Conference 1:20 - Introducing James Shore Github Flow for Javascript Screen cast Email: jshore@jamesshore.com 1:40 - Freelancing and Consulting 5:20- Co-opting Agile and the movement away from technology/software Agile Alliance Technical Conference Agile Fluency Model 16:20- Evolutionary Design in Agile Ron Jeffries Sudoku Think Like A Git code visualization built with Gource 24:15 - Evolutionary Design for Beginners James Shore - Evolutionary Design Illustrated Stack Overflow 32:30 - Technical Practices and Agile Architecture Procrastinate on Purpose by Rory Vaden 39:10 - Engineering on a Team Level “No Silver Bullet” by Fred Brooks James Shore - Rethinking Scaling 52:10 - Redesigning Team Responsibilities Joy, Inc by Richard Sheridan Picks Sandi Metz “The Wrong Abstraction” blog post (Sam) Why Are Computers podcast by Tom Stewart (Sam) Netstat (Jess) Wood Badge (Charles) Remember the Titans (Charles) Rick Sheridan’s Agile India talk (James) Liftoff by Diana Larsen and Ainsley Nies (James)
Rails Remote Conference 1:20 - Introducing James Shore Github Flow for Javascript Screen cast Email: jshore@jamesshore.com 1:40 - Freelancing and Consulting 5:20- Co-opting Agile and the movement away from technology/software Agile Alliance Technical Conference Agile Fluency Model 16:20- Evolutionary Design in Agile Ron Jeffries Sudoku Think Like A Git code visualization built with Gource 24:15 - Evolutionary Design for Beginners James Shore - Evolutionary Design Illustrated Stack Overflow 32:30 - Technical Practices and Agile Architecture Procrastinate on Purpose by Rory Vaden 39:10 - Engineering on a Team Level “No Silver Bullet” by Fred Brooks James Shore - Rethinking Scaling 52:10 - Redesigning Team Responsibilities Joy, Inc by Richard Sheridan Picks Sandi Metz “The Wrong Abstraction” blog post (Sam) Why Are Computers podcast by Tom Stewart (Sam) Netstat (Jess) Wood Badge (Charles) Remember the Titans (Charles) Rick Sheridan’s Agile India talk (James) Liftoff by Diana Larsen and Ainsley Nies (James)
Welcome to the Software Process and Measurement Cast 264 The Software Process and Measurement Cast 264 features my interview with Alexei Zheglov. We discussed lean, work-in-process limits and flow. A summary of Alexei's bio from LinkedIn . . . How does value flow through your knowledge-work organization? The reality for many knowledge-work organizations today is, not very well. Therefore, we need to design, evolve, discover and help better systems of work emerge. Alexei's present drive and ability to help guide people to those better ways go back to his programming since the 80s (professionally since the 90s), mastering many practices and discovering manyproblems and solutions. It was more than 10 years ago that I created my first test doubles and human-readable acceptance tests. He was in the engineering trenches of a lean startup long before there was such a term. Alexei doesn't "roll out" "methodologies." He draws from a large number of approaches - such as Kanban (and, by extension, many innovations rapidly created by the global Lean/Kanban community). A3 Thinking, Agile software engineering practices, and others - to discover solutions to problems and to help people learn and see why and how something we do is an improvement. Alexei has actively contributed to the Agile/Lean community in his part of the world over the last several years, emerged as an influencer at Canadian open-space Agile Coach Camps (2010-2013), organized and presented at many user group meetings, and spoke at larger forums such as Agile India 2012, Agile New England, AgileDC and three Canadian AgileTours: Montreal, Toronto, and Ottawa. He was one of the translators of the Stoos Communique in January 2012 and founded my region's Limited WIP Society chapter later that year to facilitate learning of the Kanban method and how Lean works in knowledge-work fields in general. His specialties include: Agile and Lean software development. How Lean works in knowledge-work fields. Agile technical practices. Kanban. Personal Kanban. Lean Startup. Systems thinking. Cynefin. Real Options Big concepts . . . a big interview! The Software Process and Measurement Cast has a sponsor . . . As many you know I do at least one webinar for the IT Metrics and Productivtity Intstiute (ITMPI) every year. The ITMPI provides a great service to the IT profession. ITMPI's mission is to pull together the expertise and educational efforts of the world's leading IT thought leaders and to create a single online destination where IT practitioners and executives can meet all of their educational and professional development needs. THe ITMPI offers a premium membership that gives members unlimited free access to 400 PDU accredited webinar recordings, and waives the PDU processing fees on all live and recorded webinars. The Software Process and Measurement Cast recieves a fee if you sign up using the URL in the show notes. http://mbsy.co/fGdw All revenue our sponsors goes for bandwidth, hosting and new cool equipment to create more and better content for you! Support the SPaMCAST and learn from the ITMPI! THe Software Process and Measurement Cast is a proud member of the Tech Podcast Network. If it is tech it is on the Tech Podcast Network. Check out the Software Process and Measurement and other great podcasts on the TPN! TPN: www.techpodcast.com Do you have a Facebook account? If you do please visit and like the Software Process and Measurement Cast page on Facebook. http://ow.ly/mWAgU The Daily Process Thoughts is my project designed to deliver a quick daily idea, thought or simple smile to help you become a better change agent. Each day you will get piece of thought provoking text and a picture or hand drawn chart to illustrate the idea being presented. The goal is to deliver every day; rain or shine, in sickness or in health or for better or worse! Check it out at www.tcagley.wordpress.com. Shameless Ad for my book! Mastering Software Project Management: Best Practices, Tools and Techniques co-authored by Murali Chematuri and myself and published by J. Ross Publishing. We have received unsolicited reviews like the following: "This book will prove that software projects should not be a tedious process, neither for you or your team." NOW AVAILABLE IN CHINESE! Have you bought your copy? Contact information for the Software Process and Measurement Cast Email: spamcastinfo@gmail.com Voicemail: +1-206-888-6111 Website: www.spamcast.net Twitter: www.twitter.com/tcagley Facebook: http://bit.ly/16fBWVContact information for the Software Process and Measurement Cast One more thing! Help support the SPaMCAST by reviewing and rating the Software Process and Measurement Cast on ITunes! It helps people find the cast. Next: The Software Process and Measurement Cast 265 our essay on retrospectives. If you are not doing retrospectives you are leaving productivity and satisfaction on the table.