Acorn Analytics
The Acorn proven process wheel: discover, design, develop, deploy

The Acorn Proven Process

Software development projects, especially data-intensive ones like machine learning, are highly uncertain: requirements and priorities change as more information becomes available. For this reason the field has adopted Agile software development methodologies as an industry best practice.

Discover, Design, Develop, Deploy

Discover and Design are the Blueprint.

  1. Discover

    Part of the Blueprint

    Identify stakeholders, investigate issues, frame problems, understand use cases, gather requirements, interview business leaders and tactical and technical experts, research benchmarks and best practices.

  2. Design

    Part of the Blueprint

    Perform analysis of data, create wireframes and prototypes of possible solutions, and design mockups or interaction flows, and propose plans to get from the current state to the desired future state.

  3. Develop

    Scale the work from the Design phase into more ubiquitous and scalable solutions using realistic real-world components and production-ready systems. This is the fun part where code is written and dreams come to life.

  4. Deploy

    Deploy solutions into production, operationalize, transfer competency to your internal team, and move into maintenance mode with or without the Acorn team. This is when we put your vision out into the world!

How engagements start

New clients can start with Advisory, Execution or a Blueprint. If you are ready to commit, begin directly with Advisory or Execution. If you are not ready yet, begin with a Blueprint.

Advisory

We run this process at the strategy level while guiding others on execution.

Execution

We own the whole process end to end.

Blueprint

Our initial discovery engagement, for clients not yet ready to commit to more. It covers the Discover and Design phases. We interview your leaders and technical experts, then deliver:

  • Current State Synthesis
  • Strategic Roadmap, with findings and recommendations on the business and technology risks and opportunities in your current state, the desired future state, and how to move from one to the other
  • Investment Estimates
  • A custom execution proposal

A Blueprint with a proof of concept adds an interactive prototype built on synthetic or mock data.

After a Blueprint, we propose a menu of options. It may include an Advisory or Execution engagement, or other offers with concrete outcomes.

Pencil in an intro call

Roles for our Agile Data Team

Acorn works with clients in iterative cycles, each referred to as a “Sprint” or “Sprint Cycle.” Part of our onboarding is to establish who will play what role in the partnership's success. Typical roles include:

  • Product Owner. Our clients typically assign a “Product Owner” to identify and prioritize the work for each Sprint Cycle. The Product Owner specifies high-level requirements and business use cases to the Acorn team, and has at least 30 minutes a week to meet with us, give feedback and unblock the work.
  • Agile Team Lead. Acorn assigns an “Agile Team Lead” to coach the team through the Agile process and remove impediments. Above all a facilitator, the Agile Team Lead is the continuous point of contact between the business stakeholders represented by the Product Owner and the Acorn team doing the work. As the needs of the client and project change and call for different expertise, the Agile Team Lead makes those transitions seamless and keeps continuity for the lifetime of the partnership.
  • Agile Team members. The entire team working on the engagement is the “Agile Team”, including the Product Owner, the Agile Team Lead and other contributors. Whether or not our client nominates individuals to join, Acorn provides the balance of people who make up the bulk of the Agile Team.
The sprint cycle, and how the client team, product owner, team lead and agile team members relate

Frequently asked questions

What if the full plan feels too big?

Say so. We split it into smaller, separate projects that pay back faster, and you choose where to start.

Should we wait on an IT migration, such as moving from Microsoft to Google?

If you have not started a major migration, it often helps to wait a few weeks. We map and protect your existing data first, so history is not lost, and then you can migrate. The worst is when we start work while things are happening behind the scenes, and suddenly key pieces of information are mysteriously disappearing.

Will the work we do now be wasted if we later build our own client management system?

No. The early projects are the first pieces of that larger system and fold into it.

Let's talk.

Tell us what you are launching, fixing or trying to decide.

Pencil in an intro call