2. Organisation: ROI, cost per employee, growth, etc
I assume points 1 & 2 are already straightforward, aren’t they?. Then why there’s a point 3??
Maximizing the value of the product will lead to the increasing value of the company or organization, agree?. Then, is the product having the ability to doing self-improvement? of course no. Who can do it? the people behind it. The more knowledge they have, the more chance they can win the competition.
People tend to forget that improving people’s knowledge = increasing the asset of the organization. Increasing the asset of the organization can lead to the increasing value of the company and organization.
So, is your team still afraid to doing a re-write? or moving into the latest technology stack?, of course, we shouldn’t forget to calculate the “investment” (need to explore more about this).
I’m starting to write This Week I Learn (TWIL) in the spirit of continuous improvement. I hope it helps me remember how far I go and get feedback on my thought; even better, it allows you not to be trapped on similar mistakes.
As a #coach, I just realized we often face the unideal situation. Some of our co-workers left the company, and I need to keep the team engaged and continue to run the business.
This week I learn that just supporting the team in this condition with just literally saying “come on guys,” “what can I help,” etc., sounds/feels useless. We need to change our uniform from a coach to an enabler: “so, what should I do?” “how to make this happen?” etc.
It’s a different spirit.
I know there will be a judgment: “No, as a coach, you have to make your team able to do the task by themself (self-organized).”
Yes, I know it. But I think the most important thing, in the beginning, is to fulfill the team’s needs first. Along the way, then we can start to delegate the task one by one.
Just my thought, do you have any other better idea?
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!
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.
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.