Michael James

Curious fact: One well-run agile story writing workshop can keep your backlog clean and aligned for months! 🗓️ Mike Cohn suggests holding these sessions about once a quarter In my own practice, a single rapid release planning session every three months replaces traditional big room or PI planning, making our workflows more efficient. 📊 https://lnkd.in/eqE34ji5 #Agile #AgileDad #Scrum #ProductManager #ProductOwner #Leadership #GoalSetting #AgileManagement #Productivity #BacklogManagement

11

Scrum and Kanban comprise the core ideas used by the world's most successful Agile organizations. My upcoming Scrum and Kanban classes provide practical techniques to effectively manage workflow and iterative/incremental development. https://lnkd.in/gvs_jBmU

4

3 Comments

I’ve spent 9+ years training Scrum Practitioners. This case resulted in 79% faster recipe development time for a non-tech team. Get the study for FREE! 👇 After their class experience, a food company applied what we uncovered about Professional Scrum not only to their software teams but also to their kitchen staff, transforming recipe creation from 8-11 weeks to a consistent 2 weeks. Inside the case study, you'll find: ↳ How they doubled revenue and team size ↳ How they transformed recipe development ↳ How they achieved 614% increase in product releases Perfect if you want to: ↳ Eliminate wasted time costing customers and revenue ↳ End the anxiety of "Will this product launch on time?" ↳ Optimize agility to capitalize on market opportunities Check it out 👉 https://lnkd.in/eNq-45UX

15

7 Comments

Frameworks like Scrum and Kanban are powerful, but only when humans apply them as an improvement tool and start working better together. Had a great time on the Scrum.org Community Podcast sharing how Professional Scrum with Kanban can improve handling unplanned work, reduce stress, and boost customer satisfaction.

29

4 Comments

Poster #2 Systems Thinking Thinking My earlier post about about the tenets of systems thinking. This one is about some aspect of how to think in terms of systems thinking. Systems thinking is perhaps the biggest missing concept in the Agile Manifesto. Instead of "Individuals and interactions over processes and tools" is should have been something like "As systems thinking we value individuals and interactions and the processes and tools that support them to be better." It's not one over the other - even when you value both. The reality, this set up people not appreciating systems / processes. Feel free to distribute this poster.

5

2 Comments

✅ Playwright Learning Update! Today I ran into an interesting issue while practicing Playwright. I was testing Google’s page title and saw this error: ❗ Error: expect(page).toHaveTitle() failed – Expected: /Google/ but Received: "" The reason? I forgot to use await before the page actions. 🔧Correct Code: await page.goto("https://www.google.com/"); console.log(await page.title()); await expect(page).toHaveTitle(/Google/); 🎯 Key Learning In Playwright, most functions are async, and forgetting await can lead to: 1. Empty values 2. Timeout errors 3. “Test ended” errors 4. Assertions failing 👉 Putting a habit of using await for every Playwright step makes automation stable and predictable. Every day is a new learning step in the SDET journey! 🚀 #Playwright #AutomationTesting #SDET #JavaScript #QA #LearningEveryday #CodingJourney

11

Continuing the series of author reading The Innovation PROCESS Book over at my new company page for Global NP Solutions. Check out the new page and follow along with Episode 14 discussing the phases and tools for Scrum Product Development. Remember you can get your copy of The Innovation PROCESS Book at Amazon to follow along and catch up on the YouTube series for Part 1 Waterfall Product Development and Chapters 7 and 8 on Agile New Product Development. https://lnkd.in/gugKR_vC

2

Scrum is for the powerful and privileged. For the powerful who can speak up. And the privileged who can recover from the potential retribution. What if the reason teams don’t model Scrum Values is that the system they work in has taken away their power. And they don’t have the privilege to recover from the retribution for modeling the Scrum Values. Which might include getting sidelined or worse - getting fired. They need their job, their salary and their benefits in a tough job market. In this podcast. Elaine Lin Hering, Patricia Kong and Lindsay Velecina helped me discover a whole another complex adaptive system that might be impacting Scrum adoption. If you are a Scrum trainer, Scrum Coach, a Scrum Master or a leader in a tech organization, I would love for you to listen to it and share your perspective👇🏼

13

10 Comments

Jonathan Patrick , a friend and former colleague of mine posted this earlier today https://lnkd.in/gZXEZ4Ce . It resonated with me enough to consider that maybe the point he makes would make sense as another point on the Agile Manifesto. As a result, it would read as follows: We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan -- Delivering Results over Following Frameworks -- That is, while there is value in the items on the right, we value the items on the left more.

6

2 Comments

This is a great article for teams that are just getting started moving from lengthy business requirements documents to user stories and backlog items, along with teams that have been working this way for a while and find themselves stuck in story template purgatory. Don't get yourself wrapped up in imaginary templates, frameworks or rules when creating your backlog items, because there are no rules. If you have a coach that is forcing a template on you and your teams as 'the one true way', my advice is to get a new coach. From the article: 'What’s important is that every backlog item, no matter the format, clearly communicates: the intended value, who benefits, what is being done, any non-obvious constraints, and how you’ll confirm it’s done.' That's it. If you and your team can understand those things, you will generally be in good shape. #productdevelopment #userstories https://lnkd.in/eDP6wxqi

3