今天就学习课程吧!
今天就开通帐号,24,600 门业界名师课程任您挑!
Lightweight modeling
- When we use the word agile to describe a person, we usually think of someone who is quick, nimble, and probably smaller, lightweight. This is why you may hear the terms lightweight requirements or lightweight modeling. Lightweight requirements and lightweight modeling encourage BAs to use the lightest approach possible to generate the right conversations and deliver valuable results. This does not mean that we do light analysis. It's more about that we are either looking deep at a small piece or wide in an overall context. We are not trying to analyze the details of everything at one time. On Agile teams, there is very limited work-in-progress. The team has an extreme focus on one small piece of functionality at a time while having the big-picture view. So given this intense focus, it's hard to justify heavy, upfront documentation and heavy, detailed models. What Agile teams and BAs do instead is focus on lightweight, context visuals and lightweight, visual models of the details…
随堂练习,边学边练
下载课堂讲义。学练结合,紧跟进度,轻松巩固知识。
内容
-
-
-
-
-
-
Product decomposition3 分钟 14 秒
-
(已锁定)
Context techniques2 分钟 50 秒
-
(已锁定)
User observation2 分钟 40 秒
-
(已锁定)
User stories3 分钟 37 秒
-
(已锁定)
What to do with technical stories?2 分钟 41 秒
-
(已锁定)
Acceptance criteria2 分钟 38 秒
-
(已锁定)
User story maps2 分钟 25 秒
-
(已锁定)
Scenario planning3 分钟 59 秒
-
(已锁定)
Story slicing and splitting2 分钟 43 秒
-
(已锁定)
Lightweight modeling3 分钟 29 秒
-
-
-