Mironov Consulting brings deep, hands-on experience to a range of product management

problems. We provide both solo consulting and teams for interim VP Product Management, agile
product strategy and business models. See http!!""".mironov.com!. Product #ytes is our long-
running blog on soft"are, start-ups, product strategies, Silicon Valley, and the inner life of product
managers.
$his M%& template is a "or' of fiction, but may provide good ideas or a fe" chuc'les to product
fol's. (ll rights reserved, especially if you get teleportation "or'ing.
Sample Marketing Requirements Document (MRD)
(uthor!)"ner %ich Mironov, rich*mironov.com
Version!&ate v+.,, ,--March-./,0
Abstract:
$his product release, code-named 1#abylon-0,1 addresses three top re2uirements. 3n order, they are 4,5
meeting the emerging mar'et need for teleportation, 4.5 boosting internal 2uality and supportability through
telepathic diagnostics, and 4+5 increasing net"or'ing price-performance. (ll three are re2uired for successful
release and launch, "hich is planned for next Wednesday.
3n addition, a "ide variety of other improvements and extensions have been identified. 6one of these are
defined as gating items for the release, so may be postponed if they threaten timeliness or functionality of
the release.
%evision 7istory 8example9
V,./ :irst draft for comment, /,-;an-./,,
V,.- 3ncorporating feature order, ,<-Sept-./,,
V../ Coordinated "ith feature si=ing from &evelopment, ..-Mar-./,.
V.., %evised based on initial alpha tests 8liability concerns from Corporate >egal9, ,--(pr-./,+
V+./ %edefined for use only on inanimate ob?ects and cargo due to slight side effects, ./-;un-./,+
V+., @pdated lin's and "ebsite information, ,--March-./,A
B ,CC0-./,A, %ich Mironov.
MRD Template 1 Mironov Consulting, www.mironov.com
Table of Contents
1.0 Strategy and Overview.......................................................................
1.1 Goals and Objectives........................................................................3
1.2 Strategic Road Map...........................................................................3
1.3 Customer Categories !ser "rofiles#.......................................................3
1.$ Competitive Strengt%s and &ea'nesses..................................................$
1.( )*ternal "ositioning..........................................................................$
1.+ Microsoft.......................................................................................$
!.0 "usiness Model.................................................................................#
2.1 ,alue "roposition.............................................................................$
2.2 Mar'et Segment..............................................................................(
2.3 ,alue C%ain Structure.......................................................................(
2.$ Cost Structure................................................................................(
2.( "osition -it%in t%e ,alue .et-or'.........................................................(
2.+ Competitive Strateg/........................................................................(
.0 $%%ected &roups...............................................................................'
3.1 0evelopment..................................................................................+
3.2 Mar'eting......................................................................................+
3.3 Support.........................................................................................+
3.$ Operations.....................................................................................+
3.( Sales............................................................................................+
#.0 "ill o% Materials................................................................................'
$.1 Transporter Server...........................................................................1
$.2 Transporter Console2G!3....................................................................1
$.3 Sound Generator.............................................................................1
(.0 )nternally *ommitted Requirements......................................................+
(.1 )limination of Top ( 4ig%5"riorit/ 6ugs...................................................1
(.2 3nternal "erformance 3mprovements......................................................1
(.3 6ac'-ard Compatibilit/.....................................................................1
(.$ .e*t5Generation 7rc%itectural C%anges..................................................8
(.( "latforms and "rotocols.....................................................................8
(.+ )nd5of59ife for Older ,ersions..............................................................8
(.1 !ptime and :ualit/ of Service.............................................................8
'.0 ,-ternally *ommitted Requirements.......................................................
+.1 Molecular Transmittal........................................................................;
+.2 ,oice57ctivated 0ebug Mode...............................................................;
+.3 6road "erformance 3mprovement..........................................................;
+.$ 7uto5!pgrade <eature.......................................................................;
+.( 6enc%mar's...................................................................................;
+.+ Metering Support for 7S" Model............................................................;
+.0 /ig0ly Desira1le Requirements...........................................................10
1.1 Status 3ndicators............................................................................1=
..0 2uture Requirements.......................................................................10
8.1 !ndo2Redo...................................................................................1=
3.0 2eatures 4ot "eing )mplemented.........................................................10
;.1 Random Transformation....................................................................1=
MRD Template 2 Mironov Consulting, www.mironov.com
1.0 Strategy and Overview
1.1 &oals and O15ectives
{A short, easily measured objective echoed from top page.}
$his product release, code-named 1#abylon-0,1 addresses three top re2uirements. 3n order, they
are 4,5 meeting the emerging mar'et need for teleportation, 4.5 boosting internal 2uality and
supportability through telepathic diagnostics, and 4+5 increasing net"or'ing price-performance. (ll
three are re2uired for successful release and launch, "hich is planned for next Wednesday.
3n addition, a "ide variety of other improvements and extensions have been identified. 6one of
these are defined as gating items for the release, so may be postponed if they threaten timeliness or
functionality of the release.
1.! Strategic Road Map
$his pro?ect is part of the companyDs overall plan to penetrate financial and supply chain accounts in
6orth (merica, "here early adopters for futuristic capabilities tend to collect. 3n addition, it helps us
in our core decision support base, "hich has been "aiting for performance improvements to move
very large files among planetary systems. 6on-Earth customers are a secondary target for the
company, and this product.
1. *ustomer *ategories (6ser 7ro%iles or 7ersonas)
{Detailed description of target users and buyers. May require several sets of target descriptions,
with as much information about customer environments as can be found. Are users road warriors
with alm ilots, or help des! staff running system management tools"}
$arget customers are expected to fall into the follo"ing categories and usage profiles
,.+., Current customer base, loo'ing for performance upgrades and improved
diagnostics. Most are currently on support contracts, so do not generate
incremental revenue F but are our leading source of references and upgrades.
@sage patterns should be similar to current applications, "ith increasing use of ne"
diagnostic features and on-line do"nloading of financial indicators.
Most vocal current customer is 7P printer logistics division, "hich needs to ability to
ma'e urgent deliveries to remote customers at lo" cost. #abylon-0 should allo"
7P >ogistics to centrali=e printer supplies in %oseville C( and #angalore, reducing
real estate costs and in-pipeline inventories else"here. See detailed use case
attachedG
,.+.. Hi-Tech Mergers & Acquisitions users, "ho "ill be most interested in reducing
latency of financial updates and pricing. Moving price data through teleportation
gives program traders and hedge funds a "ay to 1lead the mar'et1 by as much as -
seconds. :or this group, ra" transmission speed is the only criterion.
#igure A sho"s a schematic ho" our system "ill fit "ith pricing data from ma?or
exchanges, 86HSE, 6(S&(I as delivered through %euters!$3#C)9 and buy-side
interfaces "ith portfolio trading apps.
MRD Template 3 Mironov Consulting, www.mironov.com
,.+.+ Plastics Manufacturers, "ho need dramatically better price-performance to reach
production economies. )ur previous versions have re2uired too much computing
po"er for this mar'et. ( +.-x improvement in price-performance brings us into the
right range for the first time, and ahead of our competitors. 3n this segment, total
system cost and support for very large storage arrays "ill drive purchasing
decisions.
$hart % sho"s current and future performance 8in absolute and price-performance
terms9 for this segment. 3f necessary, a mar'et-specific lease option "ill be created
to lo"er upfront buy-in costs.
1.# *ompetitive Strengt0s and 8eaknesses
)ur biggest competitor has failed to address 'ey aspects of this mar'et. $hey have neglected ne"
transport methods in favor of old-style fuel-based mobility. 1#abylon-01 "ill let us tilt the P% playing
field in our favor 81old versus ne"19 as "ell as sell upgrades to older customers no longer on
contract. 3n particular, "e should be able to ta'e share a"ay from #igCo based on their clumsy
pricing and slo" development cycles.
Since "e "ill not yet have filled some holes in our o"n product line 8especially safety testing for
transport of people and live cargo9, "e "ill de-emphasi=e this in our materials and use cases. (ll
mar'eting and advertising "ill picture transporting of physical 8no-living9 goods. 3n addition,
Corporate Mar'eting "ill provide delivery insurance to cover any losses from mis-directed
shipments.
1.( ,-ternal 7ositioning
{A pithy summary of what&s new and different enough that press'analysts will listen}
(t launch, "e "ill position this "ith the broad non-technical press asG
and focus technical revie"ers!readers onG
)ur comparison "ith existing competitors "ill focus onG
:or existing customers, our top-line message "ill beG
1.' Microso%t
$his is in potential competition "ith several long-term Microsoft initiatives, such as 1enfield(
)ac!son1 and 1*+D+1. )ur plan must be either to 4a5 ma'e this an attractive partnering opportunity
for Microsoft, "ith hopes for free bundling or ac2uisition, or 4b5 position it as complementary to
MicrosoftDs incomplete lo"er-level offering, "hich "e assume "ill be bundled at no charge in all of
the follo"ing products and suites )ffice.//0, MoonExplorer, and 1,-%eam1.
(ny discussion "ith press or analysts "ill include a designated P% ! Product Mar'eting
representative to cover Microsoft 2uestions.
!.0 "usiness Model
An e.plicit description of this product /service0 and 1how it ma!es money1 is important to careful planning
2
.
While the business model may change "ith competitive shifts or learning during the development cycle,
assumptions about mar'etplaces and pricing "ill drive many decisions and define ho" "e "in against
existing offerings.
!.1 9alue 7roposition
Clear description of the value created for users by the product!service, including reasons "hy
current offerings are insufficient.
,
#ased on the "or' of Prof. 7enry Chesbrough, 7arvard #usiness School
MRD Template 4 Mironov Consulting, www.mironov.com
3.ample4 database stored procedures 8a.'.a. triggers9 allo" program trading of securities driven by
real-time mar'et price data. Pre-existing solutions re2uired manual intervention or batch price
scans, "hich "ere too slo" to catch real-time mar'et moves. $his technology created a ne" class
of traders able to arbitrage tiny mar'et inefficiencies, and made millions for early Wall Street
adopters.
!.! Market Segment
Who are the users 83$, line of business, roaming execs, home surfersG9J What are the details of
the applicationJ
3.ample4 a global 3nternet dial-up service is targeted at roaming business users "ith Windo"s
laptops "ho cross national boundaries. $hey dial in for email and corporate 3P applications 8on
average9 t"ice per business day and infre2uently on "ee'ends. $hey are non-technical, so cannot
be counted on to configure any local settings or understand the subtleties of local telephone
services.
!. 9alue *0ain Structure
7o" "ill this be distributedJ What are necessary complementary productsJ What prere2uisites "ill
customers re2uire 8and that can be used as mar'eting screens9J
3.ample4 a real-time alerting system for corporate bac'-office applications re2uires deployed,
"or'ing corporate applications 8e.g. E%P or finance9 and bro"sers installed on all end user systems.
3t is a complement to these large apps, adding value to triggering or error status features, since end
users often fail to see urgent alerts. (s a stand-alone offering, it lac's high-value content. Can
Mar'eting create a simple targeting screen for early location!2ualification of prospectsJ
!.# *ost Structure
3s this a service or a productJ (re costs driven by one-time %K& or ongoing support and
provisioningJ What is the profit potential given the customer proposition and value chainJ
3.ample4 a transaction-based service has high fixed 8start-up9 costs and lo" per-transaction costs.
( .ALML+0- support team is expensive to maintain, but can manage a large number of cases "ithout
expanding. Company needs to get a minimum revenue per month 8day, year9 to cover support costs
and amorti=e %K&, but needs relatively little per additional transaction to generate profitability.
Subscription model and per-transaction fees are possible pricing solutions.
!.( 7osition wit0in t0e 9alue 4etwork
7o" does the company lin' "ith suppliers and customersJ Which are li'ely complementors and
competitorsJ Who "ould lead in a teamed sales modelJ
3.ample4 :ault-tolerant systems platforms are re2uired for C,, applications as "ell as cash
machine net"or's. 3n both cases, the customer re2uires a custom soft"are solution, "hich is
chosen before the hard"are!)S combination. $he systems provider must team "ith top vertical app
developers and "in their attention!loyalty versus alternate platform providers. 6atural channels are
)EM through application vendorsN V(% through system integratorsN in-house application
development teamsN investment or ac2uisition of leading app providers.
!.' *ompetitive Strategy
7o" "ill "e gain advantage over competitorsJ What uni2ue resources do they lac', or conflicts
have they created, that 'eep them from using the same strategyJ >oo' for specific 1hard1 items,
rather than generic ans"ers 8e.g. focus, smarter team, reputation9.
MRD Template 5 Mironov Consulting, www.mironov.com
.0 $%%ected &roups
.1 Development
&evelopment "ill need to build an overall plan, and execute against that plan. Current target date
for first beta release is (pril .//M, and general availability in (ugust .//M. @nless explicitly signed
off, all listed features and functions "ill be included. Where trade-offs are made, Product Mar'eting
"ill be included in the decision process.
I( "ill be done by our testing group inG $his is targeted as part of our broader release of version
-./ scheduled forG
.! Marketing : Sales
Product management "ill be done byG External P% and announcement planning "ill start in 6ov-
.//0 and be headed byG $raining materials and vertical mar'et "hite papers "ill be the
responsibility ofG >eads and ne" prospects "ill be identified by a combination of direct mail, opt-in
email and seminars starting inG
SALES: Oey accounts 'no"n to "ant this product areG :ormal sales training is planned forG :ield
technical resources "ill be trained in advance of customer betas. Current beta dates and prospects
areG 3dentification of target accounts among the installed based "ill be done byG
. Support
$his product addresses the follo"ing 'no"n "ea'nesses in our current offering, as identified by
SupportG We "ill designate a 1tiger team1 to handle beta and early production calls from
customers from our Support group inG Sign-off on customer and internal training materials "ill be
done byG 3n addition, Support "ill recruit untrained customers and prospects to do user testing of
the beta product. @sers "ill attempt to install and use the product "ithout manuals or install guides,
and "ill score their experience. 3f M/P of these testers are unable to perform a minimal set of
product functions QlistR, Product Management and Support "ill do a full revie" of @3 and functional
designs.
.# Operations
)perations must G
Iuality of service metrics for this product areG
$est installations and )perations acceptance testing "ill be done byG
.( Sales
Starting in ;an-.//M, "e "ill begin loo'ing for beta customers among the existing installed base.
$his "ill be led by Sales, specifically Meredith Sreenfield 8)maha9 and Patty )D:urn 8&ublin9G
Presales SEs "ill get t"o rounds of product training initial concepts and selling strategies. Sales
$raining "ill be responsible for coordinating these events and turning standard mar'eting
deliverables into Sales formatsG
Mar'eting "ill launch a contest and campaign during the first three months of availability, "ith pri=es
for all %eps "ho close more than one accountG
.' ;egal
:or some products 8e.g. this teleportation product9, developers "ill need to "orry about liability and
failure issues F and include a legal revie" of the product or claims. Consider the conse2uences of a
net"or' outage on hospital systems, or a security breach of la" enforcement databases. :or
MRD Template 6 Mironov Consulting, www.mironov.com
teleportation, are there disclosures and "arnings that "ould minimi=e la"suits "hen an occasional
user arrives as a puddle of 2uivering protoplasmJ
#.0 "ill o% Materials
$his section identifies all of the customer-visible product deliverables to be produced, as "ell as
customer site re2uirements and dependencies. :rom this list, a development schedule can be
created to complete everything needed 1in the box1 for successful customer installations and
deployments. )nce this #)M is matched to a product architecture, all pieces are re2uired F
therefore no priority is implied by this sectionDs numbering scheme.
#.1 <ransporter Server
$his server soft"are runs on a conventional (pp Server provided by #E( 8Web>ogic9 or 3#M
8WebSphere9. 3t controls all transporter functions and continuously chec's for errors.
#.! <ransporter *onsole=&6)
$he console manages the $ransporter Server and provides its user interface. 3n addition to physical
controls, the Console can be managed via voice commands and unobtrusive (S> 8(merican Sign
>anguage9 hand gestures.
#. Sound &enerator
Every cool device needs its o"n set of special sounds to indicate proper operation. $his subsystem
lets engineers choose the sound palates most to their li'ing, and coordinates the sound generator
units 8SS@s9.
#.# Demograp0ic 6psell Module (D6M)
$he &@M as's each teleportation user to provide some demographic information before being
transported. $his is useful for contacting next-of-'in after a system failure as "ell as offering
additional products 8life insurance, destination-appropriate clothing9 and adding to Mar'etingDs
database of user profiles. >egal has as'ed us to include a disclaimer that demographics are not
re2uired, and do not have any effect on Iuality of Service.
(.0 )nternally *ommitted Requirements
Within this section, each item is ran'ed, "ith +., ta'ing higher priority than +.., etc. Product o"ners
and development must 'no" "hich features are most important. 3n general, this section contains
features or improvements that are invisible to customers, or "hich will not be announced.

(.1 ,limination o% <op ( /ig0>7riority "ugs
$echnical Support and Product Management have compiled a list of our most serious soft"are
defects, as follo"s. (ll of these must be fixed and tested prior to release. (s of this "riting, they
include
#uffer over-"rite on messages T .<.A $#
Memory lea' causing re2uired reboot of core service every << hours
$runcated header data on $ype 33 E&3 loo'ups
%emoval of end user option to turn off soft"are updates
MRD Template 7 Mironov Consulting, www.mironov.com
Misreading of 3CMP pac'ets as (pple$al' printer 2ueue re2uests
(.! )nternal 7er%ormance )mprovements
$"o bottlenec's have been identified that are generally not yet visible to customers retrieval of real-
time database records during bac'up cycles, and simultaneous receipt of multiple items by a single
transmitter. #oth "ill start to sho" up in customer testing 8or live production use9 as traffic builds
beyond 0- S#!hour. &evelopment must tune!redesign the MMS and $0 modules, and I( must
verify that "e can score more than << on the $CP-U benchmar'.
3n addition, "e "ill re2uire improvement of at least ./P on each of the follo"ing metricsG
We "ill also need more complete analysis charting of the 'ey performance variables that customers
'eep demanding. $his includes the improved performance from additional server memory up to
-,.S# and support for larger 1chun'ing1 hard"are to handle extra-long organic molecules such as
&6(.
(. "ackward *ompati1ility
$his version of our product "ill "or' "ith previous versions starting "ith v../ and including our most
recent release 8A.A#9. 3t must allo" a mixed use model, "ith all versions running simultaneously on
separate machines, since forcing an instantaneous upgrade is not yet possible. With the follo"ing
exceptions, no functions or capabilities "ill be removed in this version
#ac'up!restore "ill be limited to formats from versions A./ and later. )lder bac'ups can be
retrieved using a pre-existing copy of the soft"are.
$he 1audio only1 communications mode "ill be discontinued.
Customers "ill be notified C months in advance 8in "riting and from their sales teams9 of these
changes.
(.# 4e-t>&eneration $rc0itectural *0anges
$his release "ill include changes to internal data structures and management mechanisms that "ill
not be complete or visible until a later releaseG
(.( 7lat%orms and 7rotocols
Server-side soft"are "ill run on %ed 7at Enterprise >36@U vM.. and later, Windo"s Vista Server
..-V, and Solaris ,/. 6o special client-side soft"are "ill be re2uired other than bro"ser support
8minimal set of 7$M> and (;(U supported by both MS3E 0.,V and :irefox ../V9. Client-side
bro"ser testing "ill be done on Win.', WinUP, MacU, >36@U M./V and Palm)S. Communications
"ill be assumed as 7$$P8S9 or :$P over standard $CP!3P unless other"ise stated.
(.' ,nd>o%>;i%e %or Older 9ersions
Starting + months after launch, "e "ill announce end-of-life (!"# and end-of-su$$ort (!%# for
previous versions running on a variety of obsolete platforms. $hese include 7P-@U, all 3#M )S
platforms other than >36@U, @>$%3U, &EC )S:!,, SS3 3%3U, bac' versions of 3ngres and 3nformix
databases, and net"or'ing support for 3PU and (pple$al'. Customers "ill be given from upgrades to
any supported platform. )ur E)> program outline "ill be
6otify all customers in "riting of impending E)>!E)S three months after this launch
3nclude offer of free upgrade! migration to any currently supported platform "ithin ,. months of
announcement
MRD Template Mironov Consulting, www.mironov.com
Special 1SW($ team1 created for professional services opportunities "ith customer migrations
6o additional patches or fixes to be made 0 months after announcement date
6o ongoing support or technical assistance ,. months after announcement date
(.+ 6ptime and ?uality o% Service
Customers are assumed to accept at least .. minutes of do"ntime per month for upgrades,
database bac'up, and hard"are preventive maintenance. (ll configuration and management
functions must be performed "hile applications are running, so cannot re2uire any shut-do"ns, off-
line periods, or restarts. $his translates to CC.C-P uptime. )perations "ill monitor and report on all
'no"n customer do"ned systems, collect statistics, and calculate actual field uptime. 3n addition,
monitoring soft"are "ithin the applicationG $hird party test tools "ill includeG )nce "e have
achieved our target uptime, "e "ill begin reporting this monthly to customers as an aggregate result
8averaged over all customers and all systems9. We "ill ma'e our measurement tools available to
customers "ho "ant to trac' their o"n uptimeG
'.0 ,-ternally *ommitted Requirements
Within this section, each item is ran'ed, "ith A., ta'ing higher priority than A.., etc. External
announcements and customer communications "ill follo" this list, since they are ran'ed in
importance. 3f the first A items are not completed, "e "ill delay launch until they are finished and
fully tested.
'.1 Molecular <ransmittal
(O( teleportation, this is the ability to move matter to remote devices "ithout traversing the
intermediate space. Customers are eager to get this feature, and the competition is years behind in
developing it. Several ma?or customers are "aiting for this, including G
$his is a ma?or ne" capability and "ill set us apart from the competition by allo"ing customers toG
'.! 9oice>$ctivated De1ug Mode
Since users often have their hands full "hen problems develop, this ne" feature allo"s them to as'
1"hat if1 and 1"hatDs "rong1 directly F instead of touching a 'eyboard. :iltering has been included,
"hich deletes inappropriate "ords before logging and translating them.
6ote to I( extensive testing must be performed on sound-ali'e "ords. :or instance, customers in
the supply chain may often use 1ship1 or 1truc'1 so should not have these bloc'ed or deleted.
'. "road 7er%ormance )mprovement
We must sho" general performance improvement of at least +-P, as measured "ith our internal
W36S. test suite. $his reflects actual customer applications. We "ill also use standard industry
benchmar's 8belo"9, "hich must sho" at least +/P improvement.
3f our "or' to overcome internal bottlenec's 8above, section +9 contributes to this, then "e have a
double "in. 3f not, "e still re2uire that customers running normal application loads or benchmar's
see mar'ed improvement. $herefore, a full set of CP@ usage and "ait time data "ill be re2uired
from our Perf>ab F including identification of the top 0 to ,/ CP@ 1hogs1 and net"or' latency areas.
MRD Template ! Mironov Consulting, www.mironov.com
'.# $uto>6pgrade 2eature
Customers continue to have difficulty accepting, scheduling or applying soft"are updates 8patches,
interim releases, and ma?or upgrades9. $his release "ill include an 1auto-update1 feature that is
enabled by default, but can be turned off by the customer or by us. 3n addition, it must allo" for
selective upgrades by version and customer 3&.
3f accepted by customers, "e expect to discontinue our distribution of physical media in ;an-.//<,
and begin increasing support charges for versions more than one year old. Customer Support
expects this to allo" promotion!redeployment of more than ,/P of their staff, and is an important
part of their plan to reduce case turn-around times by +-P during :H.//<.
'.( "enc0marks
We "ill run the follo"ing performance tests internally, "ith a plan to release benchmar's beating the
competitionG $hird party test labs that "ill re-run or verify our results areG Publications that
promote these benchmar's includeG
'.' Metering Support %or $S7 Model
Mar'eting "ill re2uire a pricing mechanism for (SPs 8application service providers9 "ho "ill offer
teleportation 1per trip1 rather than on a full license basis. Product must support a method for
counting and billing for each use. 3deally, this "ill include pac'et counts, so that larger items can be
billed at higher rates than smaller ones.
+.0 /ig0ly Desira1le Requirements
$his section sho"s items that ma& be included in this release, but are not committed yet. 3t is
intended to reduce 2uestions about 1that thing "e as'ed for, but isnDt included on your list.1 3n
general, since lists get shorter during development, fe" of these items are expected to fit in the
current release.
+.1 Status )ndicators
While not re2uired, this "ill dramatically reduce calls to $echnical Support. 83t may also reduce
la"suits.9 System should sho" status of all transfers in progress, as "ell as statistics and details on
completed and 2ueued transfers. &ata must include date!time, destination, origin, si=e, "eight, and
delivery options.
%ed 1alert1 signals must identify if any item has failed to be received intact, or if 2ueued items have
been flushed from buffers.
..0 2uture Requirements
$his section sho"s items that may be included in later releases, but are not committed in this
release. 3t is intended to reduce 2uestions about 1that thing "e as'ed for, but isnDt included on your
list.1
MRD Template 1" Mironov Consulting, www.mironov.com
..1 6ndo=Redo
$his has been re2uested by many customers, but is not included in this release. Some architectural
"or' has been slipped into the main code line for completion in later releases. :or no", customers
"ho send something do not have the option to 1change their minds1 or later destination coordinates.
3.0 2eatures 4ot "eing )mplemented
Some re2uests are specifically excluded or denied. Sho"ing them here is an excellent "ay to move
conversations from 1"henJ1 to 1"hy notJ1 Most re2uests that do not come from a ma?or customer
or support critical strategic ob?ectives end up here.
3.1 Random <rans%ormation
$"o vocal customers have made repeated re2uests for items to be transformed F at random F
during teleportation. $his is a fundamentally bad feature, since it could be turned on accidentally or
by hac'ers. Please be clear and unambiguous "ith customers that this is not a feature "e "ill ever
implement, and that enhancement submissions "ill be closed "ith the 16ot @nder &evelopment1
label.
MRD Template 11 Mironov Consulting, www.mironov.com