Unlocking Value for your products

42% of start-up failures are attributed to one reason - "They developed something that is not a need". Over the last few decades many organizations have spent billions in digital transformation. However, few years back Forrester estimated that $900 billion worth of spend in digital transformation will miss the mark. Be it startups or organizations that transform digitally, they both find their digital journey tough. In the user centric world, digital transformations are still plagued with traditional mindset. If we see from hindsight, these organizations could never ascertain value of their solution upfront from an end user angle. We need a value foresight to deal with this existential challenge and there is no crystal ball to predict it. So, the questions CIOs ask is – Can Value be defined and how can it be engineered into the solution? If value can be engineered in, can every team member be an innovator? Anything that is definable can be qualified, improved upon and dealt upfront.

This talk will help define value and provide a set of aspects on how successful products in the industry have engineered value upfront. Talk will also draw experiences of digital transformation initiatives where the research from successful products have been implemented – CODEX, a project management platform that transforms the governance of engagements for customers & OnTheGo, mobile intranet in the hands of employees for their daily needs


In a nutshell, this talk will drive home the point of value engineering every aspect of the product for best in class user experience and adoption.

 
 

Outline/Structure of the Talk

This session will be in the format of a talk.

First part will be helping the audience to understand a simple, easy to implement definition of value. There would be examples from gurus of innovation like Henry Ford, Akio Morita and Steve and helping participants understand the definition with industry examples

Second part will be to introduce the two pillars of successful products - Need and Value.

Third part will be helping participants ways of engineering value into products

this talk typically takes about 75 to 90 minutes. Given that the max time is just 45 minutes, will have to cut short the first two sections to 20 minutes while the methods of engineering value would be the last 20 minutes, dedicating 5 minutes for Q&A

Learning Outcome

  • Understand the importance of Qualifying Value measurably
  • Multiple ways of removing barriers
  • Ideas for enabling superior user experience
  • Transforming the entire engineering team to be an innovation hub

Target Audience

CIOs, IT heads, Project managers, delivery managers, Product Owner, Scrum Master, team member

Prerequisites for Attendees

An attitude to learn would be the only pre-requisite

schedule Submitted 10 months ago

Public Feedback

comment Suggest improvements to the Speaker

  • Liked Penelope Barr
    keyboard_arrow_down

    Penelope Barr - From Dogma to Pragma - helping 500 squads on the road to agile maturity

    Penelope Barr
    Penelope Barr
    Founder & CEO
    BeautifulAgile
    schedule 10 months ago
    Sold Out!
    45 Mins
    Talk
    Intermediate

    What a joy to be in a key leadership position in one of the largest-ever corporate experiments - the transition to new ways of working. I'm accountable for establishing and operating the Centre of Expertise, New Ways of Delivering - how we uplift culture, delivery & technical capability. We're doing this through consulting, coaching, educating, facilitating & mentoring.

    The scope - 5000 people, 500 squads, 6 regions.

    The process - Think systemically, optimise locally.

    The result - it's a process...

  • Liked Smitha
    keyboard_arrow_down

    Smitha / Chetan Vasuki - Agile in software services : An oxymoron?

    20 Mins
    Experience Report
    Intermediate

    Which are those top 10 that come to our minds when it comes to Agile? Google, Amazon, Apple, Thoughtworks and of course many others to name. But how many of those companies are software services?

    Lets take the new age digital platforms in India, rapidly delivering and adapting to change - flipkart, OYO, ekart, swigy ,OLA, paytm, zomato - what's common with them when it comes to developing their platforms? They have their own shops with their own teams working together to deliver their solutions. They own, decide and claim their value chain to customer. They may have outsourced some of their pieces to other service providers. But the core value chain is developed and owned by the primary owner. So, why aren't there many service companies coming out as thought leaders in Agile practices, but rather end up as followers? How many of them are really doing agile?

    According to the State of Software Development Report, 2018, close to 80% of the participants used agile methods ( 58% being SCRUM). However, ask them what their challenges are? They are still capacity management,Priorotising development, time management, unrealistic expectations, estimation, lack of clearly defined deliverables, lack of well defined success criteria.. They survey had 15% from IT services and 39% from Software /technology areas. These problems existed years back as well. Should we be worried?

    So, is agile really helping or are slipping into these common terms used nowadays like faux-agile, dark scrum etc?

    Agile practices drive teams to embrace agility and provide value incrementally. However to do this, there is an ecosystem that has to be brought, nurtured and sustained.

    But too many variables galore in a software services sector: From variable nature of customers who want to control everything, dependencies between multiple vendors, fast changing technologies and their wide range, customer maturity, skill matches needed for the technology range and many more.

    Teams, in spate of these variables, quite often can tend to slip into into a ceremonial agile ; leaving them confused about how agile benefits in reality. We call it as the “Miragile syndrome”( an agile mirage ).

    This talk discusses and examines cases on how teams can be affected by syndrome and what are cures in place.