Journal entries
This commit is contained in:
parent
ffdac104b0
commit
22a8709292
1 changed files with 14 additions and 0 deletions
|
|
@ -117,3 +117,17 @@ the ticket without the spec then the assigned dev would have had problems. So
|
||||||
this planning work has potentially saved time, avoided some pretty nasty tech
|
this planning work has potentially saved time, avoided some pretty nasty tech
|
||||||
debt and bugs, and saved me the headache of trying to fix those problems after
|
debt and bugs, and saved me the headache of trying to fix those problems after
|
||||||
the initial feature rollout.
|
the initial feature rollout.
|
||||||
|
|
||||||
|
@goal Develop a system for writing functional specs that can be used by devs
|
||||||
|
and testers.
|
||||||
|
|
||||||
|
# 2025-09-11
|
||||||
|
|
||||||
|
Conversation with dev revealed that he had missed or forgotten a lot of the
|
||||||
|
team's plan (and reasons behind the plans).
|
||||||
|
|
||||||
|
Made me realise that the things that we discuss in meetings and chats are
|
||||||
|
ephemeral.
|
||||||
|
|
||||||
|
@goal Write down all decisions that affect the team, including context and
|
||||||
|
rationale where necessary.
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue