It’s very easy to become hierarchical and turn into a “bank” when software company is growing fast. Is there a way to avoid that? How to keep the focus on value creation? What about Value departments, not Functional departments? This presentation shares ideas what we can learn from Scrum and apply in organizational design. It shares hypothesis how a company could look like when everybody is focused on value creation.
When companies transition to Agile, it is not too difficult to find new roles for member of the current software development teams. Finding a place for middle management in the new organization is not so easy and some people even advocates to get rid of them. In this blog post, Em Campbell-Pretty brings her own middle management perspective to this discussion.
Software is everywhere today, and countless software products and projects die a slow death without ever making any impact. Today’s planning and roadmap techniques expect the world to stand still while we deliver, and set products and projects up for failure from the very start. Even when they have good strategic plans, many organizations fail to communicate them and align everyone involved in delivery.
One of the technical practices of Agile software development is to support cross-functional teams where members perform multiple activities like requirements, coding and testing. In their book “Being Agile”, Leslie Ekas and Scott Will discusses the difficulties of creating a whole team.
The product owner is one of the three roles of the Scrum framework for Agile project management. The product owner is responsible for defining and prioritizing the backlog and to convey the product vision to the Scrum team. Some people have compared this role to the traditional product manager position, but the context is different.In her blog post, Ellen Gottesdiener shares nine things that every product manager should know about being an Agile product owner.
Adopting new software development approaches like Agile and Scrum is always a challenge. There is a natural tendency for part of an organization to resist changing and some prejudices exist against Agile, mainly due to a lack of knowledge. This article discusses these misconceptions and provides some tips on how to overcome these prejudices to get Agile adoption on track in your organization.
Improvement is one of the core principle of the Agile Manifesto that states “At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly”. Retrospectives are a powerful technique to achieve this goal in Scrum and in this blog post, Jonathan Berger proposes seven practices to facilitate retrospectives.
Scrum Expert Copyright © 2009-2024 Martinig & Associates