Purpose of this post is to describe the Software Project Audit Process which is capable of capturing different  activities which take place throughout a Software Project life-cycle. The main purpose of this process is to audit the quality of the deliverables at the client site. After the auditing, the quality level of the audited activity will be presented using a measurement called Metric.

The process will be used by both the Development team and the Software Project Audit team to derive their own metrics to measure the quality status of a software product in its life cycle. Eventually, the trends of such metrics will be used to predict or change the Projects' way forward by identifying any potential failures which can happen in the future.

Also in this post i will explain the several guidelines used by the Software Project Audit Process for Project Progress calculation, mapping Payment Milestones with Project deliverables and Project Artifact reviewing.

Further, it will explain the way how the process differ from typical software development life cycle and how it has been automated by integrating several testing tools and testing methodologies as well as embedding best industry standards.

Scope of this post is to provide an insight about ;
​

• Software Project Audit Process
• Importance of Metrics
• Analysis of Metrics
• Automated Process of Metric Generation
• Skills required to generate certain Metrics
• Guideline for Project Progress Calculation
• Guideline for Mapping Payment Milestones with Deliverables
• Guideline for Review of Project Artifacts.

​Last night was a long one and i was up and about till 2 AM in the morning looking at my laptop screen with amazement and some skeptical approach to the new features been presented at SharePoint Conference 2018 at Las Vegas.

​So here is my post on what was shared and whats coming in future when it comes to Digital Workplace through Microsoft SharePoint and Office 365.