-
Notifications
You must be signed in to change notification settings - Fork 330
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Knowledge transfer #59
Comments
When VISTA is Open, it is Open. When you get the software, you get the software. It is an interpreter and actually runs the source code. This is why we can capture the line of code when there is an error. There is over 1.6 gigabyte of documentation available from the VISTA Documentation Library. This has been extracted and collected so that the documentation can be freely distributed to any who wants it. VISTA is all about technology transfer in this countryand over-seas.. |
@HABruce Thanks for the comment. I think you are referring mostly to documentation related to how the service is built, for the benefit of knowledge transfer to other team members who will be adding features or doing maintenance on the software in the future. Is this correct? |
My frustration in my arena is that the amount of documentation "required" Curtis On Mon, Aug 25, 2014 at 6:46 PM, HABruce notifications@github.com wrote:
|
I mentioned this because documentation is a well known weak point of On 9/10/2014 5:40 PM, ruckc wrote:
|
Originally yes... On 9/10/2014 5:13 PM, Charles Worthington wrote:
|
Documentation needs to have a clear consumer. If we don't have someone Software developers generally know better than to rely on documents to Documentation needs consumers, and so user manuals, operations manuals, and Robin Dymond, CST Somewhere in the process it might be helpful to suggest that agile process
— |
I don't mean to seem argumentative...BUT On 9/10/2014 9:06 PM, Robin Dymond wrote:
|
Fortunately I don't have to rely on opinion for this issue. Client #1 uses Scrum for creating software to operate Pacemakers. They have Client #2 uses Scrum with a product development division of over 400 IBM uses Scrum to manage the development of WebSphere, the most used Java Documentation does not determine the success or failure of Agile Robin Dymond, CST
|
Possibly I don't understand the purpose of this exercise. The referenced (e) Design history file(DHF) means a compilation of records which (f) Design input means the physical and performance requirements of a (g) Design output means the results of a design effort at each design (h) Design review means a documented, comprehensive, systematic (i) Device history record (DHR) means a compilation of records (j) Device master record (DMR) means a compilation of records containing (k) Establish means define, document (in writing or electronically), and all of which clearly indicate an articulated record (documentation) of So you are quite right...it is not about opinion...in the case of FDA I am aware the average project contemplated by you Playbook and TechFAR My area of concern is strictly medical and specifically where this I brought this to the attention of the team an intention to collaborate On 9/12/2014 1:48 AM, Robin Dymond wrote:
|
We’d like to spend more time learning about this one. We think there is potential for a new play on knowledge transfer and sustaining services. Please continue to share references to best practices on how to determine the appropriate amount of documentation for digital services. |
Hi Charles, There are no best practices. "[Best Practice] has a chilling effect on our progress as an intellectual See more at James Bach's blog on this topic. cheers, Robin Dymond, CST On Wed, Sep 24, 2014 at 5:26 PM, Charles Worthington <
|
WoW Robin, Looks like you and I are simply bound to bump heads on this "sacrifice Attempting to perfect a lasting framework without an introspective loop My sense of what we are trying to accomplish is a cultural On the other hand, I am sensitive to the burden of documentation. HAB On 9/24/2014 10:58 PM, Robin Dymond wrote:
|
Hey Charles, Just a few lines on my way out the door... I suggest a study of Edwards Demming's writings...maybe begin with "The He's about culture building...the goal of knowledge transfer and change However, if you are interested in FDA-type documentation I'm not sure where you want to go with this...I don't mean to be coy but Multi-agent infrastructure projects are not a new concept. It is I wrote in my reply to Robin that I consider "cultural value HAB On 9/24/2014 7:26 PM, Charles Worthington wrote:
|
Hi Charles, As mentioned in a couple places in HAB's missive, Agile methods rely on Thanks, Robin Dymond, CST On Thu, Sep 25, 2014 at 5:36 AM, HABruce notifications@github.com wrote:
|
Sorry for my late response...once again, I am forced to agree with Robin The difference between banging out a coded product and developing I would expect someone in Robin's position to take a similar tack, Learning (accreted) systems are not new...nor are difficult problems. I've reached the end of the evaluation process in the absence of HAB On 9/25/2014 11:29 AM, Robin Dymond wrote:
|
I am bowing out of this conversation. It has become unproductive. As with Robin Dymond, CST On Thu, Sep 25, 2014 at 5:12 PM, HABruce notifications@github.com wrote:
|
Howdy, I've been searching for open source systems that are also documented with 820 in mind. Rather than enforce changes on contributors, I'm going to attempt simply describing how social networks like github works, eg how the culture of safety works and develops. For the sections @HABruce mentions, I plan on saying, see "git flow" and github materials, changelogs, pull requests. Then in audits, reporting, I plan on using a tool to mine the data and usage trails from the APIs github and other systems make available. Ideally, the audit trails should help observing whether or not the process was followed, as well as how effective it was. In particular, a tool could use github's API to export weekly/monthly roll ups on issues closed/opened. The issues themselves could be design discussions closed/opened as design inputs, with pull requests, and the discussions on pull requests archiving the review. Is anyone attempting to use APIs to observe and document requirements to fulfill CFR 820? Is VISTA using git-flow? Does VISTA have an open set of documents to satisfy 820 et al? http://process-controls.readthedocs.org/en/latest/index.html |
Hello Ben, On 1/21/2015 8:54 PM, Ben West wrote:
|
Although I have been a member for a while, I haven't spoken up. I am interested in GT.M V6.3. It has been announced as released, but hasn't made available. I suspect that their intensive testing has revealed something that caused the release to be delayed. For our testing and development purposes, we could probably benefit from seeing the current version and concerns list and aid in helping to make this release stronger and more resilient. |
Howdy @HABruce, been a long time. Since we last chatted, FDA invented It's been quite an interesting journey... |
Somewhere in the process it might be helpful to suggest that agile process workpapers and artifacts should collate into an articulated document as a proxy for work-in-process (and potentially thereafter) documentation...as this is one of the most common problems of “ad hoc” development. It can be accomplished in various ways from a wiki to a conscientious effort to stream the abstraction process using artifacts (potentially in journal form - which may be reviewed or not) depending on the criticality of the mission software. Making knowledge transfer a priority from early planning through execution will assist the process at every level and is unlikely to occur without specification. I could go on but I'm hoping the group gets the point and will help expand on the concept. Specification must begin early and documentation is important for improvement and innovation. I'm simply guessing clients would like to assist innovations/improvements after the project is complete...particularly when released to open source.
The text was updated successfully, but these errors were encountered: