This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
The role is not called product administrator, feature broker, product backlogmanager, user story writer, or project manager—even though that’s sometimes how it is interpreted. I regard a (digital) product as an asset that creates value for a group of users and for the business. Word is the product. Pl atform Owner.
This sequential, waterfall-based approach used to work when there was little change and innovation, when product managers could correctly predict what the users needed and describe the detailed product functionality upfront. But it is less suited to create complex digital products. The Brave New Agile World.
Here we dive deep into the third key consideration when embarking on a digital transformation: organisation. In our latest podcast, Clarasys’ own Ben Lover, Helen Morgan and Moray Busch explore what organisations must focus on during a digital transformation and the four-stage model of change to enable success.
This sequential, waterfall-based approach used to work when there was little change and innovation, when product managers could correctly predict what the users needed and describe the detailed product functionality upfront. But it is less suited to create complex digital products. The Brave New Agile World.
Developing a successful digital product requires more than technical knowledge. If, however, you feel overwhelmed by the team’s questions, then coach the team to help people see the bigger picture and involve the team in product backlogmanagement and user story creation. Help the Team See the Bigger Picture.
The 4 core Agile values are: Individuals and interactions over processes and tools Functioning end product over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan While some practitioners might give off a different impression, there’s nothing “woo” about Agile.
We organize all of the trending information in your field so you don't have to. Join 57,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content