Tag Archives: Indonesia

Design Sprint Meet Scrum – Scrum Jakarta (CiKemPon) 3rd Meetup

Group photo after the meetup

Hello Scrum enthusiast in Cilandak – Kemang – Pondok Indah – (and around) area!
Thank you for those who came to our last meetup. (Thursday, November 23rd 2017)
Thank you also to PT Asuransi Astra Buana (Pak Iwan) for a great venue.

There wasn’t a usual meetup that we had some speakers to shared a talk, we only did an open space. Open space is a session when we discussed everything based on what we want to discussed within the timebox. So, this is how we hold the session:
1. We are divided into 3 different group (each group will be facilitated by someone: Mas Aditya Suryomurtjito from Sepulsa, Mas Tommy Fadillah from Aleph Labs, and me)
2. Every member of the group got opportunity to share the topic that they wanna discussed, used a post it
3. Then we prioritized the topic to being discussed based on vote from member of the group, means the topic that we pick is the topic that still confusing by most of the people
4. Let’s discussed! (don’t forget to keep the timebox!)

Goal of the session: no more confusing on the most topic, and can you guest what is that? it’s basic Scrum. :”)

Yeah, we discussed everything related basic Scrum, it’s okay, there’s always a session to build the mindset first.

Then we discussed about Design Sprint – Scrum.

Myth that usually came up:

1. Design Sprint is sprint that held by product people (designer and PO) and should be held exactly before (Scrum) development sprint

Design Sprint involve everyone whose in charge or interact with the solution, it can be people outside tech and product team, it can be inside (developer). So it’s not only for designer and PO even though PO and designer might take a major role in the session.

Exactly before Scrum sprint? of course no, it’s not a mini waterfall for designer and PO. So, what is the goal of having a Design Sprint? please check next answer..

2. Design sprint is REQUIRED before we start a Scrum sprint, means no Design Sprint == no Scrum sprint

Goal of Design Sprint is to produce high quality backlog. High quality means validated and tested considered human desirability, business viability, and technical feasibility. So, it can help PO in terms of produce the backlog, but is it always required? the answer is: it can help but not always needed. For pretty straight forward solution and more technical feature, having a Design Sprint might overkill.

Then what is required to start a Scrum sprint? of course not always having a Design Sprint before it.
It is Product Backlog and Sprint Goal.

3. Design sprint is held in sprint planning

Remember, how many hours maximum for sprint planning? 4 hours. Then 4 hours for having a design sprint? of course not enough.

4. Additional time needed in design sprint means less time for all member of the team to developed and delivered the feature

Not all member of the team required in Design Sprint. It can be adjusted based on possibility scope of the solution. If it’s probably impacting front end then we can only invite one of front end guy (not all fronties from that team). It’s also applied to stakeholder, if it’s only touch operation issue, no need to involved marketing guy isn’t it?. Be effective!

Then, don’t forget to consider %capacity of the team that probably involved on Design Sprint so we can include it into capacity calculation during a sprint planning.

5. There’s no any other methodology other than design sprint to produce a great product backlog

There’s no silver bullet. :))

Sharing session after open space

Sharing session after open space

Sharing session after open space

So, what is the best way to accommodate Design Sprint into Scrum?

Design Sprint is one of great way in order to produce high quality backlog, which is something that Scrum framework not really told deeper. So, it’s complementary. Just do Design Sprint separately with Scrum sprint so our product backlog pipeline will always filled with a great one. And just do Scrum sprint as usual as long we have list of product backlog and Sprint goal.

Hope those can help. If it’s still confusing? let’s meetup in our next meetup!

Scrum Jakarta (CiKemPon) 3rd Meetup

Scrum Jakarta – Chapter CiKemPon 2nd Meetup

Scrum Jakarta CiKemPon 2nd Meetup

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

After successfully run the 1st meetup, we will have another one!

On our 2nd meetup, we will discuss why Scrum does not work in Indonesia. We will discover all blockers, challenges, etc from those who currently struggling and face the problem every day, with Rudy Rahadian from XL Axiata & Asep Roni Setiawan from Bank Danamon. Recommended for Scrum Master.

There will be an open space to discuss and share what action items, tips, etc that probably helps.

RSVP here: https://www.facebook.com/events/128908987830036/

Host: HappyFresh

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

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!