Given we now have a significant amount of content within the Handbook, we want to produce a "Getting Started Guide" to be used during the on-boarding process.

This will be a file with links to various training and content to reduce the overwhelm of first starting capstone. This will be applicable for both juniors and seniors.

As discussed in the T1 end of tri planning meeting

Address feedback from #5 around 'the' article usages in the charter doc

Looks good, @tancnle - can we just add a "the" to make it "The Thoth Tech charter"? :)
Originally posted by @kats8 in #5 (comment)

@tancnle and if we can just adjust this to "The Thoth Tech charter" also?
Originally posted by @kats8 in #5 (comment)

T2 2022 questionnaire: JUNIORS please fill this out to assist with ensuring you are placed appropriately next year and get a chance to take on roles and growth opportunities of interest. This is your chance to have your say.

Test strategy: has your team completed yours? This is an important part of the Quality Assurance process and should exist before you start coding. Reminder, a sample Test Strategy template is in the handbook. If you have particular testing resources and skills, there will be opportunities to express interest this week to help out your fellow Thoth-Tech company members.

Remember to book into your calendars, next Monday 9th of May, Daniel from Midnyte City is presenting an guest session all around Experience working in Industry. It’s at 12-1pm so you can dial in over lunchtime. Daniel has real world delivery lead experience, so this is a great opportunity to gain valuable insight into the real world and enhance your capstone leadership learnings.

Onboarding form improvements:

• skill confidence (1-5) eg. programming, troubleshooting, documentation, project collaboration etc

• do you want to work towards leadership?

• Product Lead + Area lead merged

• Addition of more area leads

• QA team

• Documentation team part of Internal Systems

• Delivery lead training in week 0

• Implement recommendations from T1 Delivery leads

Tuesday:

3pm: Dreambig Prototype 1
4:30pm: SK Extensions meeting
4:45pm: SK Operations meeting

Wednesday:

7pm: Documentation meeting

Thursday:

1pm: OT Voice Verification
5pm: Dreambig Prototype Meeting 2

Unsure:

Front-end migration
Deployment
Internal Systems
Applications (sundays?)
Modules
Jupyter notebook

• All company meeting
• What should be done
• Delivery!!!!!
• REACH OUT FOR HELP

product fixes

Just some add on highlights to the products:

• SplashKit is not limited to object-oriented coding, it aims for beginners starting from programming paradigms like structural and procedural programming approaches.
• OnTrack, it aims to facilitate portfolio base assessment by providing an opportunity for students to get feedback as a formative assessment reflecting their learning and to formulate a deeper understanding of the concepts students are learning time to time to showcase in their final portfolio. One of the key features of it is to provide interactions in tailored learning experience.

Adding these clarified goals and initiatives of the products will help in shaping the strategic development directions for the Company.

content adding on top of updates

• include QA processes and timeline
• See the following Software Requirements Specification (SRS) reference
• plan and design of implementation (the medium level of description, not the low level coding details) based your listed goals/expected deliverables

Good:

Besides, for the product development, all of the company members in this task have nicely conveyed

1. Define your product's purpose
2. Describe what you're building, for their responsible product/project.
3. Detail the requirements.
4. Deliver it for approval.

Document collapse component and mermaid feature on mardown guide.

As a follow-up from the following review comments:

• Originally posted by @talzid in #57 (comment)
• Originally posted by @talzid in #57 (comment)

Why

Teams would like to gain more insights into what they can get done in a given amount of time. Good estimation helps leadership to optimize for efficiency and impact.

What

Develop some guidelines on how to estimate using story points in the Trello guide.

How

• Propose a set of guidelines in the Trello guide
• Seek feedback from teams
• Run a Q&A or workshop meeting if needed

Resources

• Common mistakes when using story points
• Atlasssian - Estimation

Congrats on the excellent feedback about Task 2.1
Starting to think about your retrospective (6.1) / task 5.1
Watch the D/HD workshop video (benefitial for everyone)
Fill in the learning survey
Seniors who want to mentor – reach out
Juniors who would like to work towards leadership next trimester (EOI for attending the leadership conference being organised)
Showcase for D/HD students being organised at the end of the week - presenting to MDs with trello board, plans, testing & data strategies (fill in the templates) - great place for feedback
By now trello boards should planned out, upskilling should already be happening
Comfortable in github, creating pull requests
Review the QA doc – there will be a session on this during the week
Transition away from word docs – everything moving towards thoth tech from this week onward.
Ensure you have cloned your repos from the Thoth Tech organisation - not doubtfirelms

why

Now that we have the documentation repo - which is project based - I feel like there is no need to have the projects in the handbook. I think each product should have a place and description as they are a part of the company, but should only be high-level and stakeholder based information

what

Remove projects from handbook to ensure clarity between repository purpose.

how

None of the folders have any content so could easily be removed.

Based on the 6.3 Feedback, incorporate:

• tips for professional communication
• Guide for process around late comers
• Tips for fearless feedback

Focus is on development?
Task 6.x this week
Documentation now going into the documentation repo (https://github.com/thoth-tech/documentation)

• If the file is relevant companywide and for more than one trimester, it goes in the handbook repo
• If the file is relevant to a product or project, it goes in the documentation repo

Start thinking about off-boarding and trimester transition