3.7.1 CARGO MISSION

Timbur
The Naval Armada Corps

Friends, Traders, and Mercenaries, with the new patch 3.7.1 on the horizon, it's time to prepare for the upcoming cargo mission. Our mission is to push credit generation to its limits through hauling as a coordinated effort. Our vision is to have dozens of traders hauling in the Crusader system working in unison. As traders increase, pirates will also increase and so will the need for vital escort services. Our plan is to support all of these activities through credit and activity generation. For those familiar we’ll be using a framework called Scrum, I’ll provide a short recap of Scrum at the end of this document.

During the next two weeks (after the 3.7.1 patch is released), our plan is to accomplish the following goals:

Get to 1 million aUEC on Day 1 of patch, enough to Haul Laranite
Buy everyone a Caterpillar (or Freelancer Max)
Pay Out Bounties for confirmed Kills on other Caterpillars w/ Laranite
Pay crew daily to everyone involved in daily operations.

Daily Metrics:

  • Report your daily cargo credit balance.
  • Report any incidents or impediments.
  • Report any ships bought in game.
  • Report any confirmed caterpillar kills
  • Did you pay your crew?


At the end of Two weeks:


  • Total number of Caterpillars (and other ships) Earned in Game
  • Total number of daily cargo credit balance reports, and daily average.
  • Number of confirmed caterpillar kills
  • How much was paid out to crew?

A Brief Overview of Scrum:

This is a brief overview on how we’ll use scrum in this cargo hauling mission. 

The Scrum Team: The Scrum Team consists of a Product Owner, the Development Team, and a Scrum Master. Scrum Teams are self-organizing and cross-functional. Self-organizing teams choose how best to accomplish their work, rather than being directed by others outside the team. Cross-functional teams have all competencies needed to accomplish the work without depending on others not part of the team. The team model in Scrum is designed to optimize flexibility, creativity, and productivity. The Scrum Team has proven itself to be increasingly effective for all the earlier stated uses, and any complex work.
Scrum Teams deliver products iteratively and incrementally, maximizing opportunities for feedback. Incremental deliveries of "Done" product ensure a potentially useful version of working product is always available.
  • Self-Organizing, those doing the work choose how best to accomplish the work
  • Cross-functional, teams have all competencies needed to accomplish the work without depending on others not part of the team. 

Product Owner: The Product Owner is responsible for maximizing the value of the product resulting from work of the Development Team. How this is done may vary widely across organizations, Scrum Teams, and individuals. 
  • Timbur will be the Product Owner for this mission
Scrum Master: The Scrum Master is responsible for promoting and supporting Scrum as defined in the Scrum Guide. Scrum Masters do this by helping everyone understand Scrum theory, practices, rules, and values.
The Scrum Master is a servant-leader for the Scrum Team. The Scrum Master helps those outside the Scrum Team understand which of their interactions with the Scrum Team are helpful and which aren’t. The Scrum Master helps everyone change these interactions to maximize the value created by the Scrum Team.
  • Timbur will also act as the Scrum Master for the team unless someone else wants to fill in this role. 

Team Size: Optimal Development Team size is small enough to remain nimble and large enough to complete significant work within a Sprint. Fewer than three Development Team members decrease interaction and results in smaller productivity gains. Smaller Development Teams may encounter skill constraints during the Sprint, causing the Development Team to be unable to deliver a potentially releasable Increment. Having more than nine members requires too much coordination. Large Development Teams generate too much complexity for an empirical process to be useful. The Product Owner and Scrum Master roles are not included in this count unless they are also executing the work of the Sprint Backlog.
  • Teams consist of 3 to 7 people. (+/-2).

SPRINT EVENTS

Sprint Planning: We'll plan out the next two weeks, what items of the backlog can we accomplish?

Daily Scrum:  Report your progress toward the goal, we're looking for two metrics:
  1. Report your cargo balance. Report your progress toward the goal. This is defined as how many credits are you putting into haul cargo. Subtract any expenses for refuel, repair, rearm, outfitting, weapons armor, personal weapons.  Ex. Timbur, 100,000 aUEC. 
  2. Report any incidents or impediments. Is there pirate activity in the area? Did you have any 30k crashes? What's holding you back from getting to the goal?
Sprint Review: We'll review what we've accomplished.
Sprint Retrospective: We'll review what we can do better next time as a team.
Product Backlog: Ordered list of everything that needs to be done.

A Brief Example

A brief example of how this would work in gameplay. Timbur is the Product owner so he assembles a cross-functional self organizing team of 7 people to haul cargo. Timbur is the Cat owner, so he’ll spawn his Drake Caterpillar, he’ll hire a professional caterpillar pilot as his #2, Selwyn_Lindquist. He’ll also hire Rich_Banks as a second caterpillar owner with SQ flying as pilot. El Dio and Time Lord will be escorts, and Dewderonomy will be flying a ship designed to take out any competition.
Let’s review:
  1. Timbur, Cat Owner
  2. Selwyn_Lindquist, Cat Pilot
  3. Rich_Banks, Cat Owner
  4. SQ, Cat Pilot
  5. El_Dio, Escort
  6. Time_Lord, Escort
  7. Dewderonomy, Anti-Caterpillar
In this team we have a self organizing and cross functional team because we have the ability to accomplish the work as needed and they don’t have to rely on anyone outside of the team. We’re not telling the cats where to haul or what commodities to get, we have a second caterpillar who can also run a separate route, we have three escorts who can decide if it’s better to guard the caterpillars in one sport or be active escorts, and we have one escort dedicated to eliminating any competition.


This can be refined and changed as needed, but the team of 3 to 7 should always be self-organizing and cross-functional. Think of this as an advanced Seal Team, Sports team, ect.

Comments

Popular posts from this blog

Timbur's Log 19 Nov 2949

A few thoughts on Star Citizen's Reputation System

A New Day, A New Goal