---
title: Development Lifecycle
excerpt: ''
deprecated: false
hidden: false
metadata:
  title: ''
  description: ''
  robots: index
next:
  description: ''
---
# Development Lifecycle

Once you've picked an experience to build, you'll want to take the following steps to maximize your chance of launching that experience to production.

<Steps>
  <Step title="Understand the use case">
    A clear understanding of business requirements is essential before you start building. Creating mock-ups make the requirements explicit.
    
    1. Use our [purple chat builder](https://developer.moveworks.com/creator-studio/developer-tools/purple-chat) to create a mock-up.
    2. Ensure that mock-up follows all our [mocking best practices](/docs/mocking-up-requirements).
  </Step>
  <Step title="Identify risks">
    **System API Risk:** Make sure the target business system has APIs that will allow your Assistant to integrate with it. For example, if your system only has purchase order APIs, you can't build an invoicing use case using APIs.
    
    There's generally workarounds (email interception, RPA tools, etc.). You can get in touch with [our professional services team](https://www.moveworks.com/us/en/professional-services) for help.
  </Step>
  <Step title="Build the use case">
    Once your use case is de-risked, just keep the project on track. **Always have a milestone with a target date and report on it regularly.** You can [follow our delivery schedule templates](/docs/project-managing) with a weekly stand-up if you need help with this process.
    
    If you ever get stuck, feel free to [ask our community](https://community.moveworks.com/)
  </Step>
  <Step title="Test the use case">
    1. Get access to any test / UAT business systems
    2. Identify testers and tell them how to use your use case
    3. Launch the use case to testers
    4. After a few days, get sign-off on the experience
  </Step>
  <Step title="Launch the use case">
    1. Get access to any production business systems
    2. Send launch communications to all relevant users about this use case
    3. Check back after day 1 & day 7 in [analytics](/docs/copilot-insights) to make sure everything is working.
  </Step>
</Steps>