KienDN

2014-Oct-16

Offshore Tips Sharing - Software Project -

daongockien.vn@gmail.com

Agenda

2

Meeting effectively

REQ analysis deeply

Handle project issue correctly

Avoid trouble, delivery smoothly

• This sharing focuses on basic tips. There are already many tips available in your project, but not yet applied strictly. But in my view, quality will getting much better if we could follow even basic tips. • The case study here is mainly some apps of our team. But it might not exclude others.

1.1 Meeting effectively

3

Prepare meeting agenda, meeting contents in advance.

Make sure you understand and clear what you want to ask

customer?

Use image/graph whenever possible.

1.2 Meeting effectively

4

Avoid using ambiguous words like "this/ that/ it/”. Always

indicate and link to source information clearly.

Conduct meeting minute and transfer for confirmation and follow-up action.

Should spend more time and effort. (because meeting is an

important interface of your work if not the most.)

1.3 Example

5

App1 (Oct-14): Don’t prepare meeting agenda and send on time.

App2 (Oct-15): Don’t clear what to ask about APK installer.

2.1 REQ analysis deeply

6

Clear by asking yourself 5W1H about each REQ item.

The most weakness is usually the comprehensive of background/purpose of REQ item.

Should aware that Customer is just a member of project like us.

Willing to accept change, raise your idea if it helps

product better.

2.2 Example

7

App3 USB content encryption.

App4 “DCIM” -> HTML content.

3.1 Handle project issue correctly

8

Judge the seriousness of issue. If serious, report immediately. Don’t let it become big trouble.

Don’t workaround without confirmation.

Remember to make detail report: “Issue is yours, other could not

understand without enough context information.”

3.2 Example

9

Device setup issue Asking issue without device name, ROM version, log info.

App5 Using Android MediaPlayer or OEM MediaPlayer or …

App6 Using dummy code due to OEM API issue.

4.1 Avoid trouble, delivery smoothly

10

Even simplest output product requires instruction.

Instruction should be step by step and exactly like copy/paste. Avoid writing style which describes flexible method.

Attach all required libraries/apps/test data with exact version neccessary to run the product.

Keep in mind that even customer are technical-friendly, they don’t have time to play ”game challenge” to run your output.

4.2 Example

11

App7 No attached necessary libs/apps.

No guide for pre-setup of some libraries.

Discussion

12