I am the CTO of a small company I helped start and one of the more experienced developers there. I would like to have the benefits of a self-organizing team, but a couple people on the team have told me they'd like me to attend their standup meetings and contribute to technical decisions. Does Scrum prohibit this?
Posted on October 21, by Bryce Lynch This will be long. I beg your understanding for my verbosity hypocrisy; this is the product of four years work. I have now reviewed every adventure in every print issue of Dungeon Magazine.
I started in August ofafter spending several months locating issues. It was a herculean effort and, several times, it broke me. Or maybe you do. I did every fantasy adventure and most of the sci-fi ones.
I generally reviewed them Wednesday, Thursday, and Fridays, taking notes and then writing the review on Saturday for posting the next Saturday morning on my review website tenfootpole. I have review standards and strong beliefs on what makes a good adventure.
First and foremost it has to be useful to the DM at the table while they running it. You can use it as inspiration, steal parts from it, or use it as a doorstop if you want, but, judged as an adventure, it has to be useful at the table.
My standards are VERY high. A large part of being useful at the table is a writing style that allows the DM to scan the text quickly during play and locate information.
The characters walk in to a room and the DM must quickly, in just seconds, locate the description, grok it, and relate it to the players.
Then as they react the DM must continue scanning and absorbing to react to their actions as guided by the DM text for the room. After this, we come to creativity, interesting encounters, and all the rest.
But first, it has to be useful to the DM at the table. Dungeon Magazine is an abject failure in this regard. Mountains of backstory, mountains of room text. All of it fights the DM running it at the table.
If you are including something in the main text then it has to be directly useful for play. It reveled in useless detail.
I also empathize with their jobs, having to wade through garbage day after day. While my task was voluntary they had the extra pressure of mortgages and kids to raise. As far as genres, the Oriental Adventures pieces were generally good, especially the earlier ones.
But as folklore-heavy adventure with talking animals and relatable situations then they score high. The Adventure Paths in Dungeon Magazine were generally dreadful.
The Mere of Deadmen series, a proto-adventure path, had a couple of decent ideas and adventures before becoming mired in boringness. I generally found the first couple of adventures in the series interesting, and an occasional idea in later issues.
The trek through the jungle after a shipwreck in Tides had some nice set pieces. There was also a great diplomacy idea with demon lords in the same series. Too much gimping of the characters abilities to force them in to what is, essentially, a low level adventure design.
Ah, the linear adventure.
Usually with set pieces. The long stat blocks and attempts to build reason in to a dungeon via rules … A magic mouth says a key word that dispels a contingency that holds a stasis that summons a monster.
TOlerates maybe, but prefer? The early adventures tend to be more creative and have more elements to steal. As the issues count up, especially after issuethe designs become more linear and more focused on stat blocks. Some are even good. In a stunning coincidence, it has come out to ten. It just turned out that way.
Thelist will also show the depths of my hypocrisy.In the social sciences and life sciences, a case study is a research method involving an up-close, in-depth, and detailed examination of a subject of study (the case), as well as its related contextual conditions..
Case studies can be produced by following a formal research method. These case studies are likely to appear in formal research venues, as journals and professional conferences. The style of a case report and a case series.
A useful definition of a case report that we have found in the literature was “a description of clincial events of one or several patients in a narrative form”.
27 This, by surface validity, is similar to the patient's medical report. Each patient will have his/her own medical report which is written in a seperate section.
Jan 03, · Case series are a commonly reported study design, but the label "case series" is used inconsistently and sometimes incorrectly.
Mislabeling impairs the appropriate indexing and sorting of evidence. This article tries to clarify the concept of case series and proposes a way to distinguish them from cohort studies.
In some regards, graph databases are like the next generation of relational databases, but with first class support for “relationships,” or those implicit connections indicated via . A case series (also known as a clinical series) is a type of medical research study that tracks subjects with a known exposure, such as patients who have received a similar treatment, or examines their medical records for exposure and outcome.
Phenomenal write up. This must have been a daunting task to say the least. I haven’t played D&D in a while but I’m hooked man. I’d love to try Depths of Rage and The Spottle Parlor.