Devops for Growth

Interestingly enough, the article written by Steve Blank does intend to draw a clear line dividing those two approaches. The two main arguments supporting this division, according to Blank, are based on the different features of a startup compared to those of a established company, and they are as follows:

- A startup has a pressure and a sense of urgency (so that they don't run out of resources before validating their innovative proposal, which would imply to close that emerging company and to fire the team) much more noticeable than in the case of an established company that wants to explore an innovative project. This makes innovation processes (and, among them, learning from customers) to be different in one case or the other.

- Customer Development was conceived by Blank thinking about startups launched by "visionaries" that startup with a solid idea about a product and search for customers and markets wanting it. Thus, they have that pressure and sense of urgency to find those customer segments (and reaching product/market fit) before running out of resources. Design Thinking (at least according to Blank) is not devised thinking of an entrepreneur's vision of the product he/she wants to build. Instead, it focuses on "searching for problems/needs" using a process that attempts to reduce risk through learning and iterative refinement using prototypes.

Malika Mir, DSI du groupe agroalimentaire Bel, revient sur la transformation de la DSI grâce au design thinking, sur ses enjeux data et green tech.

Continuous delivery demands the use of hypotheses, not requirements, to deliver what customers want. Developers embrace continuous experimentation and adaption.

Treating APIs as products is a concept that is rapidly gaining adopting across the API space, and organizations are increasingly seeing the benefits of using product management principles when developing APIs. This approach involves applying the same level attention and planning to your API portfolio, as you would to any of the other software products your team is delivering.

This was also a popular concept at the recent Nordic API Austin API Summit. The conference featured a number of talks that touched on this topic, including: Why Productization Is the Key to Unlocking API Value from Pete Clare of Vanick Digital, and Embedding API-as-a-Product Culture from Rahul Dighe of Paypal.

The 18F Methods are a guide to putting human-centered design into practice.

Playbacks are meetings that are used to keep stakeholders, clients, and teams in sync. Playbacks occur at different points during a project:

Persona and scenario definition

Minimum viable product (MVP) definition, including the user experience

Development delivery of completed stories

The value of playbacks

Playbacks help ensure that the team is aligned on the personas that will use the service and the scenarios to include to satisfy the MVP.
Playbacks in practice

Effective playbacks incorporate these practices:

Being concise

Scheduling enough time to listen to stakeholder feedback

Focusing on the value of the scenario rather than the technical implementation details

MVP definition

When playbacks are part of the MVP definition, the goal is to align the entire team around the scenarios that are part of the MVP and the user interface to achieve those goals.

Dans cette courte vidéo, on vous livre un super outil de design thinking qui vous permettra d'observer une situation donnée.