SITCON
      • 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
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Write
        • Owners
        • Signed-in users
        • Everyone
        Owners 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

      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.
      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
    • Engagement control
    • Transfer ownership
    • Delete this note
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Versions and GitHub Sync Note Insights Sharing URL Help
Menu
Options
Engagement control 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
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Write
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners 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

    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.
    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
    Subscribed
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    Subscribe
    --- GA: UA-34467841-15 --- 就算是新手,有愛就沒把專案做出來,對吧 - 宏宏 === <blockquote> 本場將會以個人經歷出發,瞭解一幫學生如何模仿業界工程師、設計師以及產品經理的分工方式卻無情翻船。整場議程將會著重在我與系上好友為了賺取 20 萬元一起出國玩而參與某專案競賽,一路從產品發想、規劃、開發到翻船的歷程,並與會眾解析我們是如何失敗,其中有何處其他團隊可以借鏡之處,並在最後整理出一套輕量化適合學生團隊的專案開發方式。 ## 先備知識 個人經驗分享無須先備知識,唯有經歷過完整專案歷程的人會更能理解本議程 </blockquote> ###### tags: `SITCON 2020 共筆` `SITCON 2020` `2020` `共筆` `R0` {%hackmd dTfmj-h3QvSA0myqavKbxg %} > 請從這裡開始 ## Speaker - 宏宏 @ 台大資管 - 實習仔 - 開源社群 透過實習潛伏在商業界的工程師 ## 為什麼要講產品開發? - **失敗**太多次,透過這場 talk 來推坑 ## 為何參加比賽? - 小紅很窮 - 參加社群,組隊打怪 ### 團隊組成 - PM \*1 小紅 - UI \*1 - FE \*2 - BE \*2 #### 第一次討論 @麥當勞 大家吃得很開心 沒想法 下次再討論 #### 第二次 @肯德基 還是沒人有想法 小紅硬著頭皮提出了 "AI 雲端大數據雲端物聯網水果販賣機" #### 兩個關鍵錯誤 - 找太多人不利於團隊運作 > 一個團隊 size 最好在兩個 pizza (可以吃飽的人數,6~8人佳)以內 - 小紅身為 PM 與專案召集人,自己卻沒有想法 ## 過程 - 小紅叫設計師去做有夠華麗炫炮的介面,即使他沒有想法 - 小紅交給前端刻介面 - 前端消失了! - 小紅硬著頭皮硬幹 - 沒有得獎,又忘記領 1000 元安慰獎 #### 又兩個關鍵錯誤 1. 小紅沒有定義好專案 scope,導致根本做不完 2. 小紅沒有顧慮與追蹤到隊友的狀態,導致進度宕延 # 重來一次要怎麼把專案做成? ## 專案的四階段 1. 定義問題 & 問題分析 2. 制定企劃 & 產品規劃 3. 產品開發 4. 產品維護 & 營運 ## 1. 定義問題 & 問題分析 - 先對問題基本了解,避免解決錯誤的問題。 ### 問題表單 | 條目 | 說明 | |---|---| | 專案目標 | 專案要達成的明確目標 | | 專案脈絡 | 為何要達成這個目標的理由 | | 決策指標 | 幫助判斷是否達成專案目標的指標 | | 專案邊界 | 什麼樣的解決方案不用考慮 | | 解決方案邊界 | 解決方案有什麼限制(如預算限制) | > Source: [CTPS](https://reurl.cc/j7XZon )課程筆記 #### 範例 | 條目 | 說明 | |---|---| | 專案目標 | 幫助水果公司賣出更多水果 | | 專案脈絡 | 水果公司想要增加營收 | | 決策指標 | 水果公司營收、水果公司賣出水果數量 | | 專案邊界 | 不能夠破壞水果公司的高端大器上檔次的定位 | | 解決方案邊界 | 不要 Android | ## 定義清楚問題以後就要發想解決方案 要想出好點子別無他法,要運用生活中的各種情境來練習 要如何幫助水果公司賣出更多水果? - 早上搭捷運去學校 :arrow_right: ? - 在學校上課到中午 :arrow_right: ? - 中午放學後去打羽球 :arrow_right: ? 同時我們可以用用魚骨圖幫助思考解決方案 -> 例如問題拆成食衣住行育樂六個解決方案 e.g. - 衣: 跟 uniqlo 合作推出聯名商品(? UNIQLO 透過魚骨圖分析生活中的不同面向,迫使我們 (想出解決方案之類的) ## 制定企劃&產品規劃 接下來要開始寫 PRD 了對吧? <!--正確講法為小等一下--> ![小等一下.jpg](https://i.imgur.com/EO7Ut7v.png) 在這之前先研究一下競爭者是怎麼做的吧?畢竟能夠鑑往知來,才能避免前人踩過的雷。 - 量化分析 - 文獻研究 - 實際觀察 - 產品怎麼 work - 專家訪談與使用者訪談 > 有很多種途徑分析,因此不要忽略以免看不到 [人人都是產品經理](http://www.woshipm.com/) 搜尋競品分析、產品體驗等文章 接下來真的要開始寫 PRD 了對吧? ![小等一下.jpg](https://i.imgur.com/EO7Ut7v.png) 我們還要先討論正確的專案 scope 專案 scope 就是要界定我們要做什麼、不要做什麼 Step 1. 先盤點你想要做什麼樣的產品功能 Step 2. 評估那個功能比較重要?多重要? Step 3. 評估每個功能個需要花多少工 Step 4. 最佳化在有限的資源下要做什麼功能 ### 專案研究分享 > GoShare 如何透過產品分析解決亂停車問題 首先了解公司背景以及他們的目標 研究 GoShare 現在如何處理亂停車 分析租車流程分拆成幾塊,以幫助發想(類魚骨圖) - 租車騎乘之前 - 租車騎乘中 - 租車後 根據分組發想可能的解決方案,並評估 - 方案 - 可行性 - 時間投入 - 資源投入 - 潛在風險 - 影響力 - 減少頻率 - 增加體驗 - 影響範圍 - 評價 依照評估結果選擇最佳的解決方案 > 最後得到的解決方案是多做一個按鈕表示找不到車位 總算做出功能規劃與畫 Wireframe ## 產品開發 進入產品開發後將會有大量的團隊合作Juststrive1 因此大多都是人的問題 人的問題基本上要有愛跟同理就能化解 那要怎麼有愛跟同理呢 其實我也做不太到 (顏文字 但我們還是可以從兩方面關心隊友 1. 了解對方到底想要參與到什麼程度 - 全心奉獻 - 願意 996 - 願意固定每週奉獻 - 心情好就貢獻 - 路過看看(需要循序漸進) > 免得叫心情好貢獻的人做太多事,他就消失了 2. 保持專案透明度!讓大家知道在做什麼 小故事:段考時間,請同學幫忙但A給B做、B給C做,透明度下降 效果不好 ### Bonus. 時常關心你的~~對有~~隊友需要什麼協助 <3 - 讓你的隊友相信你 總算講完了 貓圖<!----> ## Bonus ### 真實商業專案跟學生團隊有什麼差別 1. 戰略思維 也就是要理解的深入又完整 e.g. 法律,上下游業者,etc. <!--好難RRR--> 2. 反覆斟酌產品功能 在商業團隊裡沒人會在製作過程不斷增加功能 > 同一個問題問五次 why,解決真正的問題 > e.g. 臺大腳踏車很常被偷 :arrow_right: 臺大腳踏車都不上鎖 :arrow_right: 腳踏車停車位不足,導致大家花太多時間找車位,沒時間鎖車 :arrow_right: 大部分學生得要走很遠的距離才能上下一門課 ... Why<sup>Why<sup>Why<sup>Why<sup>Why</sup></sup></sup></sup> ### 整場聽下來什麼都不懂? **實用工具推薦!讓你至少看起來專業** <!--XDDDDDD--> - [Figma](https://figma.com) - Prototyping like a pro! - [Whimsical](https://whimsical.com/) - Flowcharting like a pro! ### Q&A 實體見面or 線上? 遠端的成員,如何定期關心? - 如果有人很久都沒聲音,就可以關心一下 - 告訴他有什麼困難講沒關係,我們很願意幫忙 # 講者延畢 (重點)

    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

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    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