Skip to content

Commit

Permalink
Update rule.md
Browse files Browse the repository at this point in the history
  • Loading branch information
tiagov8 authored May 8, 2024
1 parent b58c7f0 commit 3bb8128
Showing 1 changed file with 5 additions and 3 deletions.
8 changes: 5 additions & 3 deletions rules/shadow-spec-reviews/rule.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,14 +12,16 @@ related:
- spec-add-value
created: 2023-11-27T00:34:16.382Z
guid: a3e51a8d-66d5-48e1-a109-f89d6a19ee15

---

Spec Reviews are a vital part of architecting a new solution for a client, they are the plans upon which a new project is modeled. They serve as a key stage in the pre-sales process for software development consultancies as they create an opportunity for the developers to demonstrate expertise and provide immediate value to the client. For these reasons alone, it is evident that those who are assigned to carry out this exercise must be well-trained in the matter.

<!--endintro-->

### Importance of Specification Reviews

As the documentation delivered at the end of the Spec Review is the foundation upon which the project is built, it is imperative that the proposed solution meets the client's needs as closely as possible, this includes proposing the correct choice of technologies (factoring in their budget from [corridor conversations](https://ssw.com.au/rules/corridor-conversations/)) and providing realistic estimates of time required per resource.
As the documentation delivered at the end of the Spec Review is the foundation upon which the project is built, it is imperative that the proposed solution meets the client's needs as closely as possible, this includes proposing the correct choice of technologies (factoring in their budget from [corridor conversations](/corridor-conversations)) and providing realistic estimates of time required per resource.

Involving developers with no experience in Spec Reviews can lead to significant issues; underestimates, a misunderstanding of the right tech for the job, or a miscommunication between the developer and the client could all have huge implications on the success of the project down the line. This highlights the need for a structured training approach.

Expand All @@ -40,6 +42,6 @@ Before being able to partake in an unsupervised Spec Review, the trainee develop

After successfully completing the shadowing and assistance phases, developers are ready to conduct Spec Reviews independently, equipped with the necessary knowledge and experience.

### Approval
### Approvals

If an Account Manager wants to add an additional dev to shadow a Spec Review, they should get [cross-approval](https://www.ssw.com.au/rules/cross-approvals/) from another Account Manager, to make sure it's necessary.
If an Account Manager wants to add an additional dev to shadow a Spec Review, they should get [cross-approval](/cross-approvals) from another Account Manager, to make sure it's necessary.

0 comments on commit 3bb8128

Please sign in to comment.