SPRINT, A short, repeatable work cycle in Scrum, SCRUM, The most popular Agile framework based on sprints, AGILE, A project mindset that values fast communication and flexibility, WATERFALL, A traditional, slow project method with big stages, BACKLOG, A prioritized list of all tasks and features, OWNER, The person who represents business interests and priorities, MASTER, A servant-leader who protects the team process, ANALYST, A specialist who translates business needs into technical tasks, DEVELOPER, An engineer who writes code, TESTER, A specialist who finds bugs and checks software, DESIGNER, A professional who creates user interfaces and layouts, STANDUP, A short 15-minute daily team meeting, PLANNING, A meeting held to choose tasks for the sprint, REVIEW, A meeting where the team demonstrates working software, RETROSPECTIVE, A meeting where the team reflects on mistakes to improve, BLOCKER, Any unexpected obstacle that stops a developer from working, IMPEDIMENT, Another formal word for an obstacle in Scrum, PRIORITY, The order of importance assigned to backlog tasks, DATABASE, A structured digital system used to store project data, BUG, An error or flaw in software, FEATURE, A distinct function or capability built into an app, DEADLINE, The specific date by which a task must be finished, CLIENT, The customer who pays for the software, STAKEHOLDER, Anyone outside the team who has an interest in the project, ESTIMATE, An approximate calculation of time needed for a task, INCREMENT, The usable piece of software produced during a sprint, FLOWCHART, A diagram used to visualize process logic, CRITERIA, Specific conditions that show when a task is finished, VALUE, The commercial benefit a feature delivers to business, INTERVIEW, A structured conversation used to discover client needs

Unit 2

さんの投稿です
印刷
埋め込み

リーダーボード

表示スタイル

オプション

AI強化版:この活動にはAIによって生成されたコンテンツが含まれています。詳細情報。

テンプレートを切り替える

自動保存: を復元しますか?