Topic: Software Development Team RFP

Camp: Agreement / 15K Design Sprint or Discovery / Consensus Design

Camp Statement History

Objected
Live
In Review
Old
Statement :

Consensus Design


This camp is for the purpose of building consensus around the best design. The best way to get started is for a first team to propose their design, below here in this camp statement. Then other teams can work to improve and fix things. If any disagreements emerge (an example being using Bit Bucket vs GitHub) we want to push those competing ideas down into the team camp statements, out of the way of what everyone does agree on in this super camp. It is good if disagreements are falsifiable and camp supports describe what would falsify their camp, for them, then things like A/B tests can be performed to achieve consensus experimentally.
-----------------------------------------------
Add the links to the subtopics for sections like UI/UX to the list:


Edit summary : Adding the updated UI/UX design Topic link
Submitted on :
Submitter Nick Name : Rohit_Talentelgia
Go live Time :
Statement :

Consensus Design


This camp is for the purpose of building consensus around the best design. The best way to get started is for a first team to propose their design, below here in this camp statement. Then other teams can work to improve and fix things. If any disagreements emerge (an example being using Bit Bucket vs GitHub) we want to push those competing ideas down into the team camp statements, out of the way of what everyone does agree on in this super camp. It is good if disagreements are falsifiable and camp supports describe what would falsify their camp, for them, then things like A/B tests can be performed to achieve consensus experimentally.
-----------------------------------------------
Add the links to the subtopics for sections like UI/UX to the list:


Edit summary : Adding the feature listing topic and Coding standards document topic links
Submitted on :
Submitter Nick Name : Rohit_Talentelgia
Go live Time :
Statement :

Consensus Design


This camp is for the purpose of building consensus around the best design. The best way to get started is for a first team to propose their design, below here in this camp statement. Then other teams can work to improve and fix things. If any disagreements emerge (an example being using Bit Bucket vs GitHub) we want to push those competing ideas down into the team camp statements, out of the way of what everyone does agree on in this super camp. It is good if disagreements are falsifiable and camp supports describe what would falsify their camp, for them, then things like A/B tests can be performed to achieve consensus experimentally.
-----------------------------------------------
Add the links to the subtopics for sections like UI/UX to the list:


Edit summary :
Submitted on :
Submitter Nick Name : Rohit_Talentelgia
Go live Time :
Statement :

Consensus Design


This camp is for the purpose of building consensus around the best design. The best way to get started is for a first team to propose their design, below here in this camp statement. Then other teams can work to improve and fix things. If any disagreements emerge (an example being using Bit Bucket vs GitHub) we want to push those competing ideas down into the team camp statements, out of the way of what everyone does agree on in this super camp. It is good if disagreements are falsifiable and camp supports describe what would falsify their camp, for them, then things like A/B tests can be performed to achieve consensus experimentally.
-----------------------------------------------
Add the links to the subtopics for sections like UI/UX to the list:


Edit summary : Change the links to sub topics into a bullet list.
Submitted on :
Submitter Nick Name : Brent_Allsop
Go live Time :
Statement :

Consensus Design


This camp is for the purpose of building consensus around the best design. The best way to get started is for a first team to propose their design, below here in this camp statement. Then other teams can work to improve and fix things. If any disagreements emerge (an example being using Bit Bucket vs GitHub) we want to push those competing ideas down into the team camp statements, out of the way of what everyone does agree on in this super camp. It is good if disagreements are falsifiable and camp supports describe what would falsify their camp, for them, then things like A/B tests can be performed to achieve consensus experimentally.
-----------------------------------------------
Let’s develop and build consensus around the JSON spec for the Canonized tree service over in its own topic and Application Scalability Architecture here.

Here is the Canonizer application scalability design link. Let's develop and build consensus over this Scalability Architecture topic

Edit summary :
Submitted on :
Submitter Nick Name : Iffort
Go live Time :
Statement :

Consensus Design


This camp is for the purpose of building consensus around the best design. The best way to get started is for a first team to propose their design, below here in this camp statement. Then other teams can work to improve and fix things. If any disagreements emerge (an example being using Bit Bucket vs GitHub) we want to push those competing ideas down into the team camp statements, out of the way of what everyone does agree on in this super camp. It is good if disagreements are falsifiable and camp supports describe what would falsify their camp, for them, then things like A/B tests can be performed to achieve consensus experimentally.
-----------------------------------------------
Let’s develop and build consensus around the JSON spec for the Canonized tree service over in its own topic.

Here is the Canonizer application scalability design link. Let's develop and build consensus over this Scalability Architecture topic

Edit summary :
Submitted on :
Submitter Nick Name : Rohit_Talentelgia
Go live Time :
Statement :

Consensus Design


This camp is for the purpose of building consensus around the best design. The best way to get started is for a first team to propose their design, below here in this camp statement. Then other teams can work to improve and fix things. If any disagreements emerge (an example being using Bit Bucket vs GitHub) we want to push those competing ideas down into the team camp statements, out of the way of what everyone does agree on in this super camp. It is good if disagreements are falsifiable and camp supports describe what would falsify their camp, for them, then things like A/B tests can be performed to achieve consensus experimentally.
-----------------------------------------------
Let’s develop and build consensus around the JSON spec for the Canonized tree service over in its own topic.

Edit summary : First Version
Submitted on :
Submitter Nick Name : Brent_Allsop
Go live Time :
Statement :

Consensus Design


This camp is for the purpose of building consensus around the best design. The best way to get started is for a first team to propose their design, below here in this camp statement. Then other teams can work to improve and fix things. If any disagreements emerge (an example being using Bit Bucket vs GitHub) we want to push those competing ideas down into the team camp statements, out of the way of what everyone does agree on in this super camp. It is good if disagreements are falsifiable and camp supports describe what would falsify their camp, for them, then things like A/B tests can be performed to achieve consensus experimentally.
-----------------------------------------------

Iffort's Core Design Architecture


Based on the series of discussions and current understanding of the system, we recommend the following architecture for the proposed system.

Server Architecture

https://www.iffort.com/clients/canonizer/server_architecture.png

Application Architecture

https://www.iffort.com/clients/canonizer/app_architecture.png

Please note that the above architecture is an initial draft and it will evolve as and when we learn more about the application.

Edit summary :
Submitted on :
Submitter Nick Name : Iffort
Go live Time :
Object Reason : The plan for structuring this platform is premature considering the problems present on the platform
Objector Nick Name : TheSmokingPeanut
Statement :

Consensus Design


This camp is for the purpose of building consensus around the best design. The best way to get started is for a first team to propose their design, below here in this camp statement. Then other teams can work to improve and fix things. If any disagreements emerge (an example being using Bit Bucket vs GitHub) we want to push those competing ideas down into the team camp statements, out of the way of what everyone does agree on in this super camp. It is good if disagreements are falsifiable and camp supports describe what would falsify their camp, for them, then things like A/B tests can be performed to achieve consensus experimentally.
-----------------------------------------------

Edit summary :
Submitted on :
Submitter Nick Name : Brent_Allsop
Go live Time :