#Scrum debate

[dreamzghostz]

SCRUM DEBATE 1#!

(Left) Sayaka, Byakuya, Nagito, Mahiru, Sonia, Shuichi, and Kirumi

"Gundham attacked first!"

(Right) Celestia, Chiaki, Hajime, Mikan, Kaede, Rantaro, Kiibo, and Korekiyo

"Gundham was innocent!"

CELESTIA, CHIAKI, HAJIME, MIKAN, KAEDE, RANTARO, KIIBO, AND KOREKIYO'S TEAM WINS

"THIS IS OUR ANSWER!"

BREAK!

[hexapustapes]

Old colored sketch art, danganronpa gbd bootleg scrum debate They are drawn from memory so i cannot ensure they are on model

[blondesillyboylover]

Mutuals, komahina vs saiouma

[spookberry]

Shhhh theyre thinking

[flamingredanon]

Happy Halloween, have a vampire!

[accirax]

DRDT vs. The Scrum Debate

Greetings party people (<- DRDT fan community). By complete accident, I wound up writing some analysis addressing DRDT's Chapter 1 Scrum Debate and what it might mean for the future of Chapter 2. Although it can no longer be used in the exact context for which I originally wrote it, there were still some interesting things to note, so I thought I'd share.

So, here's the question I'll pose: whenever DRDT's Chapter 2 Scrum Debate eventually appears, can we deduce who the killer is by which side of the Scrum Debate they're on? (DRDT spoilers, obviously, as well as V3 spoilers.)

Let's start out with the facts of DRDT so far. I'll recap the Scrum Debate using this formatting: the person listed first is the one who speaks first, on the team opposite the protagonist. The person listed after the arrow (->) is the person who countered them from the protagonist's team. The team whose opinion is proven correct by the end of the Trial will have their names in green, while the incorrect team will be listed in red. The killer is bolded. The protagonist is underlined. The protagonist's side always wins, so I'm not additionally marking that in any special way. I'll list anyone who doesn't talk at the bottom, and cross their name out (name) if they're dead.

DRDT Chapter 1 Scrum Debate

Question: Is Teruko the culprit? (yes/no) J -> Nico David -> Whit Veronika -> Rose Levi -> Ace Hu -> Eden Arei -> Arturo Min -> Teruko No lines: Xander, Charles

In this case, Xander didn't speak in the Scrum Debate (because he's dead) and neither did Charles (because he was having a mental breakdown). As it stands so far in DRDT, the "pattern" is that the killer, Min, spoke and was on the team opposite from Teruko. She was countered by Teruko herself, even!

Therefore, you could say that "the killer will be someone who argues on the opposite side of the protagonist, and possibly even whoever is countered by Teruko. If your killer pick winds up on Teruko's team, it's bad news for you."

However, it's hard to find a pattern in only one example. Now, we'll see if those assumptions hold true when compared to the OG of Scrum Debates, the canonical Danganronpa V3: Killing Harmony.

V3 Chapter 1 Scrum Debate

Question: Is Shuichi the culprit? (yes/no) Kiyo -> Gonta Miu -> Kaito Maki -> Kirumi Ryoma -> Kiibo Kokichi -> Kaede No lines: Rantaro, Angie, Tenko, Tsumugi, Himiko, Shuichi (^ Unlike what's been shown in DRDT so far, in V3, characters' death portraits are assigned to a side of the Scrum Debate. That is what these colors note for Rantaro right now, and other dead students below.)

V3 Chapter 2 Scrum Debate

Question: When was the body put in the piranha tank? (in the morning/at night) Tsumugi -> Angie Kiyo -> Himiko Miu -> Kaito Kokichi -> Shuichi Gonta -> Maki Kirumi -> Tenko No lines: Rantaro, Kaede, Ryoma, Kiibo

V3 Chapter 3 Scrum Debate

Question: [Should we] Vote for Korekiyo [now, or discuss it further]? (vote now/discuss further)* Himiko -> Kiibo Miu -> Shuichi Kaito -> Kiyo Gonta -> Kokichi Maki -> Kiyo Tsumugi -> Shuichi No lines: Rantaro, Kaede, Ryoma, Kirumi, Angie, Tenko (*Although the team that said vote for Kiyo now would have technically been correct, given that he did kill Tenko and Angie, it's generally good practice to discuss every piece of evidence in a Class Trial in case something strange comes up last minute. Thus, I will call the team that said they should discuss further correct. If you disagree with this verdict, just flip the colors in your mind.)

V3 Chapter 4 Scrum Debate

Question: Could Gonta have committed the crime? (no/yes) Kaito -> Shuichi Tsumugi -> Kokichi Maki -> Kiibo Kaito -> Shuichi Kaito -> Kokichi Himiko -> Kiibo Gonta -> Shuichi No lines: Rantaro, Kaede, Ryoma, Kirumi, Angie, Tenko, Kiyo, Miu

V3 Chapter 5 Scrum Debate

Question: Which one is dead? (Kokichi/Kaito) Kiibo -> Shuichi Himiko -> Maki Tsumugi -> Maki Kiibo -> Shuichi Himiko -> Maki Tsumugi -> Shuichi No lines: Rantaro, Kaede, Ryoma, Kirumi, Angie, Tenko, Kiyo, Miu, Gonta, Kokichi, Kaito

Oof, my man Ryoma cannot catch a break. And Miu is only correct once she's dead; that's pretty funny.

Now, let's answer some questions! As established by v3...

Does the blackened have to be on the opposite team from the protagonist? No, Kiyo argued on Shuichi's side in Ch3!

Does the blackened have to be countered by the protagonist in their Class Trial? No, Kirumi, Kiyo, and Kaito were never countered by Shuichi!

Is the blackened always on the incorrect side of the Scrum Debate? No, Kaede, Kiyo*, and Kaito answered correctly!

Does the blackened have to speak in the Class Trial? No, Kaito didn't say anything, as himself or as Kokichi!

(Granted, Kaito not speaking was a very special circumstances that will in all likelihood never apply to DRDT, much less in this Class Trial. And, of course, Kaede wasn't countered by the protagonist either, but given that she was the protagonist at the time, that would have been basically impossible.)

With these answers, I think we can confirm that, in general, you cannot determine who the killer of a given Trial is based on where they're placed in the Scrum Debate. As established by V3, they can talk on the side of the protagonist, talk against the protagonist, or not talk at all, and they can still be the killer. It makes sense that it would be this way, or else you could start calling the killer as early as the first episode of the Trial, depending on the Scrum Debate's placement.

However, that's not to say that you can never infer things from the evidence you're given. In a well written Class Trial (which DRDT has, in my opinion), a killer is always looking to support their end goals in subtle ways. In V3, all of the killers acted in the way that made the most sense to them based on the question asked: Kaede wanted to protect Shuichi and everyone else, Kirumi wanted others to think the truth of the murder was impossible, Kiyo wanted to extend the Trial to evade a guilty verdict, Gonta genuinely believed he was innocent, and Kaito didn't tip the scales by commenting on one side or another. Of course, that begs the question: what will DRDT's Scrum Debate be about?

Personally, I think it will be about whether Arei met with the killer at 7:30 PM or 7:30 AM, and will happen almost immediately once episodes resume. Thus, in that specific scenario, I find it likely that DRDT Chapter 2's killer will once again be on the team opposite Teruko. Presumably, the killer would want to argue that the time was 7:30 PM, because they likely left AM or PM off of the note intentionally because they had an alibi at night. If we assume that Teruko would side with Charles in saying that the time was 7:30 AM, playing into her feeling that something about David being the blackened is wrong, then that would put her on the (likely correct) AM team, opposite the killer.

An interesting side note about this theory for the Scrum Debate's subject is that it's really similar to V3's Chapter 2 Scrum Debate question. V3 Ch2 asked whether Ryoma's body was placed in the Gym in the morning or at night, and DRDT's may ask if Arei's body was put in the Playground in the morning or at night. Similarly, "is Shuichi the culprit" and "is Teruko the culprit" are almost identical questions, down to the person suspected being the innocent eventual protagonist who was only put into this precarious position by their trigger-happy bestie.

If this pattern holds up, we might expect DRDT's subsequent Scrum Debates to ask us whether we should make an impulsive or cautious decision, something about someone's personality as it pertains to the crime, and which of two people is dead/the culprit. Does that information get anyone theorizing? I certainly think it's interesting idea.

Well, whatever happens, I'm sure we'll have lots to talk about once Episode 12 does eventually dropped. Thanks for checking this out, and hopefully I can post more properly planned DRDT content soon.

[sourscratched]

requested by @incorrect-play-it-by-ear: compilation of all the play it by ear end credit moments in season 2; many little dances and bops to be had

[rubberduckyrye]

So me and Celest are having a disagreement--

[ahogedetective]

"Kaz... I want to feel bad for you, but you kind of brought this on yourself. ...I still hope you'll be okay, though. ....And that you did not plan on being a father in the future...."

[the-kiss-of-wet-asphalt]

I think it's that time in the decade where we talk about how hard Danganronpa OST actually fucking hit. Like they go so fucking unapologetically over the top. They're HARD and that's the rule

And also they're so recognizable. I can say with zero shame that i'm certain they're comparable to Undertale OST in this regard

[spectershaped]

So, one fun tidbit in Petal Crash I noticed is that, barring a handful of CGs and the sprites in the matches, each character has only one "dialogue sprite" so it needs to be decently versatile. This is something I've noticed in the MMBN games before - I think there's skill to creating a default sprite that is characterful but also slightly unfathomable so it doesn't clash with the emotional tone of most scenes (granted, PCrash isn't exactly a story with extreme stakes, which helps)

[jonquilyst]

My sims' takes on this debate

Megyn: "I don't think cereal's a soup, but the only reason why I think that is because I've just always considered it to be its own thing. I think soup has to be cooked anyway."

Eva: "Cereal's a soup! It might be cold, but it has a liquid base, complementary solid pieces, and you eat it with a spoon. Just because it's not hot doesn't mean it isn't a soup!"

Jayden: "I think cereal can definitely be a soup. The first thing that comes to my mind when I think of soup is "liquid plus any solid stuff within in that you eat with a spoon." Cereal is just that."

Wyatt: "Culinary-wise, cereal isn't a soup. It's just a breakfast food that happens to be similar to soup when you pour milk over it. You can eat cereal plain or use it in recipes, like if you're using corn flakes for chicken. You can't really do that with actual soups."

📩 Simblr question of the day: Your sim is having a heated discussion with someone about whether Cereal is a soup or not, what side are they on? 👀

answer in whatever way is most comfortable for you and feel free to share this SQOTD around, make sure to use the hashtag SQOTD and tag me in separate posts ~ 💛

[iliketrainsandstars]

I think the danganronpa fandom needs to take over this new event in hsr because i can't do this 😭

[rachaelwilterdink]

More Great Agile Debates, Part 1

My previous presentations and blogs on "Great Agile Debates" have proven extremely popular, so I thought I would add to this body of knowledge with a new blog series. In each blog, I will cover five more great agile debates for your consideration. Keep in mind that my opinions are my own, and not necessarily those of any other organization I am affiliated with. I'd also love to hear what you think, so don't be shy - leave some comments, and let's debate! Here are the first five topics of debate about agile I will cover: - The Developers are a Sub-team in Scrum - The Three Questions are Required - A Product Goal is Not Required - Backlog Refinement is an Official Scrum Event - Teams Cannot Combine Different Agile Elements

The Developers are a Sub-team in Scrum

This is now FALSE! In previous versions of The Scrum Guide, the Developers were considered a sub-team within a Scrum Team, but in the 2020 update to the guide, this concept was removed. The point of this change was to ensure that the team is a cohesive whole – without having a team within a team. The former Dev Team concept created an “us versus them” attitude between the Developers, the Scrum Master, and the Product Owner. Going forward as one united team, many things that were once in the domain of the Dev Team are now jointly owned responsibilities among the entire Scrum Team.

Further, having everyone on the Scrum Team on equal footing as team members allows people to collaborate and build trust more easily. Everyone on the team should be “in the know” on what’s happening, without any surprises from the separateness of having a sub-team.

The Three Questions are Required

This, too, is now FALSE! In the previous versions of The Scrum Guide, the three questions were, in fact, the prescribed format for running the Daily Scrum. As a reminder, the questions were: - What did I do yesterday that helped the Development Team meet the Sprint Goal? - What will I do today to help the Development Team meet the Sprint Goal? - Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal? The creators of the guide realized that requiring the answers to these three questions was far too prescriptive. Their goal was to simplify the framework. Many Scrum Teams had already stopped using the three questions because it felt rote and repetitive. Answering these questions didn’t really give the team the real opportunity to figure out their collective plan for the day toward accomplishing the Sprint Goal.

I myself had already stopped using this format on my Scrum Team. A far better exercise is to “walk the board” – going through your Sprint Backlog and looking at each item (either by person or from top to bottom) and its progress. Having this visual also helps to identify if there are any impediments, whether some team members are overloaded while others might not have much to do. There are other options, as well. The main idea is that you can choose the format that works best for your team in your context. Some teams prefer to post on a collaboration channel like Slack or Teams, while others simply go round robin verbally, without focusing on what has already happened – rather, looking forward to what needs to be accomplished today.

A Product Goal is Not Required

You guessed it – WRONG! A Product Goal is now required. Prior versions of The Scrum Guide did not include this concept. In the absence of this as a requirement of Scrum, many teams and Product Owners introduced their own idea to fill the void: Product Vision. Some people might argue that there is little difference between a vision and a goal. I struggle with this myself, especially having trained many Product Owners and helped them craft Product Vision Statements.

In training new Product Owners, I now feel obligated to include the Product Goal as it is now an official aspect of Scrum. The way I see it, these can be two separate things. The vision is the aspirational description of what the product is and how it is beneficial, which is strategic in nature. On the other hand, the Product Goal (or goals) is more tactical, with specific measurable objectives similar to SMART goals. These provide more direction on what is needed to achieve the vision.

Backlog Refinement is an Official Scrum Event

Sorry, folks! This one isn’t true, either (at least not yet). While The Scrum Guide infers that Backlog Refinement is an important, ongoing activity, it’s not an officially recognized Scrum event. Personally, I would like to see this added as an “official” requirement of the Scrum Framework. To be successful in any type of endeavor using Scrum, whether project- or product-based, having a properly managed Product Backlog is essential.

Many teams only do this activity on an ad-hoc basis, which is inconsistent and unpredictable. I prefer to have this activity, if running two-week sprints, on the opposite day from the Sprint Review. This ensures that Backlog Refinement actually happens regularly. I would also suggest a timebox similar to that of the Sprint Planning event. These events are very similar, but Backlog Refinement is a preliminary opportunity for the team to review and discuss upcoming stories, answer any open questions, and gain a shared understanding of each item. The team can also use this session to size the stories. Having done this work in advance also speeds up Sprint Planning.

Teams Cannot Combine Different Agile Elements

Once more, FALSE! There is no rule written that people cannot combine different aspects of various agile practices. Most Scrum Teams also use Kanban boards, and other concepts borrowed from lean, XP, or other agile frameworks. Scrum alone isn’t always sufficient to create all products or solve all business problems. Support teams, for example, would be much better suited toward sticking with Kanban, but may also use Scrum activities such as periodic retrospectives to look for improvement opportunities. Likewise, traditionally run projects (aka waterfall), can also benefit from inserting some agile ideas into their projects. They too may have more frequent retrospectives, rather than end-of-project Lessons Learned (when it’s too late to do anything about it).

For teams that want to avoid full-blown scaling, they might simply take from the Nexus scaling framework (or others) to achieve some parts of scaled agile, without adding too much additional overhead and cost. The Project Management Institute also offers a certification in Disciplined Agile, which I would call a compilation of all kinds of agile ideas, that can be combined in whatever fashion makes sense and works for your team.

Wrapping it Up

Thank you for reading! This is just the beginning of many more great agile debates, so come back often! And, if you have an alternate opinion, I would love to hear it - please post in the comments below! Read the full article

[eggs-can-draw]

komaeda anon: HAHAHAHA YOU REACHED IT, DO YOU SEE WHY I WAS SO EXCITED ONAOFKSKGKEH

scrum debates would not work on komaeda bc his podium will fall at one point 😭😭

YES HOLY FUCK ITS SO COOL DIOS MIO ok but also the image of everyone having to stop and help him back on is hilarious

[pppuri]

debate scrum START!