Agile principles

The Agile Manifesto is based on twelve principles:[15]

Customer satisfaction by early and continuous delivery of valuable software
Welcome changing requirements, even in late development
Working software is delivered frequently (weeks rather than months)
Close, daily cooperation between business people and developers
Projects are built around motivated individuals, who should be trusted
Face-to-face conversation is the best form of communication (co-location)
Working software is the principal measure of progress
Sustainable development, able to maintain a constant pace
Continuous attention to technical excellence and good design
Simplicity—the art of maximizing the amount of work not done—is essential
Best architectures, requirements, and designs emerge from self-organizing teams
Regularly, the team reflects on how to become more effective, and adjusts accordingly

Relationship to DevOps

Because both DevOps and Agile principles embody many Lean philosophies, including collaboration and communication, their meanings are often conflated; in reality they are two different concepts. Organizations that adopted agile development began to see a higher quantities of releases; with this, Continuous delivery and DevOps were born. [19] Agile represents a change in thinking, whereas DevOps implements actual organizational cultural change. One DevOps goal is to establish an environment where releasing more reliable applications faster and more frequently can occur. [20] DevOps practitioners are utilizing resources such as application release automation and Infrastructure as code tools to help advance these goals and adopt software development best practices, including agile principles. [21]
Iterative, incremental and evolutionary

Most agile development methods break the tasks into small increments with minimal planning and do not directly involve long-term planning. Iterations are short time frames (timeboxes) that typically last from one to four weeks. Each iteration involves a cross-functional team working in all functions: planning, requirements analysis, design, coding, unit testing, and acceptance testing. At the end of the iteration a working product is demonstrated to stakeholders. This minimizes overall risk and allows the project to adapt to changes quickly.[22] An iteration might not add enough functionality to warrant a market release, but the goal is to have an available release (with minimal bugs) at the end of each iteration.[23] Multiple iterations might be required to release a product or new features.

Working software is the primary measure of progress.
Efficient and face-to-face communication

No matter what development disciplines are required, each agile team should include a customer representative (product owner in scrum). This person is appointed by stakeholders to act on their behalf[24] and makes a personal commitment to being available for developers to answer mid-iteration questions. At the end of each iteration, stakeholders and the customer representative review progress and re-evaluate priorities with a view to optimizing the return on investment (ROI) and ensuring alignment with customer needs and company goals.

In agile software development, an information radiator is a (normally large) physical display located prominently in an office, where passers-by can see it. It presents an up-to-date summary of the status of a software project or other product.[25][26] The name was coined by Alistair Cockburn, and described in his 2002 book Agile Software Development.[26] A build light indicator may be used to inform a team about the current status of their project.
Very short feedback loop and adaptation cycle

A common characteristic in agile is the daily "stand-up", also known as the daily scrum. In a brief session, team members report to each other what they did the previous day toward their team's sprint goal, what they intend to do today toward their team's sprint goal, and any roadblocks or impediments they can see to their team's sprint goal.[27]
Quality focus

Specific tools and techniques, such as continuous integration, automated unit testing, pair programming, test-driven development, design patterns, domain-driven design, code refactoring and other techniques are often used to improve quality and enhance project agility.[28]

Applications outside software development
Agile Brazil 2014 conference

Agile methods have been extensively used for development of software products and some of them use certain characteristics of software, such as object technologies.[104] However, these techniques can be applied to the development of non-software products, such as computers, motor vehicles,[105] medical devices, food, clothing, and music;[106] see Flexible product development. Some of the wider principles of agile have also found application in general management[107] (e.g., strategy, governance, risk, finance) under the terms business agility or Agile Business Management.

Under an Agile Business Management model, agile techniques, practices, principles and values are expressed across five domains.[108]

Integrated customer engagement - to embed customers within any delivery process to share accountability for product/service delivery.
Facilitation-based management - adopting agile management models, like the role of Scrum Master, to facilitate the day-to-day operation of teams.
Agile work practices - adopting specific iterative and incremental work practices such as Scrum, Kanban, Test-Driven Development or Feature-Driven Development across all business functions (from Sales, Human Resources, Finance[109] and Marketing).
An enabling organisational structure - with a focus on staff engagement, personal autonomy and outcomes based governance.
An education model the blends agile practices and philosophies to create micro-schools that emphasize collaborative culture creation and self-directed learning.

Agile development paradigms can be used in other areas of life such as raising children. Its success in child development might be founded on some basic management principles; communication, adaptation and awareness. Bruce Feiler has claimed that the basic Agile Development paradigms can be applied to household management and raising children. In his TED Talk, "Agile programming -- for your family", these paradigms brought significant changes to his household environment, such as the kids doing dishes, taking out the trash, and decreasing his children's emotional outbreaks, which inadvertently increased their emotional stability.

taken from Wikipedia

Started spriting today

The walking looks kinda weird to me..

Is there anything planned for attacks or fighting style ?

- Rules. Some rules / guidelines that we should all work with
- Are you active / what are you working on. This is where we inform people of our activity for the mod.
- Character sprite concepts. This is where we make concepts for new characters;
- Originals Evolotion. This is where we discuss anything that has to do with sprite concepts for the original characters and concept moves for the original characters;
- Story mode. On the last page of this topic, you can find the story we have based our mod on;
- List of characters in the game. Here you can find a list of all the characters in our mod;
- Updated plan. This one is quite important. It tells you what we have to work on, basically So after we're done with Nino, we'll probably continue with the Wizard character (so perhaps you could try to make a few frames for that character to get into it )
- [Char] Nino. Progress for the character Nino;
- [CHAR] Wizard. Progress for the character Wizard;
- Applications. Here we discuss whether people are to be accepted in our mod or not;
- Exe file. Discussion on anything related to the exe file
- An option. Gad offered to use his characters from the space LF2 mod. We'll only use his character Hydron
- Level of quality. This is a topic for the spriters mostly, to make sure everybody uses the same spriting style ;-)
- Discussion on the limitations. As the title suggest, a discussion on what can and what can't be done in the mod (f.e. we don't want a mod with giant super moves like in R-LF2)
- Conversation room. Anything that doesn't belong in the topics above can be discussed here