Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
Daniliants Ventures
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Daniliants Ventures Rules & Regulations
Page
Discussion
English
Read
Edit
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
== Rules & Regulations == These Rules & Regulations are designed to regulate work processes and relationships within the team and to improve them. By reading these Rules & Regulations, you agree to comply with them. == Workflow == * All team members are committed to following an improved workflow and the rules governing it. * The workflow is scrum-based. Everything is broken down into sprints. Each sprint lasts one week. * If the project has strict deadlines, we estimate all tasks approximately and put them together into a sprint. If the client tries to add more tasks to the sprint, we prioritize them and move other tasks to the next sprint. * Task completion times must be tracked in Proofhub. If someone forgets to track time, it should be manually added at the end of the month. * Time tracking on client projects should be monitored by the PM or other responsible person during the month. Team members should receive weekly reminders to track their time and check for missed hours at the end of the month. * In Tech-Design, new projects should first be discussed in a brainstorming session with the developer, designer, and PM to define key points and approve the main features of the future product. == Projects == * After signing the contract and before starting work, the client must fill out an onboarding questionnaire. This should include their goals, available resources, past actions, acceptable practices, and limitations. * All introductory project information must be documented and transparent. A profile for each project must be created in Notion or Google Sites (one tool must be selected). The profile link should be attached to the project channel. * Project communication must occur in the project channel. If discussions take place in DMs, key information (e.g. documents, ideas, budgets) must be duplicated in the channel. * Communication with the client must be conducted via corporate email. * All project materials and documents must be uploaded to the client profile on SuperOkay. This ensures transparency and easy access for both the team and the client. The SuperOkay link must be pinned in the project channel. * The customer's objectives should always be the top priority when implementing a project. * Weekly performance and goal alignment must be monitored. If necessary, the responsible person brainstorms with the team to adjust strategy. * Every six months, a client satisfaction survey must be conducted to evaluate the cooperation and adjust working methods or strategy accordingly. * After a contract ends, the client must be offboarded using the [https://docs.google.com/spreadsheets/d/1-8WZ-b55lEcJX3jMazh-tOpS0a_0ibQQe4eqjB21T7c/edit?usp=sharing offboarding checklist]. The checklist and a feedback survey must also be sent to the client. == Tasks == * All tasks are created in Proofhub. * Tasks can be managed using the Proofhub Slack extension. * Anyone performing a task must immediately start time tracking for it and remember to stop the timer afterward. If this is forgotten, the time must be added manually at the end of the month. * All large builds must be broken down into subtasks. * Important and recurring tasks must be labeled. * Each task must be prioritized. Prioritization is handled by Artem during planning. * If you are creating a task list yourself, be sure to set it up using a 3-stage kanban flow. * At the end of each month, all team members must ensure their tasks are moved to the appropriate step. * A task is considered complete only after it is accepted by the customer. == Operational Tasks == * All project-related or internal documents must be created in, or immediately added to, the Daniliants Ventures Google account. * Documents related to a specific project must be stored in the appropriate Google Drive folder for easy access and organization. * To stay informed about document updates, team members are encouraged to install the Google Drive extension for Slack. * Registrations on websites or services required for work must be done using the Daniliants Ventures Google account or email. * All passwords must be stored securely in a password manager. Slack should not be used to share passwords due to security concerns. * If a password is changed by a team member, it must be updated in the password manager and all relevant team members must be informed. == Meetings == === Daily === * Every day at the same time (currently at 10:10) we hold a rally (daily standup) with all team members. * During the rally, each team member reports: * What they did yesterday * What they plan to do today * What didn't work out and why * If you cannot attend the daily standup, you must inform Johanna via Direct Message. * There was also a suggestion for daily meetings in the form of a 15-minute coffee break to socialize, rest, and recharge. [https://docs.google.com/spreadsheets/d/1Adnp--A-QbO69xt3a91UP--qLYnjMhtWtsrJxDJ-ZD8/edit?usp=sharing Suggestion Link] === Weekly === * Weekly planning meetings are mandatory. During these meetings: * We review all tasks and determine their status. * Discuss the positives and negatives of the previous week. * Determine the champion of the week. * Review any changes in projects and new tasks. === Monthly === * Brainstorming sessions are held to identify problems and discuss options for solving them. We also explore ideas for improving processes and deliverables on projects. * A channel may be created for ongoing ideas to improve our processes, work environment, activities, etc. * One-on-one sessions with team members to identify team problems, frustrations, moods, etc. == Team == === Team Members Are Forbidden To: === * Insult and disrespect each other. * Discriminate based on gender, age, race, religion, and other characteristics. * Work for competitors in parallel. === The Principles to Be Followed by All Team Members: === * Respect each team member's opinions, ideas, and cultural sensitivities. * Work together as partners, not competitors. * Prioritize the team's success over individual interests. * Support and inspire each other. * Resolve conflicts in a peaceful and constructive manner. * Be honest and transparent about your actions and decisions. * If you're dissatisfied with your work or have personal issues, communicate with Artem, HR, or PM. We will do our best to help and make you comfortable again. It's important not to keep problems to yourself, as we cannot solve them if we're unaware. * If you encounter issues in your work or make a mistake, inform Artem or PM. No one will penalize you. The key is to identify and address the issue promptly, learn from it, and prevent it from recurring in the future. === New Team Members === * It is mandatory to onboard new team members according to the [https://docs.google.com/spreadsheets/d/1tqvY4CkLxatxgn8_-Q-ptpEcLI4eI_w7okrh2bpUYZM/edit?usp=sharing checklist]. * New team members must familiarize themselves with these Rules & Regulations. * A one-on-one session should be held with the new team member after the first month to assess their progress. * After the probationary period, a one-on-one session should be held to determine their further growth. * During the first six months, the new team member's performance should be monitored according to key metrics. * Periodic sessions should be held during the first six months to check how the new team member is integrating with the team and how they're doing overall.
Summary:
Please note that all contributions to Daniliants Ventures may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
Daniliants Ventures:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)