Reorganizing Product Teams | - Rich Mironov's Product Bytes
We could simply declare ourselves to be a product company, and assign everyone to newly unfamiliar roles. Big bang. Before announcing any organizational change, though, it’s worth guessing at likely objections, pushback, skill differences, and cultural norms. Your situation may be different, but at services firms I see every process tuned to say “yes” whenever a client wants to pay for something.  Sales brings in a prospect, we size the work, and we jump to deliver a uniquely bespoke solution for that one company. Company metrics are about project-based margin and keeping our development organization busily billing for their time.  That’s diametrically opposed to how product companies think – product companies want repeatable, low-friction installations with as little handholding as possible, in order to sell hundreds/thousands/millions of users a single codeline at prices well below what customers would spend to build it themselves.
product  organization  development  business  models 
29 days ago
The Triumph Of Customer Capitalism
"At the heart of customer capitalism today is the idea that the world has changed. Power in the marketplace has shifted from the firm to the customer. Abruptly, frighteningly, and to the great surprise of command-and-control managements of big firms, the customer is now the boss."
value  stakeholders  agile  business 
4 weeks ago
Themes vs Epics vs Features vs User Stories
"Even if you do find yourself in that situation, experience has shown me that you don’t need four separate backlogs with four separate levels of hierarchy to coordinate the efforts of over 90 teams split across multiple locations. A two level hierarchy and some good old fashion communication can work wonders."
requirements  agile 
4 weeks ago
« earlier      
3d ackoff adwords agile agile_for_managers ai analysis analytics appreciativeinquiry architecture arduino article automation backup bash beyondmethod bim blogging books burnout business c# cables change cloud cms coaching code collaboration communication companies complexity conferences consulting content contracts copywriting corruption creativity css culture cv dart data decisionmaking deployment design developeruser development devops diagrams dialogue documentation drawing education email entrepreneurship estimation examples exercises experiential exploratory facilitation feedback filetype:pdf finance flow fonts forms free freelance game gamedev games gdpr git goals google graphic hdr history howto html ifc improvement innovation inspiration iphone javascript journalistik jquery kanban kids knowledge latex leadership lean learning legacy lego lighting linux mac mainframe maintenance management marketing math measurement media:document meetings metrics motivation online opensource openspace optimization organization organizations osx patterns performance philosophy photography php planning prioritization problemsolving procrastination product productivity productmanagement productowner programming projects pshychology psychology python quality quotes rails ready recruiting reference remote requirements research retrospectives ruby safe safety sales satir scale scaling science scrum selforganization seo service services shell shortcuts simulation software splitting splitting_user_stories standards startup startups statistics stories storymapping strategy systems systemsthinking tdd teaching teams technicaldebt testing text themes thinking time tips tool tools toread toyota training trust tutorial tutorials typography ui unity unity3d unix usability use-of-self userstories ux value video visualization wallpapers web web2.0 windows wordpress workshops writing

Copy this bookmark: