Girl in Tech

What is SOW? SOW is a document that describes the terms and objectives of a project or service contract, including the scope of work required to meet the objectives, costs, deliverables, timelines, and other expectations. The document is shared by the vendor to the customer.  SOW Includes 1. Purpose: Purpose of project 2. Scope of Work: requirements of customer 3. Period of Performance: Expected year of completion of delivery of the solution.  4. Deliverables Schedule: scheduled delivery of milestones of project 5. Application Standards: Machines used in project, mechanism used to deliver the project, etc.  6. Acceptance Criteria: Customer defined milestone achievements to accept the project. 7. Payment Schedule: start of project, middle of project, end of project  8. Signoff: customer and the vendor sign off  SOW Template for EPM (Employee Performance Management) Purpose:

Cloud Computing Currently, over 90% of the organizations in the world are using cloud computing services to host their business infrastructure. The entire infrastructure set up is provided over the internet by a remote data center provided by a cloud service provider. The cloud infra requirements works on a consumption based pay-as-you-go model, organizations pay for the cloud services they use and not for comprehensive services all at once. The most common daily use examples of cloud computing is Google photos, Google drive, Gmail, Amazon Prime, Microsoft OneDrive, etc.  Image Source: Cloud Computing Let’s dive deep into various aspects of cloud computing. Advantages of Cloud Computing: Compared to the traditional IT infra set up, cloud computing offers various advantages. These are: Lower IT Cost : Organizations adopting cloud infrastructure are free of cost and effort of purchasing, installing, configuring, and managing the on-prem infrastructure. Improve agility and time to va...

Image Source: Tech Writers Tribe Agile Manifesto  With the adoption of Agile Manifesto, software development has changed its trajectory and so is the documentation. Agile software development paved the way for the technical documentation to change from normal documentation to Agile documentation process. One of the core principles in Agile Manifesto is Working software over comprehensive documentation”  This principle introduces two things for technical writers:   Stronger collaboration with the developers’ team to build documentation in line with the software development lifecycle. Minimum viable documentation that is good enough so that your customers can use that documentation right away. Software Developers and Technical Writers In Agile documentation, both the writers and developers respond to change quickly instead of following a predefined plan. Agile documentation is nothing but producing documentation based on Agile Manifesto. Technical writers work closely ...