Post on 21-Aug-2015
transcript
Business Agility
Zeev BraudeBusiness DevelopmentZeev.braude@igniteso.com
Executive Prespective
• How do you know your R&D needs to go Agile• Business agility 101
Going Agile - Outbound
• You want to be fast to market• You have limited visibility to market needs• You need to quickly respond to customers feedback• Time to market is key…competition is a step behind
Going Agile - Inbound
• R&D isn’t working on the most important features for the business
• Key feature development estimations are beyond what the business can handle
• Release priorities are dictated by R&D design consideration
Going Agile - Performance
• Repeatedly missing product release dates• Release frequency is slower than required by market
conditions• Product quality is not adequate
Going Agile - Now
• If you acknowledge 2 out of 3 symptoms in your company – Go agile immediately
Business Agility 101
• Four key principles– Business Model– Innovation– Organizational structure– Efficiency
Business Model
• Company’s priorities are derived by customers priorities– Listen to customers and work with those who are open for a
dialog– Know your customers individually
• Constantly focus on activities that creates an ROI with customers
• Technology serves the business and not vise versa• Release dates and quality are always before scope
Organizational Structure
• Flatten Hierarchy• Build real cross functional teams. Business and product
development working together creating a collaboration approach
• Empowering autonomy to teams and people increases increases accountability
Innovation
• Continuous innovation– Iterative and trial and error approaches create innovation
thinking – Immediate market feedback brings insight and drives out-of-
the-box solutions
• Teams innovation– The smallest unit is a team. Team members work together,
increase the chances for innovation– Everyone on the team has the information. Everyone can
express their opinion– Autonomy to make decisions. Just go ahead and do it
Efficiency
• Work on the most important features first. Reduce waist of unneeded features
• Lean processes, fast decision making. Keep it simple• Just enough operation. Agreements, documentation,
designs, etc. Focus on business model and maximizing ROI