Scrum thought leader, author and trainer Mike Vizdos discusses what he is doing with collaborative co-working environments … the ongoing struggle to bring Agile to large enterprises … and a bunch of related side projects spanning Lean Startup, job boards and publishing. [27:00]
Choosing the right process to manage your projects is a decision that should be based on need, not rhetoric. What works in one organization might not be suitable for another, or it may require modification. Agile is no different. What is important is the success of the project, not how well it adheres to a specific approach.
The role of Product Owner, at once strategic and tactical, is misunderstood by many companies transitioning to Scrum or Agile approaches. The product owner serves as both organizational change agent and bridge between the business side and the project team. Here’s a basic primer on this indispensable role.
Does your project team really act like a team or is it just a collection of individuals who focus on their tasks and rarely support each other? Jan Beaver, author of The Agile Team Handbook, discusses why and how we can better leverage the power of teams. [25:30]
Laszlo Szalvay and Charlie Rudd of SolutionsIQ discuss the state of scaling Agile and Scrum principles on the enterprise level, including the challenges of intergrating the work of multiple teams on larger programs and portfolios. [30:48]
If practicing Agile transforms how we work, non-violent communication is a framework to transform how we interact with each other in the workplace. Juan Banda, scrum master, coach and retired martial artist, shares his thoughts on non-violent communication, and how its principles have influenced his work with scrum teams. [22:18]
Just as all projects are different, their main information radiator, the humble task board, should reflect their different characters and requirements. Here is an anatomical tour of my current team’s task board in the hope that it may spark ideas for other Agile teams.
Scrum has been at the forefront of a revolution in how software is developed and deployed. Who is using it? How? And why? In this exclusive 48-page report from ProjectsAtWork, Scrum Alliance and ProjectManagement.com, 500 professionals share their answers.
Just as agile teams strive to continuously improve, they should also continuously seek opportunities to reduce wasteful activities. A good start is creating visual representations of a team’s total wasted time over the course of several sprints as well as its time invested in improvements.
Are your project retrospectives getting a bit stale, diluting their effectiveness? Keeping retrospectives fresh for your team requires diligence on your part, but the rewards from continuous improvement are worth it. Here are three fun, simple retrospective techniques that can help get your teams re-engaged.