Technical Writer
Advantage of
Technical Writer
- SYSTEM BUSINESS PROVEN EXPERTISE
- SAVE COST
- BUSINESS ROADMAP GOALS
- System Business Proven Expertise
- Have insights on system / business operation with proven expertise and experience
- Save Cost
- Save cost, because not all problems / pain point could be solved by building system / apps, sometimes it only just need simple tools to answer the problems
- Full Control of System Development
- Have planning and full control of system development which comply with company workflow / procedure
- Business Roadmap Goals
- Creating Roadmap for system development based on Business Priorities and Goals
- Contributions
- Sometimes it will need opinion and contribution from end users so in the future there will be no hassle while adapting to the system or developing the system and we will make sure end user will have contribution in the system planning by doing interview / brainstorming with the end user
Pre-requisites
-
- Client signature on SPK / Agreement
-
- Short brief about the project / apps that consists of the description of the project, purpose of the project, target user, and integration to internal system (if any)
-
- Client will need to assign one PIC as communication channel to Client’s teams
Deliverables
MOM/Minutes of Meeting
MOM for every discussion by chat / phone / video call / direct meeting
Documentation
SRS / FSD / BRD / Blueprint document (if not finished completely in 3 months, the contract will be extended, but development could be started based on the finished blueprint and the blueprint will consist of minimum 2 - 3 milestones or months of development)
- Will adapt BPMN 2.0 but not all of them will be implemented, just a few that Yada Ekidana classify as important for development process based on Yada Ekidana' experiences
- Flowchart for all business processes
- User Stories / Use Cases (detail explanation of flowcharts)
- State Diagram for every User Stories / Use Cases
- Activity Diagram for every User Stories / Use Cases
- ERD / database design
- Class diagram
- UI/UX storyboard
- Mock-up and/or design
- Traceable Matrix (if needed)
- Priority of development or Roadmap (if needed)
BAST
BAST for every module
Team Members
on Technical Writer
The team may consist of software developers, designers, business analysts- in essence, people with all of the skills required to bring the project to fruition.
Workflow for
Technical Writer
Get in touch
What can we do to help you?
Tell us your goals, timeline, and constraints. We’ll recommend the fastest path to value.