Search results
- Dictionarysignificant/sɪɡˈnɪfɪk(ə)nt/
adjective
- 1. sufficiently great or important to be worthy of attention; noteworthy: "a significant increase in sales" Similar Opposite
- 2. having a particular meaning; indicative of something: "in times of stress her dreams seemed to her especially significant"
Powered by Oxford Dictionaries
Significant: Having or likely to have a major effect; 'a significant hazard' a significant risk' , a significant increase (or decrease) in trends/accidents/etc, a significant number of persons have been affected, a significant number have not! CFT
The major changes involve a significant amount of preparation and work with complex situations or major expenses. Examples: Implementation / upgrade of a corporate business application; Moving a computer room; Significant Changes: Significant changes involve preparation and work, evaluation, authorization and planning for change. Examples:
One way of viewing significant risk would be something which would have more impact than the control measures necessary to prevent it; so the risk arising from a wet floor (stf, lost-time injury, legal fees, management time all divided by likelihood) would cost more than the act of drying the floor, in this view a wet floor is a significant risk.
In the ever-growing complexity of dependencies amongst products at the build and run time level, there is the challenge of managing increasingly separate items that must work together upon release. This is where the concepts, disciplines, roles, and responsibilities of release management help. Release management focuses on both the engineering disciplines that must bring a specific project release together along with the management of external dependencies across products that must accompany ...
Can anyone define the difference, if there is one, between a safe system of work and a method statement? My understanding, and I'm ready to be corrected, is that a method statement should be a detailed written process (like a recipe) of how the job should be carried out and together with other relevant documentation (risk assessments, coshh assessments, pre-use inspection records etc) make up the safe system of work.
But, of course, that requires using := with the problems described above. Another alternative is the following simple caching scheme. First, I define a function cache which automatically caches a macro's value the first time it is evaluated and retrieves it from the cache for each subsequent attempt to retrieve it.
Define fine-grained promotion-levels that are consumer/role-specific. One can define numerous levels of quality assurance, but the ones that are important enough to represent new milestones in the evolution of a configuration are when that configuration has successfully transitioned to the next-level consumer in the value-chain.
Flexible sprints define a closure point nicely; whether it’s for a two-week or six-month release cycle, the length of a sprint should become shorter as we come closer to the release date. I often start with a three-week sprint and move to a two-week sprint and, finally, a one-week sprint as we reach the deadline for releasing the product.
The errors that people commit have significant impact on our projects. First, because we expect errors, we plan for them by including reviews, audits and tests as part of our project plan. This time and expense is simply part of what we do on projects because we know that people make mistakes.
Mar 4, 2023 · FWIW, in our internal reporting we have 'accident' for something that causes any injury to an individual, 'significant incidents' and 'other minor incidents', but the latter two categories are not defined with any legalese and it's up to the investigating individual whether they categorise it as something significant or something minor.
