Jul 11, 2014

​​Modified condition/decision coverage for critical software testing

Câu hỏi: Này, với những phần mềm siêu quan trọng đòi hỏi chất lượng cao thì phải test thế nào?

MC/DC là gì?
"Modified condition/decision coverage" (MC/DC) là một cách test như thế. Phương pháp này được sử dụng để test phần mềm điều khiển cất cánh và hạ cánh của máy bay.

MC/DC được áp dụng ở đâu?
MC/DC được dùng 2 tiêu chuẩn
DO-178B DO-178B, Software Considerations in Airborne Systems and Equipment Certification
DO-178C, Software Considerations in Airborne Systems and Equipment Certification
MC/DC cũng được sử dụng bởi NASA.

MC/DC yêu cầu tất cả tất cả các loại test sau
  1.     Each entry and exit point is invoked
  2.     Each decision tries every possible outcome
  3.     Each condition in a decision takes on every possible outcome
  4.     Each condition in a decision is shown to independently affect the outcome of the decision.

Câu hỏi: Bọn em làm website cho bên Chăn ga gối đệm thì có cần áp dụng MC/DC không ạ?
Trả lời: Không em ạ.


--
Best Regards,
Nguyen Hung Vu [aka: NVH] (in Vietnamese: Nguyễn Vũ Hưng, グェン ヒュン ウー, 阮武興)
vuhung16plus{remove}@gmail.dot.com , YIM: vuhung16 , Skype: vuhung16plus, twitter: vuhung, MSN: vuhung16.
vuhung's facebook  Nguyễn Vũ Hưng's blog on Free and Open Source, Blog tiếng Nhật, Vietnamese LibreOffice, Mozilla & Firefox tiếng Việt

Disclaimer: When posted to social networking groups include, but not limited to Linux Users' Groups, Free and Open Sources forums, mailing lists, the above is my personal opinion and is *not* the opinion of my employer(s), associations and/or groups I join.

Jul 6, 2014

How to run an effective meeting

​​Để chạy một cuộc họp hiệu quả, cần làm gì?

- Có mục đích rõ ràng
- và được chi tiết hóa hơn bằng agenda
- Tập trung vào agenda, không đi lệch chủ đề chính
- Càng ngắn càng tốt. Thời gian cho một meeting nên không vượt quá 25 phút.
(- Chỉ định người take note)

Tham khảo bài dưới đây:

There are good meetings and there are bad meetings. Bad meetings drone on forever, you never seem to get to the point, and you leave wondering why you were even present. Effective ones leave you energized and feeling that you've really accomplished something.

So what makes a meeting effective?

Effective meetings really boil down to three things:

    They achieve the meeting's objective.
    They take up a minimum amount of time.
    They leave participants feeling that a sensible process has been followed.

If you structure your meeting planning, preparation, execution, and follow up around these three basic criteria, the result will be an effective meeting.

1. The Meeting's Objective

An effective meeting serves a useful purpose. This means that in it, you achieve a desired outcome. For a meeting to meet this outcome, or objective, you have to be clear about what it is.

Too often, people call a meeting to discuss something without really considering what a good outcome would be.

  1.     Do you want a decision?
  2.     Do you want to generate ideas?
  3.     Are you getting status reports?
  4.     Are you communicating something?
  5.     Are you making plans?

Any of these, and a myriad of others, is an example of a meeting objective. Before you do any meeting planning, you need to focus your objective.

To help you determine what your meeting objective is, complete this sentence:

At the close of the meeting, I want the group to ...

With the end result clearly defined, you can then plan the contents of the meeting, and determine who needs to be present.

2. Use Time Wisely

Time is a precious resource, and no one wants their time wasted. With the amount of time we all spend in meetings, you owe it to yourself and your team to streamline the meeting as much as possible. What's more, time wasted in a meeting is time wasted for everybody attending. For example, if a critical person is 15 minutes late in an eight person meeting, that person has cost the organization two hours of lost activity.

Starting with your meeting objective, everything that happens in the meeting itself should further that objective. If it doesn't, it's superfluous and should not be included.

To ensure you cover only what needs to be covered and you stick to relevant activities, you need to create an agenda. The agenda is what you will refer to in order to keep the meeting running on target and on time.

To prepare an agenda, consider the following factors:

  1.     Priorities – what absolutely must be covered?
  2.     Results – what do need to accomplish at the meeting?
  3.     Participants – who needs to attend the meeting for it to be successful?
  4.     Sequence – in what order will you cover the topics?
  5.     Timing – how much time will spend on each topic?
  6.     Date and Time – when will the meeting take place?
  7.     Place – where will the meeting take place?

With an idea of what needs to be covered and for how long, you can then look at the information that should be prepared beforehand. What do the participants need to know in order to make the most of the meeting time? And, what role are they expected to perform in the meeting, so that they can do the right preparation?

If it's a meeting to solve a problem, ask the participants to come prepared with a viable solution. If you are discussing an ongoing project, have each participant summarize his or her progress to date and circulate the reports amongst members.

Assigning a particular topic of discussion to various people is another great way to increase involvement and interest. On the agenda, indicate who will lead the discussion or presentation of each item.

Use your agenda as your time guide. When you notice that time is running out for a particular item, consider hurrying the discussion, pushing to a decision, deferring discussion until another time, or assigning it for discussion by a subcommittee.

An important aspect of running effective meetings is insisting that everyone respects the time allotted. Start the meeting on time, do not spend time recapping for latecomers, and, when you can, finish on time. Whatever can be done outside the meeting time should be. This includes circulating reports for people to read beforehand, and assigning smaller group meetings to discuss issues relevant to only certain people.

Download our free agenda template here, and use this as a starting point for creating your own agenda.

3. Satisfying Participants that a Sensible Process Has Been Followed

Once you have an agenda prepared, you need to circulate it to the participants and get their feedback and input. Running a meeting is not a dictatorial role: You have to be participative right from the start.

Perhaps there is something important that a team member has to add. Maybe you have allotted too much, or too little, time for a particular item. There may even be some points you've included that have been settled already and can be taken off the list for discussion.

Whatever the reason, it is important you get feedback from the meeting participants about your proposed agenda.

Once in the meeting, to ensure maximum satisfaction for everyone, there are several things you should keep in mind:

    If certain people are dominating the conversation, make a point of asking others for their ideas.
    At the end of each agenda item, quickly summarize what was said, and ask people to confirm that that's a fair summary. Then make notes regarding follow-up.
    Note items that require further discussion.
    Watch body language and make adjustments as necessary. Maybe you need a break, or you need to stop someone from speaking too much.
    Ensure the meeting stays on topic.
    List all tasks that are generated at the meeting. Make a note of who is assigned to do what, and by when.
    At the close of the meeting, quickly summarize next steps and inform everyone that you will be sending out a meeting summary.

After the meeting is over, take some time to debrief, and determine what went well and what could have been done better. Evaluate the meeting's effectiveness based on how well you met the objective. This will help you continue to improve your process of running effective meetings.

You may even want to get the participants' feedback as well. Depending on the time frame, this debriefing can be done within the meeting itself or afterward.

Finally, prepare the meeting summary. This will be forwarded to all participants and other stakeholders. It is a record of what was accomplished and who is responsible for what as the team moves forward. This is a very crucial part of effective meetings that often gets overlooked. You need a written record of what transpired, along with a list of actions that named individuals have agreed to perform. Make sure someone is assigned to take notes during the meeting if you think you will be too busy to do so yourself.
Key Points:

Running an effective meeting is more than sending out a notice that your team is to meet at a particular time and place. Effective meetings need structure and order. Without these elements they can go on forever and not accomplish a thing.

With a solid objective in mind, a tight agenda, and a commitment to involving the meeting participants in the planning, preparation, and execution of the meeting, you are well on your way to chairing great meetings.

Given the frustration most people feel when their time is wasted, gaining a reputation for running efficient and successful meetings is good for you and your career.

Tham khảo:
http://www.mindtools.com/CommSkll/RunningMeetings.htm
http://www.forbes.com/sites/dailymuse/2013/09/17/the-21-unwritten-rules-of-meetings/​​



--
Best Regards,
Nguyen Hung Vu [aka: NVH] (in Vietnamese: Nguyễn Vũ Hưng, グェン ヒュン ウー, 阮武興)
vuhung16plus{remove}@gmail.dot.com , YIM: vuhung16 , Skype: vuhung16plus, twitter: vuhung, MSN: vuhung16.
vuhung's facebook  Nguyễn Vũ Hưng's blog on Free and Open Source, Blog tiếng Nhật, Vietnamese LibreOffice, Mozilla & Firefox tiếng Việt

Disclaimer: When posted to social networking groups include, but not limited to Linux Users' Groups, Free and Open Sources forums, mailing lists, the above is my personal opinion and is *not* the opinion of my employer(s), associations and/or groups I join.

​​​Project Executive Summary Reports

Câu hỏi:
Viết gì trong báo cáo (giữa kỳ) dự án, vừa ngắn gọn, vừa nêu được các điểm chính (nhất) tới quản lý cấp cao hơn và những người liên quan.

1. Major risks:
- Rủi ro chính của dự án
- Hạn chế tới 3 hay 5 rủi ro nổi cộm nhất

2. Major issues:
- Vấn đề (đang gặp phải) chính của dự án
- Hạn chế tới 3 hay 5 vấn đề cần giải quyết luôn và ngay

3. Progress summary
- Dự án hoàn thành bao nhiêu % tiến độ tổng thể, theo từng sprint, so với kế hoạch
- Công việc nào chậm, nhanh?

4. Project health indicator:
- Diễn tả bằng 3 màu giống như đèn giao thông (xanh, vàng đỏ).

The traffic light colors highlight for project management:

(Red): the project needs management attention,
(Yellow): is at risk of not hitting its targets,
(Green): is progressing according to plan.

5. Budget forecast:
- Tiền tiêu được bao nhiêu rồi?
- Với số tiền ấy đã hoàn thành bao nhiêu % khối lượng công việc rồi? (EVM)
- Để làm nốt thì cần chi bao nhiêu? Bao giờ phải chi


--
Best Regards,
Nguyen Hung Vu [aka: NVH] (in Vietnamese: Nguyễn Vũ Hưng, グェン ヒュン ウー, 阮武興)
vuhung16plus{remove}@gmail.dot.com , YIM: vuhung16 , Skype: vuhung16plus, twitter: vuhung, MSN: vuhung16.
vuhung's facebook  Nguyễn Vũ Hưng's blog on Free and Open Source, Blog tiếng Nhật, Vietnamese LibreOffice, Mozilla & Firefox tiếng Việt

Disclaimer: When posted to social networking groups include, but not limited to Linux Users' Groups, Free and Open Sources forums, mailing lists, the above is my personal opinion and is *not* the opinion of my employer(s), associations and/or groups I join.