The annoying, but honest, answer given to most questions about product ownership. If someone provides that answer and stops there, they’re trying to avoid the question.
If they say that and then continue to explain what happens in various situations, they are admitting the impact of context in product development.
It’s context that prevents best practices from being a real thing. There is no practice that works equally well in each situation. You have to consider your environment, your organization, and your product whenever you decide how you you’re going to approach a particular challenge.
This week I’m sharing a couple of resources for dealing with context and explanations on how to approach three different types of situations you’ll often run into in an IT setting.
Read these resources to get a better understanding of why, more often than not, it really does depend.
Why context matters to product people
Your context drives and influences the practices you use. Here’s why you need to understand context to pick the appropriate product practices.
How to consider context when learning from others
Experience is the best teacher. This post shares five steps to consider context when learning from others experience.
How to Implement COTS in an Agile Fashion
Most organizations do not develop 100 percent of the software that they use, nor should they. A vast majority of the jobs they have to do can be satisfied with readily available Commercial Off the Shelf (COTS) software, or its more modern successor, Software as a Service (SaaS). Here are some ways I’ve found to implement COTS and SaaS in an agile fashion.
Three Ways Agility Helps Business Intelligence
The ability to learn and adjust on an ongoing basis, a key benefit of agility, is extremely helpful for business intelligence and data warehouse initiatives.
If you’ve worked in business intelligence for any length of time, then you’ve experienced the ongoing discovery that happens with business intelligence efforts. Once you get a feel for the kind of information that business intelligence can provide, you come up with all kinds of things you can use the data for that you didn’t think of initially.
How can you experience the benefits of agility with business intelligence? This post takes a look at three ways you can use agility to improve the effectiveness of your business intelligence efforts.
How IT Service Teams Can Be Agile
Agile software development approaches were originally created to address software development challenges. As enterprises that don’t sell software as their main product adopt agile, they find the need to adjust their approach in order to apply agile across their IT organization and entire enterprise.
In the above posts, I explored how you can use agile to work with COTS and business intelligence, both of which are common activities that are different from (but not entirely unlike) software development activities frequently found in IT organizations. In this post, I’d like to explore how you can perform another activity, IT service, in an agile fashion.