CI Cheat Sheet (DRAFT) by Skucuk

By hosting requir­ement workshops and leveraging priori­tiz­ation frameworks like MoSCoW.

A checklist of what makes a task or feature complete

high-level insights for executives and technical details for engine­ering teams

While at Huawei, I analyzed customer billing data to identify ineffi­cie­ncies in prepaid plans, leading to optimized pricing strategies that improved customer satisf­action by 15%.

docume­ntation and iterative reviews with stakeh­olders, multiple validation sessions and peer reviews

A basic version of a product with just enough features to use.

I start by defining objectives and collecting data from reliable sources. For instance, during my master’s thesis, I conducted in-depth trade analysis between Turkey and China, identi­fying key growth opport­unities for exporters.

diagrams and analogies

I share updates, listen to feedback, and solve problems together.

consulting stakeh­olders and aligning their expect­ations with organi­zat­ional goals. detailed requir­ement decomp­osition and change management processes

JIRA, Conflu­ence, BABOK Teq.

Rules that define if a task or feature meets the requir­ements.

Anything that blocks the team's progress

assess their impact on sprint goals, reprio­ritize tasks

breaking tasks into smaller milestones and using Gantt charts to track progress

• A meeting at the end of a sprint to discuss what went well and what can improve.

A meeting to show what was completed in the sprint.

Day Meeting Descri­ption
Day 1 Sprint Planning Define sprint goal and select tasks.
Day 2-14 Daily Stand-Up Share updates and discuss blockers daily.
Day 7 Backlog Refinement Update and prioritize tasks for the next sprint.
Day 14 Sprint Review Present completed work to stakeh­olders.
Day 14 Sprint Retros­pective Reflect on the sprint and plan improv­ements.