Overview

No Items Found.

Post New Update

I really feel this needs to be clarified because so many people are conflicted when in terms of thinking about Why Marvel Heroes or Gazillion does this or that, Or has this bug or releases that so fast; WE ARE NOT Beta Testing, You need to learn about the following truth. While I am not sure if Gazillion uses these methods internally; I do not expect them to officially confirm or deny the method of internal policy and software politic as it may be part of their secret sauce; or only on a need-to-know-basis; IE Investors ETC. But, I see far too many people considering leaving the game, or at least, occuping significant time and threadspace concerned with minor bugs, errata, server downtime or unscheduled events; either unintended or as a conseqence of actively resolving issues; etc.

This is essentially a TL:DR version of Doomsaw's short response in a recent thread complaining about bugs and such related to the new Axis Raid content and variety of new things in the past few days; and overall - across the "Timeline" or "History" of the "Game".

So in this thread I attempt to bring a friendly insight into why things work as they do and as we experience in our Marvelous world; Without siding with or against those who constantly seem to misunderstand exactly why things work as they do; Why we are in FACT part of an active, alive and agile group of content creators, artists, and developers alike (Including Business "men/women" and the IT Crowd.)

Please see this thread as an attempt to bring answers to the many unaware, and often very "worried" players I see complaining and perhaps bringing an unintended image to the community when viewed in error. I hope this bridges some useful information to you and connects with many of the events and processes as well as patches and ways of Marvel Heroes.

I hope this heps a bit, to settle things once and hopefully for all; for those who care to eduma-cate themselves on Easter. Happy Easter; by the way!

Introduction

Agile methods have evolved so that changes during development can be quickly adopted. This approach is the opposite of plan driven traditional approaches. The main focus of agile methods is the early release of working software by responding promptly to changes in specifications using collaborative techniques, code refactoring, test driven development and customer involvement.

As stated in the Agile Manifesto (http://www.agilemanifesto.org):

Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more.
Agile methods follow these principles (http://agilemanifesto.org/principles.html):

-Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.

-Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.

-Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.

-Business people and developers must work together daily throughout the project.
Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.

The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
Working software is the primary measure of progress.
Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
Continuous attention to technical excellence and good design enhances agility.
Simplicity - the art of maximizing the amount of work not done - is essential.
The best architectures, requirements, and designs emerge from self-organizing teams.
At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

For more, Please read the following: http://www.codeproject.com/Articles/25278/Agile-and-Other-Development-Methods

:((

_______________________________________Introduction-End-Reached_____________________________________

PPS: It has been suggested by the humble @Doomsaw; to avoid the habbit or method of reporting bugs in Sub Hero Forums, Use the Master Bug Report Forum for maximum effect and quicker resilliance!

My personal (non-gazillion) suggestion is to write posts like this:
EXAMPLES:

-BUG - RAID - "Boss is hitting through shielded player and killing the guarded player" (WITHOUT QUOTES)
-BUG - STORM - "Power/Electrocute attack range interaction issue and Animation lock in Sirroco Rush has been adjusted/altered since her initial 52-Review and is not feeling fluid, or fair, or how it was." And explain in detail within the thread
-BUG - GUI - "Losing Object Marker when Entering Instance, and Object Header of Portal is Referencing EXTERNAL/Erronous content as Destination"
-BUG - RAID/BOSS(IEAXIS) - "Potential issue with Red Skull and Summoned Companions has been experienced during Ph#2"
-BUG - RAID/AXIS - "Clarification on Invulnerable Interations in New Content or Bug?, We are dying for no reason!"
-BUG - ITEM/Power - "Proc Triggering Proc - "For some reason, My Item is triggering a power type I do not have. Bug?"
-BUG - ITEM/REROLLING - "Item Will Not Upgrade or Reroll to Previously Validated Statistical Ranges.
-BUG - QUEST/BROKEN - "Cannot find entry point to secret area for Mission or Daily quest event"
-BUG - Broken Drops - "Obtained Item X From Monster Z; Is this intended, and is it supposed to happen this much?"
-BUG - Broken Procs - "Cannot Proc due to Hidden Coefficient, a Certain ability or item damage."
And when in doubt, Try something like this:
-BUG/Clarification? - Attack Speed/Spirit Issue - "Having Faster attack seems to eat through my spirit quicker, although the rate of spirit per second remains fixed with Attack speed increases, as per the GUI."

The above examples are used to highlight effective input, And may or may not be current issues raised or known issues to a minority of few, or simply fictional and used as reference

This type of post structure will alllow the team, presumably to address things much faster and with many more times the accuracy and attention needed to resolve things. And allows for all things to fit in the master forum which is checked multiple, several times per day by many different people involved whom which may not have all the time to look at the 40+ Sub Forums for these reports. This is frustrating as a Forum Searcher as well, To find Useful Information in a Specific-Hero only forum, Or Otherwise, Non-existent in a general sense. IE: Too Specific, Sometimes, simplicity and generality is best with such methods.