Apr 1, 2013

Is Design dead?

​Câu hỏi:

Design (thiết kế) (phần mềm, hệ thống) đã "chết" chưa? Nó thực sự còn cần thiết hay không?


Kết luận:
- Không, design không chết
- Nhưng những kỹ năng cần cho design thay đổi
- Cần kinh nghiệm
- Cần proactive, nhìn được pattern, phán đoán được thay đổi long-term và short-term
- Cần chuẩn và convention

Context:
- Thay đổi từ mô hình cổ điển (waterfall sang XP/Agile/Scum)
- Áp dụng cho mô hình phát triển phần mềm (và hệ thống nói ICT chung)

cf.
"Is Design Dead"? http://martinfowler.com/articles/designDead.html#SoIsDesignDead
Technical Debt: http://martinfowler.com/bliki/TechnicalDebt.html

--
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.

WBS, Schedule and Network Diagram

Các điểm chính về WBS, Schedule và Network Diagram:

Work Breakdown Structure:
http://en.wikipedia.org/wiki/Work_breakdown_structure
Là sự chia nhỏ công việc, gói công việc của dự án thành các thành phần nhỏ hơn (theo sản phẩm giao nộp)

Network Diagram (Project network):
http://en.wikipedia.org/wiki/Project_network
Là đồ thị mô tả sự phụ thuộc giữa các công việc của dự án (xem WBS)

Schedule:
http://en.wikipedia.org/wiki/Schedule_%28project_management%29
Có thể hiểu đơn giản, Schedule là "Network Diagram" theo yếu tố thời gian: start date và end date.

Tham khảo thêm:
Work Breakdown Structure vs. Network Diagram:
http://blogs.pmi.org/blog/voices_on_project_management/2011/02/wbs-and-schedule-network-diagr.html

WBS pitfalls:
http://www.projectsmart.co.uk/work-breakdown-structure-purpose-process-pitfalls.html


--
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.

SÀI GÒN PHÊ DUYỆT CHƯƠNG TRÌNH PHÁT TRIỂN ỨNG DỤNG CÔNG NGHỆ THÔNG TIN TRÊN CÔNG NGHỆ NGUỒN MỞ GIAI ĐOẠN 2012 - 2015 http://thuvienphapluat.vn/archive/Quyet-dinh-5867-QD-UBND-nam-2012-phe-duyet-Chuong-trinh-phat-trien-ung-dung-vb151984.aspx


Mar 31, 2013

Agile Sprint Cycles vs. Rolling Wave Planning

Agile Sprint Cycles vs. Rolling Wave Planning (cổ điển)

http://www.brighthubpm.com/agile/37999-the-30-day-agile-sprint-cycle/
"If you had to deliver functionality to the client every 30-days, would
you and your team, walk or run towards the deadline? Thirty days isn't
much to deliver functionality, SCRUM suggests sprinting."

Ý tưởng: Release ngắn thôi, theo từng giai đoạn gọi là "srpint"

http://www.brighthubpm.com/project-planning/48953-basics-of-rolling-wave-planning/
"The requirements were vague. I couldn't possible plan for the entire
project. However, at least some degree of planning was required to get
the project started. So, I used the Rolling Wave Planning technique to
plan as far as the requirements were clear enough."

Ý tưởng: Có bao nhiêu (thông tin) thì plan bấy nhiêu. Đừng và không
thể/khó đoán được những công việc giai đoạn quá xa, còn quá ít thông tin.

--
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.
http://www.facebook.com/nguyenvuhung
Nguyễn Vũ Hưng's blog on Free and Open Source:
http://nguyenvuhungvietnam.wordpress.com/
Học tiếng Nhật: http://hoc-tiengnhat.blogspot.com/
Vietnamese LibreOffice: http://libo-vi.blogspot.com/
Mozilla & Firefox tiếng Việt: http://mozilla-vi.blogspot.com/

Disclaimer: When posted to social networking groups include, but not limited 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.

Type of Organization Structures

Functional Organization Structure: In functional organization structure, the organization is grouped into various departments; e.g. sales department, marketing department and finance department.


Matrix Organization Structure:
Matrix organization structure is a hybrid of the functional organization structure and the projectized organization structure. This structure takes the benefits of both worlds.


Projectized Organization Structure:
Projectized organization takes every job as a project. Here, the project manager has all authority to complete the project successfully.


Composite Organization Structure:
In Composite Organization Structure, organizations may use any combination of the above given type of structures.


Pre-bureaucratic Structure: 
Pre-bureaucratic Structure type of organization does not have the standard procedures and policies. This type of structure is used by small scale organization with few employees who handle the simple tasks. It has a central command with one decision maker at the top position. This type is not mentioned in PMBOK.


Bureaucratic Structure: 
Organization which uses the bureaucratic structure, usually are larger and has some sort of standardization. This type is not mentioned in PMBOK.


Post-Bureaucratic Structure: 
Post-Bureaucratic Organizations are fully developed and has all kind of standards and procedures with a central command consisting of several board members where decision making is done by democratic procedure. This type is not mentioned in PMBOK.


Divisional Structure: 
In Divisional Structure, organization is divided into various divisions and each division itself will be capable of doing the task on its own. It means that each division will have its own resources required to function properly. This type is not mentioned in PMBOK.

 

Cf. http://pmstudycircle.com/2012/08/type-of-organization-structure/#ixzz2P8PA0CdZ

http://nguyen-vuhung-pmp.blogspot.com/2012/08/pmp-tight-matrix.html






--   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.  http://www.facebook.com/nguyenvuhung  Nguyễn Vũ Hưng's blog on Free and Open Source:  http://nguyenvuhungvietnam.wordpress.com/  Học tiếng Nhật: http://hoc-tiengnhat.blogspot.com/  Vietnamese LibreOffice: http://libo-vi.blogspot.com/  Mozilla & Firefox tiếng Việt: http://mozilla-vi.blogspot.com/    Disclaimer: When posted to social networking groups include, but not limited 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.