YU-SHIH-PENG
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note No publishing access yet

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.

      Your account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

      Your team account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

      Explore these features while you wait
      Complete general settings
      Bookmark and like published notes
      Write a few more notes
      Complete general settings
      Write a few more notes
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights New
    • Engagement control
    • Make a copy
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Make a copy Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note No publishing access yet

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.

    Your account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

    Your team account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

    Explore these features while you wait
    Complete general settings
    Bookmark and like published notes
    Write a few more notes
    Complete general settings
    Write a few more notes
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       Owned this note    Owned this note      
    Published Linked with GitHub
    1
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    ###### tags: `專案管理` `上課筆記` # [專案管理學程第七周:敏捷專案管理,大/小型專案管理差異,行銷/營運/開發專案管理差異](https://learn.bizthinking.com.tw/packages/8B32cF/intro) ## 一、敏捷專案管理 ### A、敏捷的核心,交付價值,獲取回饋與提高應變能力 #### 敏捷開發宣言 - 個人與互動 重於 流程與工具 - 可用的軟體 重於 詳盡的文件 - 與客戶合作 重於 合約協商 - 回應變化 重於 遵循計畫 #### 敏捷12原則 ![](https://i.imgur.com/fES5Y93.jpg) #### 12原則拆三大部分(團隊、客戶價值、成果) 敏捷核心在於客戶價值,團隊核心在於信任,成果核心在於價值觀 ![](https://i.imgur.com/ZFvEnqr.png) #### 傳統方法 VS 敏捷 傳統:希望一步到位把東西建立起來,在每Step下逐步注入資金,最後成品出來在上市售價。但此時對於上市售價定額與實際狀況還處於未知。 ![](https://i.imgur.com/bKk8dFw.png) 敏捷:一開始先建造一個較簡單的成品汽車,先上市售價看狀況,在實際回饋中在決定作第二個版。在投入更多資金作功能增加與異動外,再次上市再觀察回饋作出第三個版本,以此方法邏輯持續創造價值。 ![](https://i.imgur.com/Ck7cvKZ.png) ### 敏捷專案三大重點 - 1.降低風險 - 2.盡早交付價值 - 3.持續改善 ### 敏捷兩大難題 - 1.什麼才是價值:交出什麼才有價值 (根據數據脈絡定義) - 2.如何切割與交付:先交什麼價值最大(專案價值量化處理) ### 導入敏捷的兩個練習 - 1.試著將專案size切小 - 從季到月、從月到雙周,短周期仍要交付,會逼你思考價值與優先級。 - 2.進行每日站立會議 - 練習每天能有產出,是學習頻繁交付的第一步 --- ![](https://i.imgur.com/o67DqNe.png) --- ### B、OTPR敏捷工作法,個人最有效學習敏捷方法 學了敏捷方法,但公司不導入,如何應用在個人身上持續學習 --- ![](https://i.imgur.com/PDZkqJq.png) --- #### OTPR - O: OKR, Objective and Key Result - 設定清晰且具體的組織/個人目標與成長/短期目標 - T: Time Management - 運用科技科學方法,有規則的排出有先順序 - P: Project Management - 運用專案管理技巧,擰定可行計畫,並作好應變準備 - R: Retrospective - 惠顧覆盤,從經驗中學習,讓自己持續精進 #### OTPR又稱為周迭代 - 以一周為一個專案 - 每周作計畫,控計畫 - 每天作回顧與覆盤 - 每周作回顧與覆盤 - 周一開始,周日結束,持續迭代 #### 使用OPTR ##### Step1:先開啟你的行事曆 一般狀況下,上面除了會議與活動外,其他都空白的 ![](https://i.imgur.com/i4b7CtE.png) ##### Step2:在每周日晚上,幫自己排妥下周計畫 將處理事件也排上日曆,因為未排上的事物,某種程度就會有不確定性,這其實也是一個很好的練習專案規劃的經驗。 寫文件需花你多少時間? 你要面談需要花你多少時間? ![](https://i.imgur.com/CgMGjFv.png) ##### Step3:排出的計畫有那些不確定? ![](https://i.imgur.com/P4ZNElP.png) ##### Step4:過程中作異動 ![](https://i.imgur.com/8RMm57d.png) ##### Step5:回顧與覆盤 - 你交付什麼? - 下禮拜怎麼改善? - 排下禮拜計畫? ![](https://i.imgur.com/yj7mUVn.png) 盤點原因 ![](https://i.imgur.com/R0LA1d5.png) --- ![](https://i.imgur.com/eUzrLvj.png) --- ## 二、大/小型專案管理差異 ### A.大型專案控管難題 #### 大型專案特性 ![](https://i.imgur.com/OMyFq3X.png) ##### 以數位轉型為例 - 1 ![](https://i.imgur.com/U5I9uQ3.png) ##### 以數位轉型為例 - 2 ![](https://i.imgur.com/fLfW8Xv.png) ##### 以數位轉型為例 - 3 透過以上流程,雖經過多次會議討論,但還是難以統整。在這狀況下老闆可能覺得你應該準備好了就要求你開工了~ 此時的你,心理大致有幾個問題 --- ![](https://i.imgur.com/L0WcZCe.png) --- #### 大型專案特性困難度最大原因-不確定性 ![](https://i.imgur.com/7H6gR9t.png) #### 轉型類專案兩個起手勢 - 設定階段目標 (逐步交付,減少不確定性) - 解決特定問題 - 引入特定流程 - 從某個產品開始 - 從某個部門開始 - 成立獨立團隊 (小團隊運作,減少不必要協作) - 少人數、多能工 - 團隊專注一件事 - 減少專注利害關係人 - 團隊自主決策權 --- ![](https://i.imgur.com/6JiGSDj.png) --- #### 對於不確定性-EX1:生產100萬支Iphone 因有一定的SOP標準流程,且需求不會變來變去。雖然工作量很大,但對於生產100萬支Iphone目標其實不難。 ![](https://i.imgur.com/tMx7hBn.png) --- ![](https://i.imgur.com/YJdc1L0.png) --- ### B.大型專案控管要訣 #### Road Map ![](https://i.imgur.com/N3Ecims.png) #### 要訣一:切階段,設定里程碑 ![](https://i.imgur.com/Zps7Wrm.png) --- ![](https://i.imgur.com/BOoxcFv.png) --- #### 要訣二、建立資訊同步機自 利用溝通平台來作訊息同步 ![](https://i.imgur.com/nVy1i0r.png) 建立專案執行計畫 - 1.專案基本資訊 - ![](https://i.imgur.com/Lq42vwS.png) - 2.專案需求列表 - ![](https://i.imgur.com/tzCIxyf.png) - 3.專案組織 - ![](https://i.imgur.com/fMV2vka.png) - 4.ARCI表 - ![](https://i.imgur.com/iNfyC3l.png) - 5.專案風險管理計畫 - ![](https://i.imgur.com/WRkH0vO.png) - 6.變更管理紀錄 - ![](https://i.imgur.com/qbD3NqL.png) - 7.專案工作環境 - ![](https://i.imgur.com/ukd6gFH.png) #### 要訣三、招開定期會議 ![](https://i.imgur.com/vm3nAbS.png) ## 三、多元專案控管重點-行銷類 ### 不同專案的特性 ![](https://i.imgur.com/DOenicd.png) ### 行銷類專案保證成效迷思 #### 行銷不確定性2大來源 - 流量不確定 - 廣告成效不確定 - 活動熱度不知夠不夠 - KOL業配效果不知好不好 - 行銷主軸不知道是否抓隊 - 客戶篇好不確定 - 商品是否符合期待 - 價格是否有吸引力 - 其他競爭的產品 #### 行銷專案規劃 ##### Normal規劃排成狀況 ![](https://i.imgur.com/m5ryTvn.png) 規劃完,有考慮到以下不確定性嗎? - 發10次eDM,會換回多少訂單? - 投30萬,會換回多少訂單? - 花10萬找業配,會換回多少訂單? - 粉專貼文100次,會換回多少訂單? ##### 行銷不確定高的原因再哪? - 廣告太多人競爭,轉換變差,成本拉高 - eDM打開率低,點擊率也低 - KOL業配,也得看KOL主力受眾 - 粉專貼文,觸及率... ##### 行銷確定性高的特徵 - 原生流量高(內容好、產品好、服務好) - 搜索流量高(SEO布局漂亮) - 流量來源多元(多個漏斗) - 轉換流程順暢CTA明確(轉換率高) --- ![](https://i.imgur.com/sFYnxGF.png) --- ### 檢查項目表範例(量化基本概念,還是得面對現實) ![](https://i.imgur.com/eIMxDgV.png) 橙色地方越多,想隊來說能達到的機率就越高 ![](https://i.imgur.com/hM7ICtc.jpg) --- ![](https://i.imgur.com/JBp3TlQ.png) --- #### 範例一、糕餅販售 ![](https://i.imgur.com/O1J8mQ8.jpg) - 口味不確定:小規模試吃,門市試吃 - 包裝不確定:網頁先行 a/b testing - 價格不確定:限量預購,門市小規模試銷 --- ![](https://i.imgur.com/xLMH1Cw.png) ---

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password
    or
    Sign in via Facebook Sign in via X(Twitter) Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    By signing in, you agree to our terms of service.

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully