Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 18 additions & 5 deletions business/business-playbook-outline.md
Original file line number Diff line number Diff line change
@@ -1,11 +1,24 @@
# BUSINESS PLAYBOOK
---
tags:
- dwarves
- work
title: business-playbook-outline
date: 2023-10-16
description:
authors: []
menu:
toc: false
notice:
type: playbook
---
# BUSINESS PLAYBOOK

Table of Contents

1. Introduction

* Who we are
* The Team
* Who we are
* The Team
* Team chart
* Team members
* Portfolio
Expand All @@ -21,8 +34,8 @@ Table of Contents

5. Process workflows

* Sales Partnership process
* Sales Partnership process
* Commission model/tier
* Payment timeline
* Payment timeline

6. FAQ
15 changes: 14 additions & 1 deletion business/collaboration-guideline.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,16 @@
---
tags:
- dwarves
- work
title: collaboration-guideline
date: 2023-10-16
description:
authors: []
menu:
toc: false
notice:
type: playbook
---
# Collaboration Guideline

Guidelines for project collaboration between DF and Clients.
Expand Down Expand Up @@ -36,7 +49,7 @@ Meeting notes for Sprint planning and Sprint retrospective will be sent within 3

* Design team should at least provide:
- Color palette (all that are used throughout the UI)
- Heading / Font size should be defined by scale
- Heading / Font size should be defined by scale
- Base components (.eg headings, button variants and states,…)
* New design version is expected to be available and reviewed **by development team** before the Sprint started

Expand Down
40 changes: 26 additions & 14 deletions business/df-workflow.md
Original file line number Diff line number Diff line change
@@ -1,20 +1,32 @@
* Monday:
Sprint Planning
---
tags:
- dwarves
- work
title: df-workflow
date: 2023-10-16
description:
authors: []
menu:
toc: false
notice:
type: playbook
---
* Monday:
Sprint Planning
End-of-day (EOD) check-in message

* Tuesday:
EOD check-in message
* Tuesday:
EOD check-in message

* Wednesday:
Sprint review message
EOD check-in message
* Wednesday:
Sprint review message
EOD check-in message

* Thursday:
EOD check-in message
* Thursday:
EOD check-in message
Performance review (Account Manager, Team Lead, Project Owner, every 2 weeks)

* Friday:
Investment time/Tech Radar
Sprint Review
Retrospective

* Friday:
Investment time/Tech Radar
Sprint Review
Retrospective
15 changes: 14 additions & 1 deletion business/fbsc.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,16 @@
---
tags:
- dwarves
- work
title: fbsc
date: 2023-10-16
description:
authors: []
menu:
toc: false
notice:
type: playbook
---
## Budget

We do need to know clients' budgets. This is often uncomfortable for them but their budget helps determines what scope is possible. It saves time. If they don't know their budget, we discuss different options.
Expand All @@ -18,4 +31,4 @@ The probability of this document containing the optimum feature set is extremely

Based on that document, clients expect consultants in the industry to submit an exact timeframe and bid. This contract style sets the client and consultant working against each other right from day one. Instead of focusing on designing the product experience or evaluating what assumptions were wrong, they spend time negotiating about what was meant in a document written a long time ago or focusing on arbitrary deadlines. But it's worse than negotiating; it's retroactively discussing something that no one remembers the same way.

As you might have guessed, we don't do fixed-bid, fixed-feature-set proposals.
As you might have guessed, we don't do fixed-bid, fixed-feature-set proposals.
28 changes: 20 additions & 8 deletions business/how-to-work-with-clients.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,18 @@
---
tags:
- dwarves
- work
title: how-to-work-with-clients
date: 2023-10-16
description:
authors: []
menu:
toc: false
notice:
type: playbook
---
# TRAINING COURSE: HOW TO WORK WITH CLIENT

What skills that an engineer should have in order to work with client effectively?

1. Strong technical skills: includes
Expand All @@ -9,7 +22,7 @@ What skills that an engineer should have in order to work with client effectivel
2. Attention to details

3. Communication skills: good English skills (both written and verbal)
-> require somewhere Intermediate - Upper Intermediate level
-> require somewhere Intermediate - Upper Intermediate level

4. Problem solving and logical thinking

Expand All @@ -19,19 +32,18 @@ What skills that an engineer should have in order to work with client effectivel

7. Project Management

8. Consistency in delivering work result
8. Consistency in delivering work result

What are the issues that our engineers currently facing when working with clients?

1. Verbal and written English
1. Verbal and written English

2. Attention to details: many times not able to deliver clean works

3. Work planning

4. Consistency in delivering work result

5. Teamwork (i.e: Dong Nguyen case when working with Ukraine team, could not synchronize with the rest of the FE team very well, mostly due to not being able to communicate very well)
4. Consistency in delivering work result

6. Lack in EQ
5. Teamwork (i.e: Dong Nguyen case when working with Ukraine team, could not synchronize with the rest of the FE team very well, mostly due to not being able to communicate very well)

6. Lack in EQ
14 changes: 14 additions & 0 deletions business/invoice.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
---
tags:
- dwarves
- work
title: how-to-work-with-clients
date: 2023-10-18
description:
authors: []
menu:
toc: false
notice:
type:
---

14 changes: 14 additions & 0 deletions business/nda.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
---
tags:
- dwarves
- work
title: service-feedbacks
date: 2023-10-18
description:
authors: []
menu:
toc: false
notice:
type:
---

77 changes: 43 additions & 34 deletions business/service-feedbacks.md
Original file line number Diff line number Diff line change
@@ -1,45 +1,54 @@
---
tags:
- dwarves
- work
title: service-feedbacks
date: 2023-10-16
description:
authors: []
menu:
toc: false
notice:
type: playbook
---

# GENERAL QUESTIONS FOR SERVICE FEEDBACKS

1. Engineer performances
1. Engineer performances

a. Communication
- a. Communication

* How did the engineer interact with your team?
* How was the communication between the engineer and your team?
* Was our engineer proactive in communicating with you?
* Did our engineer ask lots of questions?
* On which aspect our engineer should improve to provide better communication?
- How did the engineer interact with your team?
- How was the communication between the engineer and your team?
- Was our engineer proactive in communicating with you?
- Did our engineer ask lots of questions?
- On which aspect our engineer should improve to provide better communication?

b. Work ethic, delivery
- b. Work ethic, delivery

* Have our engineers “coming to work” on time?
* Have you ever had to wait too long to get a response from our engineer?
* Was our engineer able to deliver good work consistently?
* Was our engineer able to deliver clean, good code?
* Was there a lot of bugs that arose from our engineer’s work?
* Were these bugs considered as “rookie mistakes”?
* What can our engineer do in order to provide better code?
* Have our engineers been able to discuss work planning before starting on the coding?
* What should our engineer do to improve the synchronization with other members?
- Have our engineers “coming to work” on time?
- Have you ever had to wait too long to get a response from our engineer?
- Was our engineer able to deliver good work consistently?
- Was our engineer able to deliver clean, good code?
- Was there a lot of bugs that arose from our engineer’s work?
- Were these bugs considered as “rookie mistakes”?
- What can our engineer do in order to provide better code?
- Have our engineers been able to discuss work planning before starting on the coding?
- What should our engineer do to improve the synchronization with other members?

2. Team management
2. Team management

* What are your opinions for the team management?
* Was our Team Lead able to help you co-manage the team efficiently and effectively?
* Was there anytime that you cannot contact our team members in a timely manner? If yes, please specify.
* When you are unhappy with the engineer’s work, who would make you feel comfortable to contact and discuss?
* Was it easy for you to contact our Account Manager?
* Was our Account Manager able to note down your request thoroughly?
* In the end, was our Account Manager able to help you solve the problems?
* What should our Account Manager do in order to improve the collaboration between two parties?
- What are your opinions for the team management?
- Was our Team Lead able to help you co-manage the team efficiently and effectively?
- Was there anytime that you cannot contact our team members in a timely manner? If yes, please specify.
- When you are unhappy with the engineer’s work, who would make you feel comfortable to contact and discuss?
- Was it easy for you to contact our Account Manager?
- Was our Account Manager able to note down your request thoroughly?
- In the end, was our Account Manager able to help you solve the problems?
- What should our Account Manager do in order to improve the collaboration between two parties?

3. Opportunity

* Would Dwarves Foundation be your first choice when it comes to hiring outsources? If not, why?
* What should the Dwarves Foundation do to improve its credibility to you?
* Do you have any further comments for the Dwarves Foundation?





- Would Dwarves Foundation be your first choice when it comes to hiring outsources? If not, why?
- What should the Dwarves Foundation do to improve its credibility to you?
- Do you have any further comments for the Dwarves Foundation?
14 changes: 14 additions & 0 deletions design/IA.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
---
tags:
- dwarves
- work
title: nda
date: 2023-10-18
description:
authors: []
menu:
toc: false
notice:
type:
---

14 changes: 14 additions & 0 deletions design/IX.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
---
tags:
- dwarves
- work
title: IA
date: 2023-10-18
description:
authors: []
menu:
toc: false
notice:
type:
---

Loading