Kippa, Reminders for Microsoft Teams. Our app is now 3.6 months young and the story of his birth is related in this series of posts.
We started off building our app for Microsoft Teams in the early stages of the pandemic lockdown. Early in the process, we decided to pay forward our experiences working in Canada’s tech industry. We designed and wrote a course on how to launch a Startup.
The first post in this series introduced the course, Take Control: Seven Steps to Independence©. You can download it here for free, no registration required.
Post #2 in the series, explained the idea behind Kippa, our reminder app for Microsoft Teams. It demonstrated how we applied the course’s theory to produce Klippas Technologies inc’s, Kippa – the Microsoft Teams’s Personal Assistant.
We delved into Kippa’s origins, and its market. We concluded that post with the six questions we asked to validate the idea using the theory covered in the course’s Step 2, Validate. We answered the questions in the post, and followed that with the way in which we arrived at the results in Post #3 in this series, which dealt with Exercises 4, 5 and 6 of the course. We ended that post promising to continue in the next one with Exercise 7 and 8.
Post #4 in the series did just that, and showed how we had constructed the business plan for Kippa – Reminders for Microsoft Teams.
Post #5 in the series introduced you to the theory of designing a solution’s components, functions and artifacts. We showed you the process we used to design Klippas Technologies inc’s Kippa, your Microsoft Teams Personal Assistant.
This post continues the story by exploring more on the way we applied the Take Control to the design of Kippa’s artifacts. An artifact, according to Webster’s Dictionary, is: any object made by human beings, especially with a view to subsequent use. In this case, the parts of your solution you have to design and build which are used in the delivery of your service or within the construction or use of your product.
In the case of Kippa, our Reminder app for Microsoft Teams, his artifacts are, as just one example, his cartoons, like this one:
There are the Graphic User Interface controls, dialogs, windows and tabs. You can see more of these by referring to Kippa’s Software Product Description.
You have already seen this mind map of the process we used to do all this, but it’s worth repeating it here for your convenience:
Kippa, reminders for Microsoft Teams’ component design.
It’s a process, right? You simply repeat the steps to the right of the blue box labelled, Touchpoint Type. You ask the 5 questions to enable you to determine which kind of touchpoint his is, and then focus on the steps to the right of the box. Kippa’s components are just the kinds of things a reminder app for Microsoft teams would need:
GUI screens and widgets, controls to allow you to set your preferences like which kinds of reminders you want the Microsoft Team members to receive – cards (with cartoons), or just plain text messages. Whether you want reminders to be snoozed every time they are issued, or the time formats you want your reminders to follow: 24 hour clocks or 12 hour forms.
Recent Comments