Embed Size (px)
DESCRIPTION
To be more successful in a development network, find better ways to produce and integrate artifacts that contribute to the goals of development. To make better hour-by-hour and day-by-day decisions, embrace a system perspective when writing more lines of code or producing more pages of documentation. Move beyond a perspective that is limited by reductionism or procrustean solutions. Encourage deliberative subtraction (deciding what not to develop) from the perspective of the system. Embrace new product development as more than a collection of diverse artifacts. Embrace new product development as more than a job characterized by obvious answers where choices are framed as ‘OR’ selections. Embrace “AND” selections that meet the needs of the present and anticipate development in the future. Facilitate set-based design over point-based design. Strive to be proficient problem solvers that also invest in future capabilities. Incorporate artifacts that contribute to the goals and minimize distractions. First rate individual contributors have the ability to hold a requisite variety of ideas about artifacts in their mind at the same time and still retain the ability to function. Refactoring F Scott Fitzgerald from The Crack-Up, April 1936 (3) With that capability, you can improve your Development Experience [DX] which is another artifact that should be made skillfully.
Citation preview
Mark A Hart, NPDP
Facts about Artifacts:Reimagining How New Product Development Artifacts Impact What We Should Be Doing Today
Outline• Categorize artifacts
• Clarify memes
• Offer concept to determine what individual contributors should be doing on a particular day
arte factum: skill + to make
Artifact
Two types of artifacts in new product development
• External deliverables (includes the product)
• Internal deliverablesIncludes design documents, data models, workflow diagrams, test matrices and plans, setup scripts,…) from Stack Exchange
• Items used to produce deliverables
• Secondary items
• Items for the future (such as training)
• Incomplete, unfinished, or abandoned items
• Intangibles (such as strategies, tactics, and culture)
Hour-to-hour and day-to-day questions• What should I be doing
now?
• Why?
• Should a specific artifact be created?
• How much effort should be expended creating it?
Resolving priorities• Requests exceed network
development capacity
• Predictions about the future
• Unknown items
• Interruptions and emergence
• Flow interruptions
• Dependencies
Perspectives influence perceptions of value
Coders value code
Copywriters value persuasive messages
Designers value prototypes
Others value spreadsheets
“Working software over comprehensive documentation”
Agile Manifesto, 2001
Factors the drive perception• Status quo
• Loudest voice
• HiPPO (Highest Paid Person’s Option)
• Curated information
• Estimates and milestones
• Feedback from experiments
Indicators of sub-optimization• Efforts expended to improve
a component do not improve the system performance
• The success-limiting component does not receive the appropriate resources
• Rewards are silo-centric instead of the system-centric
Producing artifacts quickly is not the main objective of new product development
The capability to produce artifacts quickly contributes to achieving the main objectives of new product development
Preparing individuals to make better choices• Improve proficiency
• Possess a variety of responses
• Requisite variety
• Consider immediate AND current AND future timelines
• Improve interplay
• Develop implicit coordination
Preparing the development network to make better choices
Invest to develop Einheit
Invest to improve Schwerpunkt
Preparing the development network to make better choices
Continuously self-correcting, network-informed
schwerpunkt
The phrase “working software over comprehensive documentation” should not be oversimplified to “no documentation.”
The “improvement kata (a pattern of systematic, scientific routine of thinking and actions)” should not be oversimplified to “no waste”
To be more successful in a development network, find better ways to produce and integrate artifacts that contribute to the goals of development
To make better hour-by-hour and day-by-day decisions:
• Embrace a system perspective when writing more lines of code
• Move beyond perspectives limited by reductionism and procrustean solutions
• Encourage deliberative subtraction
• Embrace NPD as more than a collection of diverse artifacts
• Move beyond the “OR” choices
• Embrace “AND” options
• Anticipate achieving future success
• Facilitate set-based design
• Invest in future capabilities
• Develop artifacts the contribute to goals and minimize distractions
To make better hour-by-hour and day-by-day decisions:
First rate individual contributors have the ability to hold a requisite variety of ideas about artifacts in their head at the same time and still retain the ability to function
Refactoring F Scott Fitzgerald from The Crack-Up, April 1936
Development Experience [DX] is an artifact that should be made skillfully
Mark A Hart, NPDP April 2014
Developing Winners: Assimilating the Insights Encapsulated in Boyd's OODA Loop
www.Developing-Winners.com
Mark A Hart
www.OpLaunch.com
Twitter: @OpLaunch
Facts about Artifacts:Reimagining How New Product Development Artifacts Impact What We Should Be Doing Today
10 April 2014
