For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Logo
DeveloperAcademyCommunityStatus
  • Getting Started
    • Welcome to Moveworks
    • Roadmap & Release Notes
    • Moveworks Best Practices
      • Launching Moveworks
      • Building on Moveworks
        • Ideal Moveworks Team
        • Designing an AI-first Service Desk
        • Developer Instances
        • Development Lifecycle
        • Hiring Developers
        • Identifying Automation Opportunities
        • Launching New Capabilties
        • Scoping with Mockups
        • Project Managing
      • Driving Adoption
    • Labs
    • Professional Services
    • Support
  • AI Assistant
    • AI Assistant Overview
    • Capabilities
    • Web Experiences
    • Analytics & Performance
  • Enterprise Search
    • Overview
    • Agentic RAG Overview
    • Content Ingestion Platform
    • Profile Boosting
    • Retrieval
    • Permissions Platform
    • Built-in Content Connectors
    • Build your own Content Connectors
    • Configure Search
    • Configure Enterprise Search
    • Vetted Content
    • Writing AI-Ready KB Articles
    • Document Chunking and Snippetization Overview
  • Productivity Boost
    • Overview
    • Configure Productivity Boost
    • Quick GPT
    • Calendar Management
    • Brief Me
DeveloperAcademyCommunityStatus
On this page
  • Development Lifecycle
  • Step 1: Understand the use case
  • Step 2: Identify risks
  • Step 3: Build the use case
  • Step 4: Test the use case
  • Step 5: Launch the use case
Getting StartedMoveworks Best PracticesBuilding on Moveworks

Development Lifecycle

||View as Markdown|
Was this page helpful?
Edit this page
Previous

Hiring Developers

Next
Built with

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.

Step 1: 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 to create a mock-up.
  2. Ensure that mock-up follows all our mocking best practices.

Step 2: 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 for help.

Step 3: 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 with a weekly stand-up if you need help with this process.

If you ever get stuck, feel free to ask our community

Step 4: 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 5: 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 to make sure everything is working.