Tai: Diary

1. 回避（脅威） / 活用（機会）
   Avoid / Exploit
   
2. 減少（脅威） / 強化（機会）
   Reduce / Enhance
   
3. 転嫁（脅威）
   Transfer (threat / opportunity)
   
4. 共有（脅威または機会）
   Share (threat / opportunity)
   
5. 受入れ（脅威）
   Accept (threat / opportunity)
   
6. 代替（脅威）
   Prepare contingent plans
   
7. 却下（機会）
   2017年度版は無いように見える。
   

• Timescales
  The question to ask for timescales is, “When will the project be finished?”
  
• Cost
  Projects have to give a return on investment; therefore, the questions to ask are: Are the costs being controlled? and are we within a budget?
  
• Quality
  Will the product be usable at the end of the project (in other words, fit for purpose) and are products passing their quality checks?
  
• Scope
  Is the scope well defined and clear to all stakeholders? Care must be taken by the Project Manager to avoid scope creep, which is to allow new requirements to be added during the project.
  
• Benefits
  Why are we doing this project and what are the benefits? Benefits must be known, clear, and measurable, and the benefits need to be delivered.
  
• Risk
  All projects are unique and therefore have risk. How much risk can we take on and how can risk be managed? For example, in a project concerned with building a house, what happens if one of the subcontractors does not show up?
  

• RFP（提案依頼書）とは？コンサルが教えるRFPの全知識と必要性
  https://it-koala.com/rfp-629
  
• Request For Proposal - Project Management Docs
  https://www.projectmanagementdocs.com/template/project-documents/request-for-proposal/
  

1. 選挙区
   県から選出される数名から1名を選ぶ。市町村でなく県。
   すべての政党が含まれるわけではなく、自身が希望する政党名が無いことがある。
   
2. 比例代表
   自身が推薦する政党または政党候補者を選ぶ。
   
   
   
   • 投票所の記載表に、全政党の一覧がある。
     
   • 一覧には選挙区よりも多くの候補者名がある。自身の県でなく、各政党の推薦者と思われる。
     
   • 誰が誰か分からなければ、政党名を書けば良いと思うが、その人の政策を知っていて、その人に投票すれば、その人への一票に繋がると思われる。よって、ただ政党を選ぶよりも、一票の重みが増すと思われる。
     
   
   

• メインは選挙区で、比例代表の存在自体の情報が少ない。投票所へ行って存在を知り、その場で選ぶことになる。結果、軽率に投票する。
  
• 選挙区がメインなので、候補者の調査をしがち。しかし、所属政党の中で、その人一人の発言は弱く、政党の方針が優先されるのは容易に想像つく。よって候補者の調査は無意味。
  
• 候補者でなく政党の方針を調べ、自身が選ぶ政党に所属する候補者を選ぶのが良い。政党が小さいならば、それだけで議席数を増やす手助けになる。
  

• 一箇所ではなく複数ある。但し、閉館時刻は18:00のところが多い。20:00まで空いているのは市役所のみなので注意。
  
• 公布日の翌日から投票可能なのは市役所のみ。その他は投票日の一週間前なので注意。
  

• 14 general management practices


• 17 service management practices


• 3 technical management practices

General management practices

1. Architecture management


2. Continual improvement (ITIL 3から継続)
   Aligning the organization's practices and services with changing business needs through the ongoing improvement of products, services, and practices, or any element involved in the management of products and services.


3. Information security management (ITIL 3から継続)
   Protecting the information needed by the organization to conduct its business.


4. Knowledge management (ITIL 3から継続)
   Maintaining and improving the effective, efficient, and convenient use of information and knowledge across the organization.


5. Measurement and reporting (ITIL 3から継続)
   Supporting good decision-making and continual improvement by decreasing the levels of uncertainty.
   
   
   
   • Critical success factor (CSF)
   
   
   • Key performance indicator (KPI)
   
   
   
   


6. Organizational change management


7. Portfolio management (MoPに関連)


8. Project management (PRINCE2に関連)


9. Relationship management
   Establishing and nurturing the links between the organization and its stakeholders at strategic and tactical levels.


10. Risk management (M_o_Rに関連)


11. Service financial management
    Supporting the organization's strategies and plans for service management by ensuring that the organization's financial resources and investments are being used effectively.


12. Strategy management


13. Supplier management
    Ensuring that the organization's suppliers and their performances are managed appropriately to support the seamless provision of quality products and services.


14. Workforce and talent management

Service management practices

1. Availability management


2. Business analysis
   Analyzing a business or some element of it, define its associated needs, and recommend solutions to address these needs and/or solve a business problem, which must facilitate value creation for stakeholders.


3. Capability and performance management


4. Change control (ITIL 3から継続)
   Maximizing the number of successful service and product changes by ensuring that risks have been properly assessed, authorizing changes to proceed, and managing the change schedule.


5. Incident management (ITIL 3から継続)
   Maximizing the negative impact of incidents by restoring normal service operation as quickly as possible.


6. IT asset management
   Planning and managing the full lifecycle of all IT assets, to help the organization.


7. Monitoring and event management (ITIL 3から継続)
   Systematically observing services and service components, and record and report selected changes of state identified as events.


8. Problem management (ITIL 3から継続)
   Reducing the likelihood and impact of incidents by identifying actual and potential causes of incidents, and managing workarounds and known errors.


9. Release management (ITIL 3から継続)
   Making new and changed services and features available for use.


10. Service catalogue management (ITIL 3から継続)
    Providing a single of consistent information on all services and service offerings, and to ensure that it is available to the relevant audience.


11. Service configuration management (ITIL 3から継続)
    Ensuring that accurate and reliable information about the configuration of services, and the CIs that support them, is available when and where it is needed.


12. Service continuity management
    Ensuring that the availability and performance of a service are maintained at sufficient levels in case of a disaster.


13. Service design (ITIL 3から継続)
    Designing products and services that are fit for purpose, fit for use, and that can be delivered by the organization and its ecosystem.


14. Service desk (ITIL 3から継続)
    Capturing demand for incident resolution and service requests.


15. Service level management (ITIL 3から継続)
    Setting clear business-based targets for service levels, and to ensure that delivery of services is properly assessed, monitored, and managed against these targets.


16. Service request management
    Supporting the agreed quality of a service by handing all pre-defined, user-initiated service requests in an effective and user-friendly manner.


17. Service validation and testing
    Ensuring that new or changed products and services meet defined requirements.

Technical management practices

1. Deployment management
   Moving new or changed hardware, software, documentation, processes, or any other component to live environments.


2. Infrastructure and platform management


3. Software development and management