Andrew Stellman affirms that having great teams with a collaborative mindset takes more than great people, visionary leaders and good organizers, providing insights into what needs to be added.
David Hussman advises on story mapping: pick an idea, choose someone that might be helped by that idea, build a story map as a way to explore that person’s experience, and start the customer journey.
Christian Legnitto offers insight in some of the tools and processes used by Facebook for pushing new updates to their mobile apps.
Steve Rogalsky explains the basics of user story mapping based on real case studies, showing pictures depicting projects’ progress and how that influenced iterative development and process visualization.
John Hughes discusses automated testing techniques that can catch more code defects, with war stories from the likes of Ericsson, Volvo Cars, and Basho Technologies.
Dario Nardi shares key insights on how the brain works and suggestions on tapping the power of individuals’ talents in order to be put together at work.
Seb Rose explores the choices a team needs to make when considering which Agile test practices to adopt, urging teams to practice, practice, practice until they are happy with the way they code.
Michael Sahota discusses top 10 Agile gotchas: when release is ready, sprint meetings take too long, no retrospectives, people aren’t working together, getting new stories, stand-ups are boring, etc.
Jim and Michele McCarthy discuss the Core Protocols that make a common platform for an organization’s culture design.
Ashley Johnson identifies key principles for high performance product development teams, and explore which of these we can and cannot control in virtual teams.
Brendan Marsh and Kristian Lindwall present what they believe an Agile Coach is, give some insight into the daily life of an Agile Coach at Spotify & explain why they believe Coaches help others win.
David Tanzer takes a look at the current status of software development and suggests what a team can do to stay competitive, and what a developer can do so his/her employers still need him over time.