Last active
November 2, 2021 04:09
-
-
Save voroninman/10966973 to your computer and use it in GitHub Desktop.
Revisions
-
voroninman revised this gist
Apr 17, 2014 . 1 changed file with 18 additions and 18 deletions.There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode charactersOriginal file line number Diff line number Diff line change @@ -1,20 +1,20 @@ # Engineering Excellence Scorecard | Process | Questions | | ------- | --------- | | Product/Project Management | <ul><li> Do we have clearly articulated goals and measures of success for every project?</li><li>Do we have clearly articulated scope for every project?</li></ul> | | Development | <ul><li>Do we have predictable and repeatable process?</li><li>Do we have clear doneness criteria?</li><li>Do we have any impediments to productivity?</li></ul> | | Source Code Management | <ul><li>Do we have an effective branching model?</li></ul> | | Release | <ul><li>Do we have zero downtime release process?</li><li>Do we have continius integration?</li></ul> | |QA | <ul><li>Do we have 100% code review coverage?</li><li>Do we have 80%+ automated unit test coverage?</li><li>Do we have 80%+ automated integration test coverage?</li><li>Do our staging environments adequately represent production environments?</li></ul> | | Monitoring | <ul><li>Are we alerted to all critical issues?</li><li>Are we warned before issues become critical?</li><li>Do we have the monitoring board with realtime top metrics?</li></ul>| |Exception Handling| <ul><li>Are all exceptions handled?</li></ul>| |Logging| <ul><li>Do we have gaps in logging?</li></ul>| |Backup| <ul><li>Is all data backed up?</li><li>Have we tested recovery?</li></ul>| |Disaster Recovery| <ul><li>Will our applications stay up when an entire data center goes down?</li></ul>| |User Satisfaction| <ul><li>Do we have user satisfaction gaps?</li></ul>| |Uptime| <ul><li>Do we have any single point of failure?</li><li>Is failover fully automated?</li><li>Do we comply with uptime SLA?</li></ul> | |Performance| <ul><li>Do we have clearly articulated performance SLAs?</li><li>Do we regularly test performance?</li></ul>| |Scalability| <ul><li>Do we understand how much load can our systems handle?</li><li>Do we regularly stress test?</li><li>How quickly can we scale?</li></ul> | |Security| <ul><li>Do we have any security exposure?</li></ul>| |Regulatory Compliance| <ul><li>Do we have any legal exposure?</li></ul>| -
voroninman revised this gist
Apr 17, 2014 . 1 changed file with 9 additions and 9 deletions.There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode charactersOriginal file line number Diff line number Diff line change @@ -7,14 +7,14 @@ | Source Code Management | <ul><li>Do we have an effective branching model?</li></ul> | | | Release | <ul><li>Do we have zero downtime release process?</li><li>Do we have continius integration?</li></ul> | | |QA | <ul><li>Do we have 100% code review coverage?</li><li>Do we have 80%+ automated unit test coverage?</li><li>Do we have 80%+ automated integration test coverage?</li><li>Do our staging environments adequately represent production environments?</li></ul> | | | Monitoring | <ul><li>Are we alerted to all critical issues?</li><li>Are we warned before issues become critical?</li><li>Do we have the monitoring board with realtime top metrics?</li></ul>| | |Exception Handling| <ul><li>Are all exceptions handled?</li></ul>| | |Logging| <ul><li>Do we have gaps in logging?</li></ul>| | |Backup| <ul><li>Is all data backed up?</li><li>Have we tested recovery?</li></ul>| | |Disaster Recovery| <ul><li>Will our applications stay up when an entire data center goes down?</li></ul>| | |User Satisfaction| <ul><li>Do we have user satisfaction gaps?</li></ul>| | |Uptime| <ul><li>Do we have any single point of failure?</li><li>Is failover fully automated?</li><li>Do we comply with uptime SLA?</li></ul> | | |Performance| <ul><li>Do we have clearly articulated performance SLAs?</li><li>Do we regularly test performance?</li></ul>| | |Scalability| <ul><li>Do we understand how much load can our systems handle?</li><li>Do we regularly stress test?</li><li>How quickly can we scale?</li></ul> | | |Security| <ul><li>Do we have any security exposure?</li></ul>| | |Regulatory Compliance| <ul><li>Do we have any legal exposure?</li></ul>| | -
voroninman revised this gist
Apr 17, 2014 . 1 changed file with 16 additions and 16 deletions.There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode charactersOriginal file line number Diff line number Diff line change @@ -2,19 +2,19 @@ | Process | Questions | Notes | | ------- | --------- | ----- | | Product/Project Management | <ul><li> Do we have clearly articulated goals and measures of success for every project?</li><li>Do we have clearly articulated scope for every project?</li></ul> | | | Development | <ul><li>Do we have predictable and repeatable process?</li><li>Do we have clear doneness criteria?</li><li>Do we have any impediments to productivity?</li></ul> | | | Source Code Management | <ul><li>Do we have an effective branching model?</li></ul> | | | Release | <ul><li>Do we have zero downtime release process?</li><li>Do we have continius integration?</li></ul> | | |QA | <ul><li>Do we have 100% code review coverage?</li><li>Do we have 80%+ automated unit test coverage?</li><li>Do we have 80%+ automated integration test coverage?</li><li>Do our staging environments adequately represent production environments?</li></ul> | | | Monitoring | <ul><li>Are we alerted to all critical issues?</li><li>Are we warned before issues become critical?</li><li>Do we have the monitoring board with realtime top metrics</li></ul>?| | |Exception Handling| <ul><li>Are all exceptions handled</li></ul>?| | |Logging| <ul><li>Do we have gaps in logging</li></ul>?| | |Backup| <ul><li>Is all data backed up?</li><li>Have we tested recovery</li></ul>?| | |Disaster Recovery| <ul><li>Will our applications stay up when an entire data center goes down</li></ul>?| | |User Satisfaction| <ul><li>Do we have user satisfaction gaps</li></ul>?| | |Uptime| <ul><li>Do we have any single point of failure?</li><li>Is failover fully automated?</li><li>Do we comply with uptime SLA?</li></ul> | | |Performance| <ul><li>Do we have clearly articulated performance SLAs?</li><li>Do we regularly test performance</li></ul>?| | |Scalability| <ul><li>Do we understand how much load can our systems handle?</li><li>Do we regularly stress test?</li><li>How quickly can we scale?</li></ul> | | |Security| <ul><li>Do we have any security exposure</li></ul>?| | |Regulatory Compliance| <ul><li>Do we have any legal exposure</li></ul>?| | -
voroninman revised this gist
Apr 17, 2014 . 1 changed file with 1 addition and 1 deletion.There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode charactersOriginal file line number Diff line number Diff line change @@ -2,7 +2,7 @@ | Process | Questions | Notes | | ------- | --------- | ----- | | Product/Project Management | <li>Do we have clearly articulated goals and measures of success for every project?</li><li>Do we have clearly articulated scope for every project?</li> | | | Development | <li>Do we have predictable and repeatable process?<li>Do we have clear doneness criteria?<li>Do we have any impediments to productivity? | | | Source Code Management | <li>Do we have an effective branching model? | | | Release | <li>Do we have zero downtime release process?<li>Do we have continius integration? | | -
voroninman revised this gist
Apr 17, 2014 . 1 changed file with 1 addition and 1 deletion.There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode charactersOriginal file line number Diff line number Diff line change @@ -2,7 +2,7 @@ | Process | Questions | Notes | | ------- | --------- | ----- | | Product/Project Management | <ul><li>Do we have clearly articulated goals and measures of success for every project?</li><li>Do we have clearly articulated scope for every project?</li></ul> | | | Development | <li>Do we have predictable and repeatable process?<li>Do we have clear doneness criteria?<li>Do we have any impediments to productivity? | | | Source Code Management | <li>Do we have an effective branching model? | | | Release | <li>Do we have zero downtime release process?<li>Do we have continius integration? | | -
voroninman revised this gist
Apr 17, 2014 . 1 changed file with 1 addition and 1 deletion.There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode charactersOriginal file line number Diff line number Diff line change @@ -2,7 +2,7 @@ | Process | Questions | Notes | | ------- | --------- | ----- | | Product/Project Management | * Do we have clearly articulated goals and measures of success for every project? * Do we have clearly articulated scope for every project? | | | Development | <li>Do we have predictable and repeatable process?<li>Do we have clear doneness criteria?<li>Do we have any impediments to productivity? | | | Source Code Management | <li>Do we have an effective branching model? | | | Release | <li>Do we have zero downtime release process?<li>Do we have continius integration? | | -
voroninman created this gist
Apr 17, 2014 .There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode charactersOriginal file line number Diff line number Diff line change @@ -0,0 +1,20 @@ # Engineering Excellence Scorecard | Process | Questions | Notes | | ------- | --------- | ----- | | Product/Project Management | <li> Do we have clearly articulated goals and measures of success for every project? <li>Do we have clearly articulated scope for every project? | | | Development | <li>Do we have predictable and repeatable process?<li>Do we have clear doneness criteria?<li>Do we have any impediments to productivity? | | | Source Code Management | <li>Do we have an effective branching model? | | | Release | <li>Do we have zero downtime release process?<li>Do we have continius integration? | | |QA | <li>Do we have 100% code review coverage? <li>Do we have 80%+ automated unit test coverage? <li>Do we have 80%+ automated integration test coverage? <li>Do our staging environments adequately represent production environments? | | | Monitoring | <li>Are we alerted to all critical issues? <li>Are we warned before issues become critical?<li>Do we have the monitoring board with realtime top metrics?| | |Exception Handling| <li>Are all exceptions handled?| | |Logging|<li>Do we have gaps in logging?| | |Backup|<li>Is all data backed up?<li>Have we tested recovery?| | |Disaster Recovery|<li>Will our applications stay up when an entire data center goes down?| | |User Satisfaction|<li>Do we have user satisfaction gaps?| | |Uptime|<li>Do we have any single point of failure?<li>Is failover fully automated?<li>Do we comply with uptime SLA? | | |Performance| <li>Do we have clearly articulated performance SLAs?<li>Do we regularly test performance?| | |Scalability|<li>Do we understand how much load can our systems handle?<li>Do we regularly stress test?<li>How quickly can we scale? | | |Security|<li>Do we have any security exposure?| | |Regulatory Compliance|<li>Do we have any legal exposure?| |