Guideline and description how System Analyst and Tech Writer are working. mostly describe as procedure of how tech writer and system analyst working, it might as a team or individual.

1. System Analyst &
Technical WRITER
SOP
Shinta Yulia P
Lead System Analyst – Techno Infinity
2022

2. Project Management
“Project management is like juggling three balls – time, cost and quality. Program management is like a troupe of
circus performers standing in a circle, each juggling three balls and swapping balls from time to time.” – G. Reiss

3. Project
Management
• Sasaran proyek:
• Scope goals: tujuan
dari proyek?
• Time goals: berapa
lama waktu yang
dibutuhkan untuk
selesai?
• Cost goals: berapa
biaya yang
diperlukan?

4. Stakeholder Project
Stakeholder adalah individu atau
organisasi yang aktif terlibat dalam
proyek, atau siapa saja yang bisa
dipengaruhi oleh hasil
penyelesaian proyek atau eksekusi
proyek
“The strength of the team is each individual member. The strength of each member is the team.” – Phil
Stakeholder
Manager
Project
Client
Tim
Developer
Sponsor
Tim
Management
Project
Comp
etitor

5. Tujuan dan Manfaat
Manajemen Project
• Efisiensi, dalam sisi biaya, sumber daya dan waktu
• Kontrol terhadap proyek lebih baik, sehingga bisa sesuai
dengan ruang lingkup, biaya, waktu dan sumber daya yang
telah ditentukan
• Meningkatkan kualitas dan produktivitas
• Menekan resiko sekecil mungkin
• Koordinasi internal yang lebih baik
• Mengembangkan hubungan dengan customer

6. Project Management Task
1. Menentukan lingkup proyek
2. Mendifinisikan stakeholder, pengambil
keputusan, dan prosedur pengembangan
3. Membangun daftar detail pekerjaan (Work
Breakdown Structures – WBS)
4. Mengestimasi kebutuhan waktu
5. Membangun inisialisasi bagan alir
manajemen proyek
6. Mengidentifikasi kebutuhan sumberdaya
dan anggaran
7. Mengevaluasi kebutuhan proyek
8. Mengidentifikasi dan mengevaluasi resiko
9. Menyiapkan rencana kontigensi
10. Mengidentifikasi ketergantungan
11. Mengidentifikasi dan menelusuri milestones
yang critical
12. Berpartisipasi dalam review tahapan proyek
13. Mengamankan sumberdaya yang
dibutuhkan
14. Mengelola proses pengontrolan perubahan
15. Melaporkan status proyek

7. System Analyst &
Technical Writer

8. Job Description SA
• A System Analyst is a skilled professional that works to enhance
user experience with software programs. They advise employers and
clients on which software program they may need, implement the
software and communicate with users to ensure the programs work
well.
• Design new IT solutions, modify existing systems and
integrate new features, to improve business efficiency and
productivity
• A system analyst is a professional who analyzes, designs (flow, db, interface),
and implements information systems. By doing so, they bridge the gap between
IT and business, thereby improving efficiency.

9. Job Description TW
• A Technical Writer is a professional responsible for creating documentation that clarifies the
product's features and benefits. They work on requirements like content strategy or scoping out new
products to ensure all necessary information has been included for users to understand what
they're reading quickly (S-P-O-K).
• The Technical Writer is responsible for generating innovative ideas for content while working
both independently and collaboratively as part of a team. The position researches products, services,
technology or concepts to be documented and easily understood by a broad audience.
• Some of the duties and responsibilities of a Technical Writer include:
• Determine the clearest and most logical way to present information for greatest reader comprehension.
• Generate innovative ideas for content and workflow solutions.
• Meet with subject-matter experts to ensure specialized topics are appropriately addressed.
• Analyze information required for the development or update of policy, procedure and form documentation.
• Review and/or copyedit content developed by other members of the team.

10. Project Team
• Project Manager
• System Analyst (include DB Eng)
• Technical Writer
• UI/UX
• FE Dev
• BE Dev
• QA

11. Documentation
• BRD/BRS = Business Process
• SRS/SKPL = Requirement System + Technical Document
• SDD/DPPL = Design System (can substitute w/ Figma + ERD)
• UAT Doc = Document Testing -> BAST
• User Manual/Manual Book
• MoM

12. Issue
• Project yang berasal dari proxsis beberapa kali tidak match
antara yang disampaikan dari pihak konsultasn proxsis dengan
kebutuhan real client. Indikasi masalah karena tim techno tidak
dilibatkan dari awal saat koordinasi dan komunikasi dengan
client.
• Saran perbaikan: lakukan perbaikan dari sisi koordinasi antara
proxsis dan techno untuk koordinasi dengan client. Termasuk
penentuan scope dan timeline. Scope dan Timeline sebaiknya
disusun Bersama antara PO (product owner) dan Tim
Developer

13. Project
• GRC East – BRS, SRS, FIGMA, UAT, MANUAL BOOK, MOM
• Jasindo – BRS, SRS, FIGMA, UAT, MANUAL BOOK, MOM
• Kominfo – BRS, SRS, FIGMA, UAT, MANUAL BOOK, MOM
• Rosneft – BRS, SRS, FIGMA, UAT, MANUAL BOOK, MOM
• Puskes – BRS, SRS, FIGMA, UAT, MANUAL BOOK, MOM
• Sikespadu – BRS, SRS, FIGMA, UAT, MANUAL BOOK, MOM