To meet schedules, deliver valuable products, and exceed your stakeholder’s expectations, you need the ability to flex scope and offer an actual minimum marketable product. You need to know how to break down your work to be forced by technology or business processes to deliver anything more than the minimum.
If you’ve used agile, you’ve heard of creating the minimum viable product (MVP). MVP has been thrown around so much and for so long that the term’s original power is lost.
A few years ago, I became acquainted with a lady running a charity for a child who was having medical bills pile up. She was holding a charity bazaar to raise money for the child's family.
Can anyone be a Product Owner (PO)? What’s the best position in the company to fill that role? With Scrum you have one and only one Product Owner for a given product...
User stories are business needs, not requirements in the traditional sense. They are oriented toward the user and a business need. The big difference between a user story and other types of requirements is that a story describes a business need, not the system’s functionality.
Do you ever influence or coach people? How? Do you use a gut feel approach or do you have coaching patterns that you use? I have several coaching patterns that I step through when trying to influence people.
Ah, the Daily Scrum, so often misused as an instrument of status (see https://youtu.be/i7_RPceEIYE for a discussion). Often the way the Daily Scrum is conducted lends itself to a report of status.