risk-first/website

Risk-First Software Development

website's Issues

Move Wiki to gh-pages

As discussed in Gustavo's PR, gh-pages might be a better way to host this content than github wiki

#13

@gandrade

Missing `www` CNAME DNS entry

Folks,

I've tried to access Risk First website typing www.riskfirst.org, but it seems that it wasn't configured. I guess that creating a CNAME DNS entry for www would be enough to solve it.

Does it make sense?

Please invite me your community

I've starred this repo, can you add me to your community?

Home Page Discussion

Comment Here

I would like to join this organization.

Capitalization issues in Audience section

In the 2nd and 3rd paragraph of , "This" starts with a capital T (which I don't think is proper). See bolded T-s below:

But here's a warning: This is going to be a depressing book to read. It is book one of a two-book series, but in Book One you only get to meet the bad guy.

While Book Two is all about how to succeed, This book is all about

Minor word correction on the betting-on-RPA.md page

Minor word correction on the betting-on-RPA.md page
On line 3 : Sytsem -> System

Quick Summary page feedback

On the https://github.com/risk-first/website/wiki/Quick-Summary page I have found that the capitalization of "Can" is inconsistent in the section titles: in section 2 and 3, "can" starts with an uppercase C, in section 4 and 6, "can" starts with a lowercase "C".

In Section 4, the link is to a Key-Man Risk, but the page is titled Coordination Risk. Should the link text be updated to reflect this?

Request to join the org

I have already starred the repo.

Consider changing adding other roles or revise developer role in the Audience section

I feel that the audience section should also include engineers wearing roles other than Developers:
https://github.com/risk-first/website/wiki/Audience

Even though I have not read the book yet, I really do hope that the book will be a useful resource for teams where the developer / tester roles are still segregated. Maybe using a more general term like engineers or those working in the trenches (individual contributors) would be more appropriate. I am pretty sure that the risk management is important in testing activities.

Broken link found (https://docs.github.com/articles/which-remote-url-should-i-use)

Broken link found

Broken Link Checker found a broken link on https://github.com/risk-first/website

Target: https://docs.github.com/articles/which-remote-url-should-i-use

HTTP_503

View Actions Results

Please invite me your community

Please invite me your community

Broken link in Meeting Reality

We should be able to weigh these separate risks in our hands and figure out whether the (Glossary#pay-off) makes a given Action worthwhile.

The term Pay Off is not properly linkified. I'd send a PR but there doesn't appear to be a way to do so.

A Simple Scenario page feedback

Comments on the https://github.com/risk-first/website/wiki/A-Simple-Scenario page:

2nd paragraph:

Lets for a moment ...

Maybe this should be changed to "Let's - for a moment - " ..

In the "Hidden Risks" section, I would change the following sentence:

The difference is, Attendant Risks are risks you are aware of, but can't be sure of the amount they will impact you

I feel that "can't" is a strong word here. I would replace that with "may not be". I feel that it is universally not necessarily true that the impact of attendant risks are unknown. Of course, unless I misunderstood the definition.

Wrong link in Evaluating Risk

Third, as soon as you publish a date it changes the expectations of the project (see Student Syndrome).

Student syndrome should link here, but instead links to Schedule Risk.

use single term for pay-off

There are different terms right now:
Pay-Off, Pay off, Pay Off

https://github.com/risk-first/website/wiki/Meeting-reality#pay-off

Seems that Payoff or Pay off are the correct ones. Usage of Payoff makes the biggest sense to me.

https://www.merriam-webster.com/dictionary/payoff

Double negation / extra isn't on A Pattern Language page

I find that the following sentence in the "What This is Not" section of
https://github.com/risk-first/website/wiki/A-Pattern-Language has an extra "isn't":

Neither is this site isn't going to be an exhaustive guide

Request to join the organisation

Can I join the organization?

Cover Legal/Regulatory Risk

This needs to be mentioned in slightly more detail (with examples) on the Operational Risk page.

Request to join the organisation

Can I join the organization?

Basic Errors on Stop-Estimating-Start-Navigating

How many of you write programs every working day?

So you know the subject you're talking about. Or trying to teach others how to do good estimations, write decent programs and stuff like that.

Organization URL is incorrect

https://github.com/risk-first displays https://risk-first.org instead of https://riskfirst.org/

Rapid Feedback loop

Hi,

I quickly read through the risks section. What I miss is the rapid feedback loop.
A way to mitigate risks is to get rapid feedback. Why is this important? Because the biggest risk, delivering the wrong feature, can only be addressed by users actually using the system. So risks are indeed a factor, but so is time.

Like you describe the internal model. The internal model changes with time. Not only because of our growing insight, but also because the world we live in changes and so does the context of our software.

BTW A developer making changes in production is not necessarily a disaster; provided that the risks are small / acceptable and the value the change brings, information / feedback, compensates for the risk. Like for a website a small bug is a not as disastrous as it would be for a bank. Especially nowadays in the micro services world where we architect with failure in our design. (E.g. a rating service in a website temporarily off line)

In the ideal world the developer makes the changes in production to get the most rapid feedback. In most cases this is not acceptable, because of the risks as you point out. However most of the things we do to mitigate risks, also slows us down. Here is the trade-off you need to make.

HTH

Stephan

HOW TO GET INVITED TO THE COMMUNITY

Github user name: GaurabKundu1
mail: [email protected]

invite me

.invite me

Broken link found (https://docs.github.com/articles/which-remote-url-should-i-use)

Broken link found

Broken Link Checker found a broken link on https://github.com/risk-first/website

Target: https://docs.github.com/articles/which-remote-url-should-i-use

HTTP_503

View Actions Results

Request to join the org

All Risk Management page feedback

A few comments for the
https://github.com/risk-first/website/wiki/All-Risk-Management page:

• the dots at the end of section titles should be removed (Every Action Has Attendant Risk., Every Decision Is About PayOff.)
• the last section link actually links to the page that is two sections before the current one. This is inconsistent

Request to join the org

Use gender neutral term "Key Person" instead of "Key Man"

...because there are lots of key people out there who aren't men 🙂

The wikipedia page that is linked from the text is already named "Key Person ..." so there's precedent for this term there. I don't think it changes the meaning or makes it less easy comprehensible either, but is a bit more inclusive.

I've changed the occurrences I could find: georgebashi/risk-first@2f35f38

I've also tidied up the inconsistency in usage between hyphenated and non-hyphenated. Totally a style thing so let me know if you prefer the hyphenated version and I'll push a new commit.

Thanks a lot for a really practical, down-to-earth and informative read!

Broken link found (https://docs.github.com/articles/which-remote-url-should-i-use)

Broken link found

Broken Link Checker found a broken link on https://github.com/risk-first/website

Target: https://docs.github.com/articles/which-remote-url-should-i-use

HTTP_503

View Actions Results

Please invite to this community :)

Github username - hemantwasthere
Email - [email protected] || [email protected]

I am really passionate towards open source, looking forward to working with you guys 😊