Gung Ho SummaryEssay Preview: Gung Ho SummaryReport this essayGung Ho! By Ken BlanchardGung Ho was a story about a small town factory that was underperforming, and a new manager and seasoned employee who used the below principals to turn the plant into a world-class process.
The Spirit of the SquirrelЄДÐWorthwhile workImportantLeading to shared goalsValue-drivenЄДÐI try to ensure the work I do is driving value for the firm, and find ways to reduce unnecessary tasks that create additional administrative burden on others. For example, I stopped sending monthly SOX emails to the finance department because I felt they were not communicating any valuable news and were just another email others had to read.
The Way of the BeaverЄДÐIn control of achieving the goalA playing field with clearly marked territoryThoughts, feelings, needs and dreams are respected, listened to and acted uponAble but challengedЄДÐWhen a clear ÐЎЧplaying fieldÐÐŽÐÐ is not given to me, I ask what is expected and what the boundaries are, and focus on evaluating the process and ways I can improve it. I also try to given clear guidelines for projects I guide others on. For my Audit Committee deliverable, I am constantly receiving input from others that I work with and putting more efficient and effective controls in place, and reducing unnecessary burden. For example, instead of printing and reprinting sections
, the committee decides to let others create their own sections to be able to use in their own projects, and give the section’s title descriptive text. And so on and so forth, the committee has to work carefully on the content of the document using the process that is usually being used by the committee. A particular approach, however, takes place in which the committee simply creates the section headings and inserts it into documents, allowing others to do the same if need be. It’s a good way to make sure all the “right things will pass”, and so the committee has to take care that their work is kept transparent and to take care to avoid mis-doing.
7. What is the goal of a project to create, maintain, or improve a specific piece of code or service?
An example: this is a project that was created from scratch, but has its own development group that is not part of the audit process (e.g., a team of experts is working on a project); so I want to create a project that I don’t have to go through for a task like: making a library or some other piece of software that is an extension of the library. The following are a few examples:
If a specific service (like Github) is in use (because such a service gives up time in order to support its own projects that share the same API, etc., etc.): that service is not allowed on the project site and instead only available for review, maintenance, and revision, as described in the documentation document. If the service has been requested by another library creator (i.e., because a team member may or may not have the same product that the project has).
If the service has been requested by an external project or a third-party (i.e., if the project has no API, there is no support for it yet).
The following scenario would explain: the project is now on GitHub and an external developer is requesting to get it into one place and to build a repository to serve what is an external product or product that should be made available to other projects:
In this case, I use a version control system (VCS) to get to Github and to list projects and to have the list accessible for review and revision only. I also use Github’s API to view the project’s status since it is a project and its repository has been approved by both an internal team or external team. In short, I write my own code that I check periodically to find out how to submit issues to Github