Newsfeeds

Term reference change

New Drupal Modules - 12 December 2017 - 2:14am

Term reference change is an API module that provides functionality for modules that need to change term references in bulk. It provides no user interface or user facing functionality and should only be installed if another module depends on it.

Categories: Drupal

Amazee Labs: Defining work - Amazee Agile Agency Survey Results - Part 6

Planet Drupal - 12 December 2017 - 1:50am
Defining work - Amazee Agile Agency Survey Results - Part 6

This is part 6 of our series processing the results of the Amazee Agile Agency Survey. Previously I wrote about team communication & process. This time let’s focus on defining work. Who is involved in defining work and which tools are essential for organising your work?

Josef Dabernig Tue, 12/12/2017 - 10:50 Defining work

When asked about who is involved in defining work, we asked about which roles would be included in different phases of the ticket process.

  • “Creating tickets” is performed by these roles ordered by a number of selections: “PM / PO Proxy”, “Any Developer”, “Lead Developer”, “Client / Product Owner”, “UX/Design” and finally “The entire team together”.

  • “Refining/grooming/specifying tickets” is performed mostly by “Lead Developer”, “Any Developer” and “PM / PO Proxy” rated equally high, then “Client / Product Owner” and “The entire team together” rated equally high and finally “UX/Design”.

  • “Estimating tickets” is done by “The entire team together” followed by “Lead Developer” or “Any Developer” rated equally often, then “UX/Design”, “Client / Product Owner” and finally “PM / PO Proxy.”

It looks like there is an apparent tendency for Developers or Lead Developers to be involved in all parts of defining the work. It also makes sense that Clients / Product Owners or the internal counterparts in the agency PM / PO Proxies do participate in defining the work but don’t participate in estimating.

For us at Amazee, having the entire team estimate is essential to make sure there is common knowledge about the problem space and that we can get multiple views to validate our understanding of the client’s requirements. Any of our developers can take a leadership position in a particular project, that person would then be tasked to specify tickets together with the Project Owner (PO) or the client directly, and get estimated by the team later on.

Survey contestants also shared some additional insights about defining work/tickets. I’d like to quote a few of them.

"We have in each team an estimation engineer, scrum master and an architect. Everyone is responsible for doing architectures and estimations, bit the QA goes through these roles. The scrum master is responsible for the 2 weekly process while also being part of the development team."

"Involvement across ticket lifespan evolves as project matures."

"Being the most verbose possible."

"You have not mentioned Acceptance Criteria. This is written in collaboration between our QA and Stakeholders client side, ideally the product owner."

"Again - depending on the project/the client and the PM. We had clients that created and defined tickets together with the PO at our side, so that they could be specified during planning and then estimated by the devs. Sometimes PM is doing it, and sometimes this is done by the lead dev (if PM/PO isn't able to do it). Estimation depends a bit on the time pressure and the team size. If possible we estimate with the whole team. But sometimes we only have the lead dev and the dev who is going to implement the feature estimate."

Organizing work 

We also asked which tools were how important when it comes to organizing work. As shown in the illustration above, the ones that had the most apparent tendency towards their importance were “Sprints”, “User stories”, “Acceptance criteria” and “Tasks”, whereas the graph looks more indifferent when it comes to “Epics”, “Definition of Done”, “Definition of Ready” and “Releases/Versions”.

For us at Amazee, two-week sprints are a crucial instrument for planning and deciding about the priorities of our work. We don’t use User Stories all the time but feel like they are a good way of allowing clients to explain their requirements to the team effectively. Acceptance criteria (AC) are a must for anything that the team will implement - this can be on the user story level or the task level. Our teams also follow a definition of done to make sure that everything is in the right place when it comes to browser testing or on which environment results should be available. Recently, we started using Epics to group requirements that we had earlier on put into components in Jira. This allows to easily track the progress per Epic which is a neat feature in Jira. Releases/Versions aren’t used too much in the teams I work with.

How do you define your work? Please leave us a comment below. If you are interested in Agile Scrum training, don’t hesitate to contact us.

Stay tuned for the next post where we’ll look at estimations.

   
Categories: Drupal

Altering Entity Routes

New Drupal Modules - 12 December 2017 - 1:07am

The Altering Entity Routes is based on Entity Construction Kit (ECK) . It can alter routes of entities created by eck.
As we know,the Entity Construction Kit (ECK) builds upon the entity system to create a flexible and extensible data modeling system both with a UI for site builders, and with useful abstractions (classes, plugins, etc) to help developers use entities with ease.

Categories: Drupal

Business of Gaming Retail: MAPs

RPGNet - 12 December 2017 - 12:00am
Why we like them.
Categories: Game Theory & Design

Tarot Adventures, Book Two: Comet Over Echo Rock Kickstarter Coming in January

Tabletop Gaming News - 11 December 2017 - 3:00pm
Sinopa Publishing has announced their next book in their Tarot Adventures line. The series, which draws its inspiration from the traditional Tarot deck, continues to the Comet Over Echo Rock adventure. As you all know, I’m a fan of pre-made adventures, as it gives the GM a lot of tools right at their fingertips. And […]
Categories: Game Theory & Design

SCSS Field

New Drupal Modules - 11 December 2017 - 2:12pm

Provides a 'SCSS' field type. Developers and site maintainers can enter SSCS code ("indented" SASS code is currently unsupported) into the field, and it will be compiled to CSS and attached to the page wherever the entity is displayed.

It is possible to "scope" the SCSS/CSS to the parent entity such that any CSS rules therein only apply to that entity.

This module is under active development and is not, by any means, ready for production use.

Categories: Drupal

The Campaigner Issue 22 Now Available

Tabletop Gaming News - 11 December 2017 - 2:00pm
When snowed in and unable to go out and hang with friends, you might find yourself getting a bit stir crazy. Well, a way to keep those shakes away is to grab a gaming magazine. In this case, you can grab a copy of Issue 22 of The Campaigner, as it’s available now. Downloading a […]
Categories: Game Theory & Design

Accelerate Drupal 8 by funding a Core Committer

Dries Buytaert - 11 December 2017 - 1:15pm

We have ambitious goals for Drupal 8, including new core features such as Workspaces (content staging) and Layout Builder (drag-and-drop blocks), completing efforts such as the Migration path and Media in core, automated upgrades, and adoption of a JavaScript framework.

I met with several of the coordinators behind these initiatives. Across the board, they identified the need for faster feedback from Core Committers, citing that a lack of Committer time was often a barrier to the initiative's progress.

We have worked hard to scale the Core Committer Team. When Drupal 8 began, it was just catch and myself. Over time, we added additional Core Committers, and the team is now up to 13 members. We also added the concept of Maintainer roles to create more specialization and focus, which has increased our velocity as well.

I recently challenged the Core Committer Team and asked them what it would take to double their efficiency (and improve the velocity of all other core contributors and core initiatives). The answer was often straightforward; more time in the day to focus on reviewing and committing patches.

Most don't have funding for their work as Core Committers. It's something they take on part-time or as volunteers, and it often involves having to make trade-offs regarding paying work or family.

Of the 13 members of the Core Committer Team, three people noted that funding could make a big difference in their ability to contribute to Drupal 8, and could therefore help them empower others:

  • Lauri 'lauriii' Eskola, Front-end Framework Manager — Lauri is deeply involved with both the Out-of-the-Box Experience and the JavaScript Framework initiatives. In his role as front-end framework manager, he also reviews and unblocks patches that touch CSS/JS/HTML, which is key to many of the user-facing features in Drupal 8.5's roadmap.
  • Francesco 'plach' Placella, Framework Manager — Francesco has extensive experience in the Entity API and multilingual initiatives, making him an ideal reviewer for initiatives that touch lots of moving parts such as API-First and Workflow. Francesco was also a regular go-to for the Drupal 8 Accelerate program due to his ability to dig in on almost any problem.
  • Roy 'yoroy' Scholten, Product Manager — Roy has been involved in UX and Design for Drupal since the Drupal 5 days. Roy's insights into usability best practices and support and mentoring for developers is invaluable on the core team. He would love to spend more time doing those things, ideally supported by a multitude of companies each contributing a little, rather than just one.

Funding a Core Committer is one of the most high-impact ways you can contribute to Drupal. If you're interested in funding one or more of these amazing contributors, please contact me and I'll get you in touch with them.

Note that there is also ongoing discussion in Drupal.org's issue queue about how to expose funding opportunities for all contributors on Drupal.org.

Categories: Drupal

Dries Buytaert: Accelerate Drupal 8 by funding a Core Committer

Planet Drupal - 11 December 2017 - 1:15pm

We have ambitious goals for Drupal 8, including new core features such as Workspaces (content staging) and Layout Builder (drag-and-drop blocks), completing efforts such as the Migration path and Media in core, automated upgrades, and adoption of a JavaScript framework.

I met with several of the coordinators behind these initiatives. Across the board, they identified the need for faster feedback from Core Committers, citing that a lack of committer time was often a barrier to the initiative's progress.

We have worked hard to scale the Core Committer Team. When Drupal 8 began, it was just catch and myself. Over time, we added additional committers, and the team is now up to 13 members. We also added the concept of Maintainer roles to create more specialization and focus, which has increased our velocity as well.

I recently challenged the Core Committer Team and asked them what it would take to double their efficiency (and improve the velocity of all other core contributors and core initiatives). The answer was often straightforward; more time in the day to focus on reviewing and committing patches.

Most committers don't have funding for their work as Core Committers. It's something they take on part-time or as volunteers, and it often involves having to make trade-offs regarding paying work or family.

Of the 13 members of the Core Committer Team, three people noted that funding could make a big difference in their ability to contribute to Drupal 8, and could therefore help them empower others:

  • Lauri 'lauriii' Eskola, Front-end Framework Manager — Lauri is deeply involved with both the Out-of-the-Box Experience and the JavaScript Framework initiatives. In his role as front-end framework manager, he also reviews and unblocks patches that touch CSS/JS/HTML, which is key to many of the user-facing features in Drupal 8.5's roadmap.
  • Francesco 'plach' Placella, Framework Manager — Francesco has extensive experience in the Entity API and multilingual initiatives, making him an ideal reviewer for initiatives that touch lots of moving parts such as API-First and Workflow. Francesco was also a regular go-to for the Drupal 8 Accelerate program due to his ability to dig in on almost any problem.
  • Roy 'yoroy' Scholten, Product Manager — Roy has been involved in UX and Design for Drupal since the Drupal 5 days. Roy's insights into usability best practices and support and mentoring for developers is invaluable on the core team. He would love to spend more time doing those things, ideally supported by a multitude of companies each contributing a little, rather than just one.

Funding a Core Committer is one of the most high-impact ways you can contribute to Drupal. If you're interested in funding one or more of these amazing contributors, please contact me and I'll get you in touch with them.

Note that there is also ongoing discussion in Drupal.org's issue queue about how to expose funding opportunities for all contributors on Drupal.org.

Categories: Drupal

Latest Kensei/Torii Releases Available From Zenit Miniatures

Tabletop Gaming News - 11 December 2017 - 1:00pm
You know, most people associate October with the undead, but December certainly has a lot of ghosts as well. The cold can certainly feel like it’s sucking the life out of you. I can’t say that it’s what happened to all these undead units that are now available for Kensei from Zenit Miniatures, but still, […]
Categories: Game Theory & Design

Fantasy Flight Previews Red Cards From Legacies Expansion for Star Wars: Destiny

Tabletop Gaming News - 11 December 2017 - 12:00pm
The red cards in Star Wars: Destiny represent those characters, abilities, and equipment that’s all about warfare. They’re the professional soldiers, vehicles, and weapons that are on the lines when it comes to blasters blazing. The Legacies expansion will bring players new red card options for their decks, from new characters to new things to […]
Categories: Game Theory & Design

Isovera Ideas & Insights: Did You Say Taxonomy or Content Type? [NEDCamp 2017]

Planet Drupal - 11 December 2017 - 11:24am
Disseminating the difference between content and taxonomy, "Did you say taxonomy or content type?" was presented at NEDCamp 2017.
Categories: Drupal

Wyrd Posts Monday Through The Breach Preview

Tabletop Gaming News - 11 December 2017 - 11:01am
You know, with Wyrd posting up a regular preview on Mondays, it’s not such a bad day after all. It could certainly be worse, is what I’m saying. This time around, it’s another look at Above the Law for Through the Breach. Check out the Witchling Handler. From the post: Witchling Handlers are an advanced […]
Categories: Game Theory & Design

Monday Terrain Corner

Tabletop Gaming News - 11 December 2017 - 11:00am
I survived the Snowpocalypse here in Atlanta. And I’m one of the lucky ones that never lost power (for more than just a flicker, anyway). I’ve got some friends that are still without. Hopefully they’ll get it back soon. And I hope all of you had a chance to enjoy the winter wonderland (if it […]
Categories: Game Theory & Design

Redfin Solutions: Controlling Facebook Preview Images with the Metatag Module

Planet Drupal - 11 December 2017 - 10:56am
Controlling Facebook Preview Images with the Metatag Module

Have you ever posted a link to facebook and wondered where the image comes from in the post preview? Ever wondered if this image is even correct or relevant to what you are posting?

Brett December 11, 2017
Categories: Drupal

Metal Toad: Sluggish Drupal 8 Adoption Lags Even D6

Planet Drupal - 11 December 2017 - 10:49am
Sluggish Drupal 8 Adoption Lags Even D6 Metal Toad Mon, 12/11/2017 - 18:49

We're just past the second anniversary of 8.0.0. To see how D8 is doing compared to prior releases, we put together the chart above, based on Drupal's usage stats page.

For versions 5.x, 6.x, and 7.x, each new release brought dramatically accelerated growth.

Comparatively, D8 has dropped off a cliff. Adoption is far below that of D7, and even behind D6.

Categories: Drupal

Google analytics server triggered events

New Drupal Modules - 11 December 2017 - 10:19am

Ever wanted to trigger a google analytics event when something happens server side? Like a node was saved, a user created or maybe a purchase completed? This module enables you to do that.

Categories: Drupal

Skirmisher Publishing Releases Coldblooded: A Player’s Guide to Lizardmen

Tabletop Gaming News - 11 December 2017 - 10:00am
While there’s certainly nothing wrong with playing a character in an RPG that’s an elf or a dwarf or a human or a halfling, but, for me, I always liked getting a bit more creative with it. Minotaurs, goliaths, and such like that. Well, if you want something a bit more scaly, Skirmisher Publishing has […]
Categories: Game Theory & Design

Dream Pod 9 Running New Heavy Gear Blitz! Kickstarter

Tabletop Gaming News - 11 December 2017 - 9:00am
Giant robot alert! We have a giant robot alert on the screen! *loud buzzing and beeping while red lights flash* Dream Pod 9 is running a Kickstarter campaign for their giant robot miniatures game, Heavy Gear Blitz!. With the Kickstarter, they’re looking to create new core army miniatures for the Peace River and NuCoal factions. […]
Categories: Game Theory & Design

Pages

Subscribe to As If Productions aggregator