Exercises Software Review Technical Advisors Technical Review 
The Product Guy
APRIL 9, 2019
In my company, we review a living document with our management chain on a quarterly basis to align business direction for the short-term (immediate one to two quarters) to the long-term (two to five years). No formal stakeholder review as this is meant to be the first version that will undergo many iterations and refinements.
bpma ProductHub
MARCH 20, 2017
Let’s review a couple of scenarios: Scenario one – company has an existing product portfolio. The sales team is providing feedback and advising that the product is missing features preventing them from penetrating market A, and if only they had those features, they could be very successful selling. Just remember to focus.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
The Product Coalition
FEBRUARY 5, 2021
Then she decided to acquire technical skills in web development to get closer to the product development process. She had many ideas about how to improve marketing tactics but did not have the technical skills to either make the necessary changes on the web or create better solutions using technology.
The Product Coalition
MAY 11, 2022
Finally, “ Building for Business: Product Management in Enterprise Software ” is a truly B2B-focused Product Management book, written by Blair Reeves (Salesforce) and Benjamin Gaines (Adobe) for “all the ones who aren’t part of the Silicon Valley startup bread”. But why is working in enterprise software now different?
Userpilot
JULY 9, 2021
Continuous Discovery Habits by Teresa Torres teaches you how to set up a continuous discovery system within your organization with actionable exercises. Product Mastery by Geoff Watts teaches you how to be a successful product owner within agile software development practices with the use of case studies. out of 5 stars. Where to buy?
The Product Coalition
MARCH 11, 2020
Finally, the term Development Team seems to limit the role to technical people, for example, software engineers. Ignoring technical debt: The Development Team is not demanding adequate capacity to tackle technical debt and bugs during the Sprint. Read more on technical debt and Scrum.) Team leads?
The Product Coalition
JANUARY 5, 2021
A good starting point would be working with the “Manifesto of Agile Software Development,” particularly ensuring that stakeholders understand that adapting to change over following a plan is paramount for the organization’s future success. A new feature is overdue and has been drastically underestimated due to unexpected technical debt.
Expert insights. Personalized for you.
148 
Let's personalize your content