2nd Product Tank Jakarta Meetup

In this meetup, i’ll share how communication from product goal should be built and derived into team then into personal team goal, and how it should be connected to people outside the team in order to managed our user and customer expectation.

Let’s meetup!

RSVP here: https://www.eventbrite.com/e/product-tank-jakarta-tickets-37936732789

Yin dan Yang

Tidak ada manusia yang sempurna 100%.

Pasti ada hal baik yang diiringi dengan hal buruk. Dan sebaliknya, ada hal buruk yang diikuti dengan hal baik.

  • Yang tampan/cantik, mungkin akan lebih membuat kita insecure karena punya kecenderungan untuk memikat lawan jenis
  • Yang jelek, mungkin akan lebih setia karena tidak punya pilihan lain
  • Yang setia, mungkin akan lebih protektif
  • Yang cuek, mungkin akan lebih bisa kasih greget dan rasa penasaran, gak hambar
  • Yang sabar, mungkin akan bikin kesel karena ya gitu aja, kaya gak keliatan punya intensi terhadap sesuatu
  • Yang tempramental, mungkin akan sangat berani untuk stand up kalau ada yang mengganggu pasangannya maupun hubungannya
  • Yang suka olahraga, mungkin akan keliatan lebih dekil, apalagi yang suka olahraga outdoor
  • Yang suka musik, mungkin akan menomorduakan pasangannya ketimbang kebiasaan bermusiknya
  • Yang suka baca buku, mungkin akan terlihat sok pintar, padahal memang pengetahuannya luas
  • Yang gak suka musik, olahraga, dan baca buku, mungkin gak menarik orangnya
  • Yang straightforward dan jujur, mungkin omongannya kadang akan suka gak ngenakin
  • Yang suka ngerayu dan berbelit-belit, mungkin gak semua omongannya benar alias “manis di bibir”
  • Yang pintar, mungkin jadi orang yang pembantah, gak mudah percaya sesuatu, bawaannya selalu mau challenge pendapat orang berdasarkan pengetahuan yang dia punya, tapi dia tidak mudah dibohongi
  • Yang bodoh, mungkin akan jauh lebih penurut
  • Yang pekerja keras, mungkin akan jauh lebih bisa diandalkan tapi tidak punya banyak waktu
  • Yang santai, mungkin lebih asik diajak bergaul dan menjalani hubungan tapi bisa jadi gak punya masa depan
  • Yang ambisius, mungkin punya goal untuk dituju, sehingga ia bisa fokus
  • Yang bisa ada setiap saat, mungkin emang karena gak punya kerjaan lain

Sesuatu hadir untuk menjadi penyeimbang sesuatu yang lain layaknya Yin dan Yang. Pilihan untuk melihat dari sisi negatif atau positif, ada di tangan Anda.

Pada akhirnya hidup di dunia bukan untuk menjadi dan mencari kesempurnaan. Tapi bagaimana kita bisa menjadi manusia yang mau bersabar, bersyukur, dan mengimprove diri setiap saat.

Banyak Doa Aja

Finally site ini kembali,

Setelah tempo hari kena hack, direstore, kena hack lagi, restore lagi, kena hack lagi. Entah para hacker-hacker kroco itu seneng banget ngerjain gw.

Padahal:

  1. WordPress udah update terus
  2. Themes udah update terus
  3. Plugin udah update terus
  4. Vaultpress aktif membackup

Mungkin provider host-nya kali yah yang gak secure. Akhirnya cabut deh dari Ne*hoster (sebenernya cs-nya kurang, dulu jaman kuliah taunya ini lalu mager untuk pindah provider).

Ternyata: themes gw disisipin malware, jadi pas Vaultpress nge-restore file gw, balik lagi tuh file yang jadi kunci gerbang mereka ke site ini.

Pelajaran yang bisa diambil:

  1. Tetap lakuin semua “padahal” yang gw lakuin di atas
  2. Once kena hack, baiknya remove all template/themes dan plugin, terus install lagi, jaga-jaga kalau ada malware yang disisipin ke file template/themes dan plugin tersebut, dan ikut ke-backup

Terakhir, banyak doa aja, mungkin lo punya salah sama orang, dan orang itu gak ridho, dan doain yang enggak-enggak misalnya “gw doain blognya mati”.

Scrum Jabodetabek Meetup – Chapter CiKemPon

Dear #scrum enthusiast around Cilandak – Kemang – Pondok Indah – etc,

Let’s join our 1st meetup. This is a community driven meetup, from us, for us, and pure sharing knowledge. For the 1st meetup, Kudo will become our host and sharing will be initiated by Joshua Partogi & M. Ichsan Rahardianto. Next meetup? it can be you (as a speaker), or your office (as a host). You also can bring your own food to share (potluck), etc. For being transparent, we also can vote who will become the next host during the meetup.

Let’s share our knowledge.

Just from us, to us.

RSVP: https://lnkd.in/fmx9mby

Multiple Team and Multiple Project/Product in JIRA

Yesterday, i read a beautiful article from Healthy Team Backlogs.

It’s all about how to make, organize, and manage our product backlog in a beautiful way. Honestly, it’s really helpful. You can implement some practices there. Let’s read that article then experiment it to your team.

But there’s a question from  in his article that quite makes me interested:

Scrum most commonly uses the term product backlog. However, many product owners who are new to Scrum are confused by this term. Reasonable questions arise: Does this suggest that a team working on multiple products would have multiple backlogs? If so, how do we prioritize between them? Where do bugs get recorded? What happens if work needs to be done, but it isn’t associated with a product; do we create a placeholder?

In this article i’m trying to answer that question in a summary. And my answer is: by using JIRA, how?

  • First, let me explain 2 most important entity in JIRA: Project and Board.
    1. Project is group of several backlog that is grouped based on similarity (based on the author purpose).
    – Similarity is subjective. It can be based on team, theme, mission, KPI, etc.
    – Due to support this article purpose, i put project as a group of several backlog that has similarity: contribute to one product.

    Project not associated with board

    2. Board is place to visualize our project.

    Project that visualized by the board (DEMO board)

    – Relation between Project and Board is many to many (m-n), so: one project is able to connect with several boards, several project are able to connect with one board, etc. (i’ll explain about this later, let’s continue!).

  • Second, let’s create 2 different project that represent 2 different product.
    – In this example, i created DEMO-1 and DEMO-2, let’s assume DEMO-1 & DEMO-2 are different product that our (full) tech-product team working on.

    Example of project

  • Third, create several backlog for each project.
    – To make it more likely a real backlog, we can put an epic to represent every each product (represent by project) has prioritized epic.

    Project DEMO-1, please do the same to DEMO-2

Then, let’s answer ‘s question one by one..

  • Does this suggest that a team working on multiple products would have multiple backlogs?
    Yes, multiple product can be represented by multiple project in JIRA. In this example: DEMO-1 and DEMO-2.
  • How do we prioritize between them?
    By using filter on the board:
    – Let’s create 1 board that visualized our team board. In this example, i named the team as “DEMO”. So, i create “DEMO Team”.

    Create a board

    – Choose what’s project source of the board that we want to visualized. In this example, we choose “based on an existing project” since we already have the project (DEMO-1 & DEMO-2).

    Choose the source of the board

    – Put board name as DEMO Team (our team name) then put DEMO-1 & DEMO-2 as our combination of 2 project (product) that we want to visualized.

    Let’s name the board!

    Ta da! we’ll see board that contain both product backlog (from 2 different product) that we will be working on!

    Let’s prioritized!

    So, currently we’re able to prioritized between this combination of product backlog.

    Then, how to differentiate between which one is backlog from DEMO-1 and DEMO-2?
    – Actually each project has a key that you can setup when you created a new project. In this example, i put “DEMO1” as a key for backlog from DEMO-1 and “DEMO2” as a key for backlog from DEMO-2.

    Setup a key for every project

    DEMO1 & DEMO2

  • Where do bugs get recorded?
    Before answer this question, i assume when the bugs is coming we easily to define the bug is coming from which product. So, for example the bug is coming from product DEMO-1. Then, yeah we just create a new bug that tight to DEMO-1 project.

    Create [BUG] DEMO G

    Board will also showing combination of each product (project) bug on the backlog, similar with the other backlog. Then, we are also able to set the bug priority and prioritize it along with the other backlog.

    Let’s prioritize the bug!

Finished!

Hope this article will help you to setup your JIRA for your team. I’ll share how HappyFresh tech-product team process in bug handling in the different article.

Here’s Atlassian documentation if you want to learn more.

See you!