-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
30 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
+++ | ||
title = "交付 Ship" | ||
date = 2024-11-18 | ||
description = "成功的交付超越技術層面,需了解高層期待並維持信任。提前揭露問題,保持高效溝通才能成為項目的英雄。" | ||
|
||
[taxonomies] | ||
categories = [ "閱讀筆記",] | ||
tags = [] | ||
|
||
+++ | ||
|
||
創作者:[Sean Goedecke](https://www.linkedin.com/in/sean-goedecke-5495a7137/) | ||
|
||
文章:[How to Ship](https://www.seangoedecke.com/how-to-ship/) | ||
|
||
很有趣的觀點。 | ||
|
||
作者用公司內的社會共識來形容交付。與開發完全不同,即使把功能做完且部署,若高層不滿意,不能被稱之為交付。 | ||
|
||
所以重點是要知道高層對專案的期待是什麼,是為大客戶客製化、爭取使用者數,還是沒原因特別看重的寵物專案,不同的情況需要重視的部分都不同。 | ||
|
||
要成功的交付,需要維持高層對你的信任。過往的戰功是最好的證明,但如果還沒有,必須持續表現自信、專業能力,保持清晰的溝通、為風險設想備案。以上都比準時上線還重要。趕不上死線,只要好好溝通,通常不是大問題,有時還讓你成為解決問題的英雄。 | ||
|
||
# 盡可能提前交付,不要害怕 | ||
|
||
在到生產環境前總是會冒出很多疑問,最好的戰略就是讓這些問題盡早浮現。 | ||
|
||
不斷問自己「現在可以交付了嗎?」如果不行,找出差距在哪裡,克服它,盡可能提前部署。 | ||
|
||
作者提到在專案前期,你通常只需要投入 20% 的能量來實作,而在最後階段,你必須提升到 90% 以上來面對真正的問題。 |