When it comes to guiding the development of a product and ensuring you’re building what the user actually needs, a product owner is the most important hire for the team. There’s just one problem: A good product owner can be really hard to find. The characteristics that make a good product owner are elusive, but here are three qualities you should prioritize in your search.
A high-performing agile team delivers exceptional results time and again, irrespective of the challenges they encounter. While their results may seem magical, lots of effort goes into building such a team, on the part of team members themselves and their leaders. Here are seven common qualities high-performance teams exhibit that you should strive for when building your own agile team.
One of the principles behind the Agile Manifesto is “At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.” Unfortunately, many associate that practice with performing team retrospectives at the end of a sprint, or periodically in kanban. But if you seek to build a high-performing team, there are more improvement activities you should consider adopting.
Scrum works well for collocated teams, but working with distributed teams brings its own different challenges. There should be some controls in order to prevent instability, ambiguity, and tension from turning into chaos. As the ScrumMaster is the servant leader of the team, here are four important initiatives the ScrumMaster can take to guide their teams—the four C’s of managing distributed agile teams.
When many think of modernizing or altering their firm with the goal of staying competitive in the market, thoughts of expensive, cutting-edge concepts that are difficult to implement usually come to mind. But innovation doesn’t have to cost a lot of money. The fact is that pure modernism is focusing on the benefit of the customer, the team, and the business. It does not always have to be overly technical or costly. As with speed, the most economical method to determine if a company is pursuing innovation is to look internally and discover how the workforce is being utilized. Giancarlo Di Vece will explore some of the key innovation questions: How do we determine if team members are appropriately applied and the project evenly distributed? Which tools do we need to get the job done? How does training drive innovation? Are we collaborating in a meaningful and useful way?
Despite thinking that organizations are slow to innovate, innovation actually abounds at many companies. Kodak, DEC, and Xerox did not fail due to lack of new, cutting-edge innovation; they failed because their organizations were tuned to their traditional markets, and a failure to change their business models and organizations led to their eventual disruption. The key to achieving business agility lies in leadership that transforms organizations. Transformational leaders succeed by changing the system, leading with purpose, and steering from the edges. They own their responsibility and boldly lead their organizations into the future. It's time for all of us to undergo personal transformations and start leading for innovation, disruption, and business agility.
Substantial confusion exists about the roles and responsibilities of test management when using an agile software development process. Agile seeks to streamline project management and leadership under the role of a ScrumMaster, but what does this mean for test managers? How do they stay...
So you think you know Scrum? Using the whimsical notion of farm animals and light-hearted visuals, take a refreshing review of the entire Scrum lifecycle as an intuitive set of roles, responsibilities, and handoffs. Particular attention is placed on what the ScrumMaster and product owner are expected to do at each handoff.
In this interview, Selena Delesie, an international leadership and transformation coach and trainer, explains how your team can find the soul of agile, why some agile teams lack creativity, and who on your team should become a leader.
In order to adopt DevOps, organizations need to be able to embrace the openness it requires, encourage experimentation and innovation, and work across departmental silos. You may be ready to encourage collaboration and communication to reap the benefits, but what if your company culture isn't? Here's how you can influence your organizational dynamics to lay the groundwork for DevOps.