Sprint Progress

Mar 1, 2024

Christian Fuss

Here you will find all information about our development sprints in chronologically reverse order, i.e. newest first. If you want to find out whats coming next, check out our backlog.

Sprint 9 (CW 18, Apr 29-May 03)

Goal: A fully functional example including documentation

• Improve DX of monorepo in VS Code (so it is easier to convince collaborators)
• integrate nlp.js
• update documentation site
• connect WhatsApp Cloud

Sprint 8 (CW 17, Apr 22-26)

Goal: Finalize integration layer und core middlewares

• Abstract logger
• Console logger and configuration
• Error handling
• Event emitting

WhatsApp cloud server and nlp.js middleware still need to be finalized.

Sprint 7 (CW 16, Apr 15-19)

Goal: Simple chatbot example according to framework architecture is implemented

• Simple console chatbot and some sample middlewares are implemented

Sprint 6 (CW 15, Apr 08-12)

Goal: Align interfaces in architecture with common representatives of NLP frameworks (nlp.js, wit.ai, Rasa)

• Define interfaces for context data and handover points for the flow through the message response
• Initial implementation for middleware dispatcher (similar to Koa web framework architecture)
• Continue Whats-App-Cloud connector

Sprint 5 (CW 14, Apr 01-05)

Goal: Publish WhatsApp-Cloud-Connector, that is standalone usable in a node.js runtime

• Migration to node.js (80% done)
  • General migration of runtime dependencies
  • Few dependencies (crypto, …): Some more work required, will be done in course of example integration
• Meeting with Tim Schupp from Little World about their PTF application with a chatbot agent library and possibilities to integrate that with ChatAlly.

Sprint 4 (CW 13, Mar 25-29)

Vacation

Sprint 3 (CW 12, Mar 18-22)

Goal: Identify usability gaps and derive requirements with Namibian youths.

• We tested the existing chat prototype for DIY instructions with some communities in Namibia: Compared to the website, the complexity of instructions in chat mode becomes more apparent. That also means that the length of messages should be even shorter and the support for streamed media (audio and video) is even more important.
• We interviewed some NUST (Namibian University of Science and Technology) students about their interest in a toolbox for chatbots and got vastly positive feedback.

Sprint 2 (CW 11, Mar 11-15)

Goal: Identify benefits and challenges with respect to middleware candidates.

Rationale: We want to identify the best middleware candidate for our chatbot platform. This sprint will be dedicated to evaluating the benefits and challenges of different middleware candidates.

As a left-over from last sprint, we will also publish our current state of the Deno-based WhatsApp connector (not as an NPM package, though).

• Publish WhatsApp Deno connector
  • Create package whatsapp-deno-connector in mono repo
  • Clean-up code
• Middleware candidates
  • Analyze Jovo
  • Compare with other solutions

Sprint 1 (CW 10, Mar 04-08)

Goal: Publish a first alpha version of the WhatsApp connector.

Rationale: As a baseline of the CI/CD process and for all future integrations, we want to extract the existing WhatsApp connector from our chatbot prototype and publish it as an NPM package within a CI/CD pipeline.

Besides that first step, setting up the website for the documentation process and all the other infrastructure is important in this sprint.

• Add a blog section to website
• Create blog posts
  • Milestones
  • Progress
  • Backlog

Tags:

• Planning
• Continuous Updates

« Backlog