Pahami Scrum dalam 10 Menit (Agile Methodology) Introduction to Scrum (Bahasa Indonesia) Bercerisa#1

Sadida Aruni
5 May 202011:53

Summary

TLDRIn this video, the speaker explores the Scrum methodology, emphasizing its adaptability for managing complex projects. Key components include the roles of the Product Owner, Development Team, and Scrum Master, as well as essential events like Sprint Planning, Daily Standups, Sprint Reviews, and Retrospectives. The speaker highlights the importance of prioritizing tasks in the product backlog based on risk and value while promoting a culture of continuous improvement. Viewers are encouraged to share their experiences with Scrum, fostering a collaborative learning environment around Agile practices.

Takeaways

  • 😀 The Schramm framework is a flexible approach to project management, suitable for various types of projects beyond software development.
  • 📅 Key roles in a Schramm team include the Product Owner, Development Team, and Scrum Master, each with distinct responsibilities.
  • 🔄 The framework promotes adaptive problem-solving, emphasizing the importance of continuous improvement throughout the project lifecycle.
  • 🔍 The Product Owner prioritizes the product backlog, ensuring that the team focuses on delivering the most valuable features first.
  • 🏗️ The Development Team operates autonomously and is accountable for delivering functional increments of the product.
  • 🗓️ Scrum events include Sprint Planning, Daily Stand-ups, Sprint Reviews, and Sprint Retrospectives, each serving a specific purpose in the project workflow.
  • ⚙️ The product backlog should be maintained with prioritized items based on risk and potential value to the customer.
  • ⏱️ Daily Stand-ups help the team stay aligned and address any obstacles in a brief, focused manner.
  • 📈 Sprint Reviews provide an opportunity to showcase completed work and gather feedback for future sprints.
  • 🛠️ The Retrospective encourages reflection on the process, allowing the team to identify successes and areas for improvement.

Q & A

  • What is the main focus of the video?

    -The video discusses the SCRUM framework, its principles, and how it can be applied in various projects, especially in software development.

  • What are the key components of a SCRUM team?

    -A SCRUM team consists of the Product Owner, Development Team, and SCRUM Master. Each role has specific responsibilities that contribute to the team's success.

  • What does the SCRUM process begin with?

    -The SCRUM process begins with planning the sprint, which includes setting objectives and defining what needs to be achieved during that period.

  • How is a product backlog prioritized in SCRUM?

    -The product backlog is prioritized based on various factors such as risk, revenue potential, and the overall value to the business, as determined by the Product Owner.

  • What is the purpose of a daily stand-up meeting in SCRUM?

    -The daily stand-up meeting, also known as the Daily Scrum, is a short meeting where team members discuss what they accomplished the previous day, what they plan to do today, and any obstacles they are facing.

  • How long is a typical sprint in SCRUM?

    -A typical sprint lasts one month or less, allowing for flexibility in adapting to changes in project requirements and complexities.

  • What is a sprint review, and what is its significance?

    -A sprint review is conducted at the end of each sprint to demonstrate the completed work, receive feedback from stakeholders, and assess progress towards the project's goals.

  • What is the purpose of a sprint retrospective?

    -The sprint retrospective is a meeting to discuss what went well, what could be improved, and how the team can enhance their processes in future sprints.

  • How does SCRUM handle changes in project requirements?

    -SCRUM is designed to be adaptive, allowing teams to adjust their work based on feedback and changes in project requirements throughout the development process.

  • What tools can help in implementing SCRUM practices?

    -Various tools exist to facilitate SCRUM practices, such as task management software, which helps track progress and manage product backlogs without relying on physical sticky notes.

Outlines

00:00

😀 Introduction to Scrum Framework

The speaker addresses common project management challenges and introduces the Scrum framework as a solution. They emphasize the importance of clear communication and adaptive processes in project execution. The Scrum framework is described as flexible, allowing teams to use various techniques and methods to achieve their goals. The roles within the Scrum team are defined, including the Product Owner, who prioritizes tasks; the Development Team, which develops the product; and the Scrum Master, who facilitates the process. The speaker also highlights the iterative nature of Scrum, where continuous testing and adaptations are essential.

05:00

😀 Sprint Planning and Execution

The speaker outlines the process of planning and executing sprints within the Scrum framework. They explain that each sprint has a maximum duration of one month to maintain focus and adaptability. The concept of defining product features through user stories is introduced, emphasizing the importance of understanding the user's perspective. Teams prioritize tasks based on risk and value, assigning story points to measure effort. Daily standups are discussed as a means for the Development Team to synchronize their efforts and address any obstacles encountered during the sprint.

10:02

😀 Review and Retrospective Processes

The video details the review and retrospective phases of Scrum. During the Sprint Review, the team demonstrates completed work and discusses what is still pending, ensuring that everyone has a clear understanding of the project’s status. The concept of 'Definition of Done' is introduced to clarify what constitutes completed work. In the Sprint Retrospective, the team reflects on their processes to identify what went well and areas for improvement. The speaker stresses the importance of continuous improvement in the Scrum methodology and encourages teams to remain adaptable and open to change.

😀 Summary and Next Steps in Scrum Implementation

In the concluding segment, the speaker summarizes the key roles and events in the Scrum framework, including the Product Owner, Development Team, and Scrum Master, along with various Scrum events such as sprint planning, daily standups, sprint reviews, and retrospectives. They encourage viewers to apply Scrum principles in their projects and invite feedback or questions in the comments section. The speaker hints at future videos discussing tools to facilitate Scrum practices, reinforcing the idea that implementing these practices can simplify project management for teams.

Mindmap

Keywords

💡Scrum

Scrum is a framework designed for managing complex projects, particularly in software development. It provides a structured yet flexible approach, allowing teams to adapt their processes based on the project's needs. In the video, Scrum is highlighted as an effective method for handling challenges that arise during product development, emphasizing its role in fostering teamwork and continuous improvement.

💡Product Owner

The Product Owner is a key role in Scrum responsible for defining the product vision and prioritizing the backlog of tasks. This individual acts as the liaison between stakeholders and the development team, ensuring that the team focuses on delivering the highest value features first. The video explains that the Product Owner determines the priorities based on market needs and business goals, illustrating their crucial role in guiding the project.

💡Development Team

The Development Team consists of professionals who work collaboratively to develop the product. They possess specialized skills and are accountable for delivering product increments during each sprint. In the transcript, the speaker discusses how the Development Team estimates their workload, highlighting their autonomy and responsibility in executing tasks effectively.

💡Sprint

A Sprint is a time-boxed period in which specific work has to be completed and made ready for review. Typically lasting between one to four weeks, Sprints allow teams to deliver a functional product increment regularly. The video emphasizes the importance of Sprints in maintaining a structured timeline for development, as well as the need for defining what 'done' means for each task within the Sprint.

💡Backlog

The Backlog refers to a prioritized list of tasks and features that need to be completed for the product. It is crucial for managing project scope and ensuring that the team works on the most valuable features first. The speaker mentions the 'product backlog' as a critical component of Scrum, indicating how prioritization impacts the project’s success.

💡Daily Stand-up

A Daily Stand-up is a brief meeting (typically 15 minutes) held by the Development Team to discuss progress and obstacles. During this meeting, team members answer three key questions: what they accomplished yesterday, what they plan to do today, and any impediments they face. The video underscores the value of Daily Stand-ups in fostering communication and accountability within the team.

💡Sprint Review

The Sprint Review is a meeting held at the end of a Sprint where the team demonstrates what has been completed. This event allows stakeholders to provide feedback and ensures that the product meets user expectations. The speaker explains how this review is essential for aligning the team's output with market needs and refining future development plans.

💡Retrospective

The Sprint Retrospective is a reflective meeting where the team discusses what went well, what didn't, and how to improve in future Sprints. This process promotes a culture of continuous improvement and adaptation, allowing the team to address any issues that hinder their productivity. The video highlights the significance of the Retrospective in enhancing team dynamics and project outcomes.

💡Definition of Done

The Definition of Done (DoD) is a clear and concise set of criteria that a product increment must meet to be considered complete. It helps ensure consistency and quality in the work delivered. In the transcript, the speaker emphasizes the importance of having a well-defined DoD before Sprint Review meetings to prevent misunderstandings about project progress.

💡Continuous Improvement

Continuous Improvement is an ongoing effort to enhance products, services, or processes through incremental and breakthrough improvements. In the context of Scrum, it is achieved through regular retrospectives and feedback loops. The video discusses how Scrum encourages teams to implement improvements iteratively, reinforcing the importance of adapting to new insights and challenges.

Highlights

Schramm is introduced as a flexible framework for addressing complex adaptive problems.

The importance of continuous testing and user perspectives in product development is emphasized.

Project planning begins with requirement gathering and design, followed by identifying significant mistakes made early on.

The framework is adaptable and can be applied to a wide range of projects beyond software development.

Key roles within the Schramm team include the Product Owner, Development Team, and Scrum Master.

Product backlog prioritization is based on value, risk, and expected revenue.

Sprint duration is limited to a maximum of one month to accommodate changes and manage risks effectively.

The daily stand-up meetings, known as Daily Scrum, focus on quick updates and eliminating obstacles.

Utilization of velocity measurement tools to track productivity and adjust workflows accordingly.

Sprint reviews involve a demo of completed work and discussion about what remains unfinished.

The Definition of Done (DoD) is crucial for assessing the completion of tasks in sprint reviews.

Sprint retrospectives aim to analyze the process, identify successes, and propose improvements.

Collaboration among team members is encouraged to ensure accountability and shared responsibility.

The framework can be adapted to various contexts such as event planning and product launches.

The session concludes with encouragement to share experiences and engage with future content on tools to enhance productivity.

Transcripts

play00:00

halo halo driven pernah ngasih kalian

play00:12

dapat curhatan kayak gini aduh simple

play00:14

Nggak jelas banget nih aku jadi serba

play00:16

salah harus gimana atau curhatan yang

play00:19

kayak udah gede produk tapi ternyata

play00:21

waktu launching ke market sudah nggak

play00:23

sesuai sama kebodohan market atau

play00:25

curhatan yang rileks banget kayak udah

play00:28

meeting tiga bulan tapi ternyata enggak

play00:30

Ada progres nah Masalahnya gini bisa

play00:33

terselesaikan dengan kram kebetulan

play00:36

beberapa minggu yang lalu aku habis

play00:38

service cammaster Saudi video kali ini

play00:41

kalian bakalan dibombardir berbagai

play00:43

informasi tentang schramm jadi please

play00:45

stay focus and keep on watching kami

play00:49

nengok banget sama yang namanya aja

play00:51

kalau dulu kita bikin Project turun

play00:54

pertama kita bikin requirements planning

play00:56

kedulan kedua kita bikin desain nah pas

play00:59

udah 1tahun

play01:00

kita nggak nyadar nih karena ada

play01:01

kesalahan besar yang terjadi di awal

play01:03

Kalau kami tutup kita menggunakan

play01:05

prinsip ajal jadi prosesnya kecil-kecil

play01:08

untuk menjalin for satu fungsi produk

play01:10

nah prosesnya itu bersifat generatif

play01:12

jadi kamu di tengah-tengah jalan bisa

play01:14

melakukan continuous testing maupun

play01:16

mengajak pulang Fokus dari Project so

play01:19

Apa sih schramm itu jadi Islam adalah

play01:22

sebuah kerangka kerja dia bukan proses

play01:24

teknik atau metode lagi Kamu sendiri

play01:27

bisa pakai berbagai teknik atau metode

play01:28

lagi di dalamnya jadi nggak ribet banget

play01:30

ya Nah pekerjaan Seperti apa kamu adalah

play01:33

karena kerja untuk menyelesaikan masalah

play01:35

yang Komplek adaptif Aduh jadi harus

play01:39

cukup Kompleks kalau misalnya dia

play01:41

terlalu simpel ya nggak perlu pakai

play01:42

scrub dan Years bersifat adaptif jadi

play01:45

enggak terlalu faktor gitu ya Project

play01:47

yang bisa bersifat fleksibel nah kayak

play01:50

apa sih yang bisa pakai sekarang kita

play01:52

tuh macem-macem banget karena memang

play01:55

terkenal di pembuatan software atau

play01:57

software development tapi sebetulnya

play01:58

enggak terbatas pada

play02:00

cuma bisa menggunakan sekarang untuk

play02:01

berbagai Project misalnya mengembangkan

play02:03

sebuah produk baru seperti mobil atau

play02:05

mungkin make up atau berhenti

play02:07

menyelenggarakan event atau bahkan

play02:09

membuat sebuah perusahaan baru atau

play02:11

bikin para baru Nah langsung aja siapa

play02:15

sih sebenernya yang tergabung dalam tim

play02:17

yang pertama ada kita sebut sebagai

play02:24

potong2 daripada kita Ia ini akan

play02:27

menentukan prioritas tentang megang

play02:29

kepentingan bisnis yang kedua ada

play02:31

development team atau mungkin nanti aku

play02:33

sebut sebagai DT sesuai namanya dia

play02:36

adalah yang mendevelop produknya ini

play02:39

bersifat organis Jadi mereka bisa

play02:42

bekerja dengan ketentuan mereka sendiri

play02:44

nah yang unik di development tim khusus

play02:47

ya sebagai development team kamu bisa

play02:49

mempunyai skill khusus tapi

play02:51

akuntabilitas itu tetap ada pada

play02:53

keseluruhan anggota Development tim dan

play02:56

yang terakhir ada semester semester ini

play02:59

berfungsi

play03:00

memfasilitasi sesuai dengan praktik dan

play03:02

tata nilai sekarang serta menghilangkan

play03:04

hambatan-hambatan yang muncul jadi

play03:06

diserang itu enggak ada yang namanya

play03:07

Project Manager ya Oke ini yang udah

play03:12

kita tunggu-tunggu jadi sebenarnya

play03:13

gimana sih kita menjalankan schramm

play03:16

secara umum kayak gini ya nanti bakalan

play03:18

aku bahas satu-satu ini adalah

play03:20

keseluruhan spring diawali dengan spray

play03:22

kita merencanakan springnya lalu ini

play03:26

diri skrub atau delimiting kita dan di

play03:28

akhir ada sprint review untuk mereviu

play03:31

produk yang kita kerjakan dan stempel

play03:33

retrospektif untuk mereview proses yang

play03:36

terjadi oke pertama bayangin kita mau

play03:39

bikin sebuah produk baik dari Customer

play03:41

dari eksekutif atau dari siapapun nah

play03:43

produk ini harus ditanya dari perspektif

play03:45

Mr ya this kami tuh fitur produk kita

play03:48

sebut sebagai Yesus Story karena kitanya

play03:51

demi perspektif user dan dituliskan

play03:53

kayak gini nih sebagai apa Aku ingin apa

play03:56

sehingga apa Nah kumpulan dari sektor

play03:59

ini

play04:00

tersebut sebagai produk decklok atau

play04:02

yang semacam bisnis Oke kita lihat

play04:05

produk backlog yang kita punya Nah kita

play04:07

bisa prioritaskan kode good lock ini

play04:09

prioritasnya berdasar apa sih Pertanyaan

play04:12

bagus Nah ini terserah daripada

play04:14

kontaknya bisa dari resiko yang besar

play04:15

bisa dari revenue ini bakalan bervariasi

play04:18

banget tergantung dari produk kalian dan

play04:21

tentunya tergantung dari kebijakan PP

play04:23

menentukan mana yang memiliki value

play04:24

paling besar lalu kita kasih banget nih

play04:27

masing-masing item sebagai yang disebut

play04:29

Story Point atau Ours bisa 12358 dan

play04:33

seterusnya nah disini itu udah bisa

play04:35

lihat ini perkiraan resiko ini kita

play04:37

lihat tahu prioritasnya kita udah tak

play04:39

bobotnya Nah kita bisa menentukan

play04:40

Bagaimana spring selanjutnya ah sprint

play04:43

apa ini nah adalah jantung dari sprint

play04:48

adalah batasan waktu untuk kita

play04:50

mendeliver potensial atau yang satu

play04:53

fungsi produk gitu loh ini kita mengenal

play04:56

namanya atau batasan waktu maksimal

play05:00

pantesan waktu maksimal dari scene ini

play05:01

adalah satu bulan kenapa ya karena kalau

play05:04

dari satu bulan definisi dari apa yang

play05:06

kita berkembangkan itu bisa berubah

play05:08

kompleksitasnya meningkat dan resikonya

play05:10

juga meninggal gimana Masih fokuskan

play05:13

sekarang kita bakalan bahasa cara

play05:15

pertama yang kita buat dalam mengawal

play05:17

Islam yaitu streamlining Disneyland ini

play05:21

kita akan menjawab Dua pertanyaan yaitu

play05:23

Apa sih yang akan kita selesaikan dispen

play05:25

ini dan gimana nyos airnya simpel aja

play05:27

sih kayak gitu paint box dari Stefan

play05:30

ingini delapan jam untuk paint yang 1

play05:32

bulan Jadi kalau misal screen Kalian

play05:34

tadi dua minggu Aceh setengahnya hanya

play05:36

bisa hitung sendiri nah di Tuban ini two

play05:40

atau produk akan membahas objektif dan

play05:42

produk because development team akan

play05:45

memperkirakan Apa sih yang bakal mereka

play05:46

kerjain atau kita sebut sebagai spring

play05:49

make up nah jumlah pekerjaan atau apa

play05:52

yang akan dikerjakan dalam springy

play05:53

ditunjukkan oleh development team ya

play05:55

kenapa ya karena mereka sendiri yang

play05:57

tahu dan bisa memperkirakan apa yang

play05:59

bisa mereka tuh

play06:00

Khan dalam satu thread ini jadi diprint

play06:03

gini Trump Tim akan menentukan spin-go

play06:06

produk backlog serta membahas kapasitas

play06:09

sebelumnya dan kapasitas terkini setelah

play06:11

streamlining kita masuk ke drilling

play06:14

skrub atau ya delimiting labossiere

play06:17

idealis kami ini 15 menit 15 menit aja

play06:19

ya dan biasanya dilakukan di tempat dan

play06:22

waktu yang sama kenapa ya karena

play06:24

konsistensi this complexity Jadi kalian

play06:27

gak perlu tuh mikirin ada warna penting

play06:28

mana ya enaknya apa ya sambutan dulu dan

play06:31

gak Babel lainnya padahal essence

play06:33

pembicaranya sebenarnya 15 menit aja

play06:35

bahkan biasanya Denis kamu itu disebut

play06:38

sebagai daily standart kenapa ya Karena

play06:40

Mereka berdiri waktu ngobrolin pekerjaan

play06:43

mereka itu bahkan ada sampai yang peleng

play06:45

dan mulut aku itu keren banget karena

play06:47

dengan ini kita terpacu untuk berpikir

play06:49

lebih cepat gitu kita nggak lihat-lihat

play06:51

dan langsung to the point gitu bisa

play06:53

kalau misal kita dudukkan kita jadi

play06:55

mager terus Gabut gitu kan Nah yang

play06:58

harusnya didirikan

play07:00

ini hanya development gamenya jadi sama

play07:02

seri itu hanya memastikan bahwa

play07:04

development team melakukan Dewi skom

play07:06

setiap hari serta menghilangkan

play07:07

hambatan-hambatan yang mungkin muncul

play07:09

Selama unit kami ini development team

play07:11

akan bahas tiga pertanyaan Jadi mereka

play07:14

akan kumpul terus cerita apa ya udah gue

play07:16

lakuin kemarin apa yang bakalan dilakuin

play07:18

hari ini dan hambatan apa yang akan

play07:21

mungkin kita hadapi Uke untuk mencapai

play07:23

screen gold Nah ada konsep yang menarik

play07:25

demi Islam untuk memantau produktivitas

play07:27

Legendary develop mesin namanya berendam

play07:30

cat bener cat ini menyediakan pengukuran

play07:33

Harian dari jumlah pekerjaan yang

play07:35

tersisa dalam satu Spain dari jadi

play07:38

gravitine itu kamu bisa lihat jumlah

play07:39

pekerjaan yang tersisa setiap harinya

play07:42

gitu sampai nanti sisanya itu sampai nol

play07:45

atau ya perginya udah selesai Nah lewat

play07:47

berendam cat ini kita bisa lihat

play07:48

rata-rata produktivitas development tim

play07:51

kita setiap harinya misalnya

play07:52

produktivitas harian tim kalian 50jta

play07:55

begitu nah kalian memperkirakan gimana

play07:57

sih kita bisa mempercepat ini atau

play07:59

bahkan kan bisa

play08:00

di mana tim kita kayak siput ya gitu oke

play08:03

setelah tadi kita dewisemi.com terus

play08:05

setiap hari kita akan masuk ke street

play08:08

food review ini kita akan bahas produk

play08:10

kita ya dah tembok dari steam review ini

play08:13

empat jam untuk steam yang 1 bulan Jadi

play08:15

kalau screen kalian itu 2minggu bagi

play08:17

setengahnya Atau Dua jam aja Ngapain aja

play08:20

sih kita di Steam review ini yang

play08:22

pertama adalah demo pekerjaannya udah

play08:23

selesai di sini produknya menjelaskan

play08:25

apa sih yang udah selesai dan apa yang

play08:27

belum selesai nah gimana sih kita

play08:29

menentukan apa yang udah selesai di sini

play08:31

kita mengenal namanya diody atau

play08:34

definition of dance ini penting banget

play08:36

karena jalan sampai antipasti review

play08:38

love lain bukannya gini kah info belum

play08:40

selesai atau hal semacamnya jadi waktu

play08:43

itu perlu untuk kita definisikan di awal

play08:45

di sini nggak juga mengenal namanya

play08:47

elemen atau Jumlah semua produk BP item

play08:50

yang dihasilkan selama sprint termasuk

play08:52

semua penambahan dari screen sebelumnya

play08:54

intinya destined to ini seluruh tim

play08:57

disitu ngobrolin tuh produktif

play09:00

Khan direvisi dan mendefiniskan item

play09:02

yang mungkin untuk spring selanjutnya

play09:04

untuk mobil ini mereka bisa

play09:05

mempertimbangkan Gimana keadaan pasar

play09:07

potensi kemudahan di market anggaran

play09:09

yang ada potensi the kapabilitas tim

play09:11

kita dan lain-lain yang outputnya adalah

play09:14

produk bengkok yang direvisi dan

play09:16

mendefinisikan item untuk sprint

play09:18

selanjutnya itu seperti apa finally kita

play09:22

sampai di acara terakhir Denis kram

play09:24

yaitu sprint retrospektif Nah kalau tadi

play09:27

spring review kita bahas produknya

play09:29

disprin retrospektif ini kita bahas

play09:32

prosesnya tembok dari steam retrospektif

play09:34

ini sendiri Tiga jam untuk sprint yang 1

play09:37

bulan Jadi kalau misalnya dua minggu

play09:39

berapa satu setengah jam setengahnya aja

play09:41

gitu nah intinya di sini kita bakal

play09:45

ngobrolin tuh tiga hal apa sih yang

play09:47

berjalan baik akan perlu kita improof

play09:49

dan gimana isn't kita untuk mengimprove

play09:51

nya karena Emang prinsip kami tua jadi

play09:54

kita akan melakukan komisi improvement

play09:56

setiap saat gitu jadi kayak kayak dan

play09:58

kita gini enaknya kayak gini deh

play10:00

kek apa kek gitu itu akan dibahas di

play10:02

retrospektif oke udah selesai Gimana nih

play10:06

pasti bombardir informasi banget karena

play10:09

buat kalian yang bingung pasti Kalian

play10:11

tadi nggak fokus nih tapi tenang aja

play10:14

karena aku baik hati jadi bakal aku

play10:16

Richard semuanya yang pertama siapa aja

play10:18

sih yang ada di schramm tim ada produk

play10:20

owner yang punya produk backup dan

play10:22

nentuin prioritas ada development team

play10:24

yang mengerjakan produk dan ada serta

play10:26

Master yang mempraktekkan nilai-nilai

play10:28

skrub terus ada apa aja sih event-stream

play10:31

itu yaitu ada sprint tuh Young Lex

play10:34

dengan screen printing untuk

play10:35

merencanakan stringnya ada deliska

play10:37

Matauli standard 15 menit setiap hari

play10:40

Senin review untuk review produknya dan

play10:43

sprint retrospektif untuk mereviu

play10:45

prosesnya terus yang ketiga apa aja sih

play10:47

aktif Dari sekam ada produk the club

play10:49

atau semacam wishlistnya Medan sprint

play10:52

backlog dan informan atau produk backlog

play10:55

yang selesai dari status pria tersebut

play10:58

bisa

play11:00

nah mantap-mantap udah di saya

play11:02

mengimplementasikan kami kehidupan

play11:03

kalian Mungkin dia Wah pasti bakal

play11:05

memang informasi baru tapi ketika kali

play11:07

dengan jalan ini tu gampang banget kok

play11:10

janji yang penting Jalani dulu aja so

play11:13

buat kalian yang udah pernah

play11:14

mengimplementasi kalau sampaian boleh

play11:16

cerita di kolom komen atau kalau misal

play11:19

kalian punya pertanyaan-pertanyaan bisa

play11:21

juga ditanyain Disini di video

play11:23

selanjutnya aku bakalan cerita tentang

play11:25

tools untuk mempermudah kita menjalankan

play11:27

sekarang Jadi kalian gak perlu tuh

play11:29

manual nempel-nempel Sticky notes buat

play11:31

bikin produk clock Nah nanti akan aku

play11:33

ceritain tuh terusnya tuh bisa apa aja

play11:35

dan gimana Cara pakainya so jangan lupa

play11:37

subsribe video ini untuk kita belajar

play11:41

dan bercerita bareng tentang hal-hal

play11:43

yang penting bagi milenial di era

play11:45

sekarang

play11:46

kau see you on my next video bye

Rate This

5.0 / 5 (0 votes)

Etiquetas Relacionadas
Scrum FrameworkProject ManagementTeam CollaborationAgile PracticesProduct DevelopmentSoftware EngineeringProduct OwnerDevelopment TeamDaily ScrumSprint Review
¿Necesitas un resumen en inglés?