+ {% block body %}{% endblock %}
+
diff --git a/app/config/config.yml b/app/config/config.yml
index b6da31e..3e45fe6 100644
--- a/app/config/config.yml
+++ b/app/config/config.yml
@@ -4,7 +4,7 @@ imports:
framework:
#esi: ~
- #translator: { fallback: %locale% }
+ translator: { fallback: %locale% }
secret: %secret%
charset: UTF-8
router: { resource: "%kernel.root_dir%/config/routing.yml" }
diff --git a/src/OpenScrum/InfoBundle/Controller/DefaultController.php b/src/OpenScrum/InfoBundle/Controller/DefaultController.php
index ef60b01..1c3882f 100644
--- a/src/OpenScrum/InfoBundle/Controller/DefaultController.php
+++ b/src/OpenScrum/InfoBundle/Controller/DefaultController.php
@@ -8,8 +8,13 @@ use Symfony\Bundle\FrameworkBundle\Controller\Controller;
class DefaultController extends Controller
{
- public function indexAction($name)
+ public function indexAction()
{
- return $this->render('OpenScrumInfoBundle:Default:index.html.twig', array('name' => $name));
+ return $this->render('OpenScrumInfoBundle:' . $this->get('session')->getLocale() . ':index.html.twig', array());
+ }
+
+ public function infopageAction($page)
+ {
+ return $this->render('OpenScrumInfoBundle:' . $this->get('session')->getLocale() . ':' . $page . '.html.twig', array());
}
}
diff --git a/src/OpenScrum/InfoBundle/Resources/config/routing.yml b/src/OpenScrum/InfoBundle/Resources/config/routing.yml
index da2b062..1598759 100644
--- a/src/OpenScrum/InfoBundle/Resources/config/routing.yml
+++ b/src/OpenScrum/InfoBundle/Resources/config/routing.yml
@@ -1,3 +1,17 @@
OpenScrumInfoBundle_homepage:
- pattern: /hello/{name}
- defaults: { _controller: OpenScrumInfoBundle:Default:index }
+ pattern: /{_locale}
+ defaults:
+ _controller: OpenScrumInfoBundle:Default:infopage
+ _locale: en
+ _format: html
+ page: index
+
+OpenScrumInfoBundle_infopage:
+ pattern: /{_locale}/info/{page}.{_format}
+ defaults:
+ _controller: OpenScrumInfoBundle:Default:infopage
+ _locale: en
+ page: about
+ requirements:
+ _format: html
+ _locale: en
diff --git a/src/OpenScrum/InfoBundle/Resources/views/Default/index.html.twig b/src/OpenScrum/InfoBundle/Resources/views/Default/index.html.twig
deleted file mode 100644
index 4ce626e..0000000
--- a/src/OpenScrum/InfoBundle/Resources/views/Default/index.html.twig
+++ /dev/null
@@ -1 +0,0 @@
-Hello {{ name }}!
diff --git a/src/OpenScrum/InfoBundle/Resources/views/en/about.html.twig b/src/OpenScrum/InfoBundle/Resources/views/en/about.html.twig
new file mode 100644
index 0000000..b7e563c
--- /dev/null
+++ b/src/OpenScrum/InfoBundle/Resources/views/en/about.html.twig
@@ -0,0 +1,128 @@
+{% extends '::base.html.twig' %}
+{% block body %}
+
About OpenScrum.org!
+
+
What is OpenScrum?
+
OpenScrum is a tool for agile development. It is a web based tool to manage your project development.
+
Become a Product Owner, define your Product, gather a Team, add your Ideas, and then all you need to do is to watch as your Product is being developed.
+
Join as a developer, read the Product advertisements, apply to join a Team, split the Product Owner's Ideas into Tasks, and start developing! You get a fully functional discussion board for it.
+
+
What OpenScrum is not?
+
+
OpenScrum is not an issue tracker
+
Although the product backlog can be seen as one, issues should be tracked in a separate software. For example, the OpenScrum team uses Bugzilla for this purpose.
+
+
OpenScrum is not a project planner
+
Although the product and sprint backlogs can be seen as one, it doesn't (and won't) provide all features of a project planner.
Want to see a real life example with pictures and stuff? Check out the Examples page!
+
+
Extract of the TODO file
+
According to the sprint length, the user story estimations and priorities, the team and the stakeholder create the backlog of the next sprint. The team will use this backlog during the sprint.
+
However, sometimes it is required to discuss something. This can be done within the specific user story using a chat function. The sprint backlog can not be changed during a sprint, as it would change the sprint's length. Instead, in the discussion, the development of the story can be halted. This, of course will mean that tha story will not be finished at the end of the sprint and will appear as unfinished in the review.
+
OpenScrum also provides some help during the Daily Scrum. It provides a chat interface on which Team members can discuss the last and next day. If the Team holds the Daily Scrum in person instead, the Scrum Master should upload a brief extract of the Daily Scrum for documenting purposes. These documents are unseen by the Product Owner unless otherwise stated by the Scrum Master.
+
During the development Team members can login anytime to see or update the status of user stories. Some parts of these updates are published to the Product Owner, so they can monitor the development's status.
+
When the Sprint is finished, OpenScrum may come in handy for the Sprint Review, either.
+
+
User story sources
+
+
Product backlogs
+
+
customer can priorize user stories by business value
+
customer must refine the user story, with the aid of the team if necessary
+
teams can vote for actual story difficulty. Only those stories make into the product backlog, which is approved by both the customer and the team: customer simply approves (yes/no), team assigns difficulty as approval (with a successful vote)
+
+
+
Sprint backlogs
+
+
product owner must define the title of each sprint
+
the team must break down the user stories into tasks
+
the team must set time requirement for the tasks
+
the tasks must have a title, a brief and long description and a time frame
+
chicken access to sprint backlog and task status may be disabled
+
+
+
Help for the daily scrum
+
+
display the task states
+
display the product burndown charts
+
the team can do the daily scrum via XMPP-based chat, integrated into the site
+
tasks can be moved at any given time, all charts and reports are updated real time
+
+
+
Sprint review
+
+
at the end of a sprint, the customer can accept or decline user stories, depending on their readiness
+
after closing the stories, the sprint itself is closed automatically
+
+
+
Sprint retrospective board
+
+
this is only a small blackboard, on which team members can discuss everything about the current sprint. This is only a tool to aid the scrum master during the retrospective.
+
+
+
Users and roles
+
+
each user can be a chicken or a pig
+
any pig can be assigned to the special role "scrum master"
+
the scrum master cannot be a product owner for any products
+
+
+
Products
+
+
each product must have exactly one product owner
+
all products must have a product description and may have customer information
+
+
+
Teams
+
+
all team must have at least one member to be considered as active
+
product owners and the scrum master can be the member of any team
+
+
+
Sprints
+
+
every sprint mst have a goal
+
at most one sprint must exist for each product at any given time
+
+
+
OpenScrum.org user stories
+
+
as the site owner, I want unregistered users to access the information pages and public Products only
+
as the site owner, I can decide if I want to allow anyone to register
+
as a possible later Product Owner, I can register my company providing a contact e-mail address, and optionally uploading a brief description of it
+
as a possible Product Owner or Team member I can register myself by choosing a username and password, providing a contact e-mail address, and optionally uploding my CV with references and some details about myself
+
as a registered user, I am able to log in to the site using my chosen username and password
+
as a Product Owner I can create a new Product on behalf of my company
+
as a Product Owner I can create advertisement about my product to find developers for my Team
+
as a Product Owner I can invite developers to my Team
+
as a Product Owner I can choose a possible Scrum Master from my Team
+
as a Team member I can vote with a plus or minus on the chosen Scrum Master
+
as a Product Owner I can set who can add items to my Product's Idea Pool: me, the Team, or anyone
+
as a Product Owner, Team member or a normal registered user I can add items to the Product's Idea Pool depending on the Product's settings
+
as a Product Owner or Team member I can vote with a plus or a minus on the Idea Pool items depending on the Product's settings
+
as a Team member I can estimate the difficulty or required time for each item in the Idea Pool
+
as a Product Owner, I can see the difficulty or development time estimated by the Team
+
as a Product Owner, I can promote one of the Team members to Scrum Master
+
as a Team member, I can put a positive or negative vote on the promoted Scrum Master. If enough positive votes are gathered, the promoted member will become the Scrum Master. If enough negtive votes are gathered, the selected person will automatically be demoted, and the Product Owner has to promote again
+
as a Product Owner or a Team member (or optionally, as a regular user, if the Product is public), I can add my ideas to a Product's Idea Pool
+
as a Product Owner, I can see if my Product has an active Sprint
+
as a Team member, I can see the Idea Pool, Product Backlog and current Sprint Backlog of the Products I am assigned to
+
as a Team member, I can estimate the difficulty of each accepted items in the Idea Pool of every Product I am assigned to, and optionally enter the reason of my decision
+
as the Product Owner, I can see my Product's Idea Pool, and accept or reject them. If I accept them and the Team has estimated its difficulty and development time, it gets to the Product Backlog. For both cases, I can add some comments on my decision
+
as a Scrum Master of a Team, I can enable or disable access to the Sprint's details (chat logs and development boards) for the Product Owner. It should be disabled by default.
+
as a Product Owner, I can see the Product Backlog of my Products, and priorize the items in it
+
as a Product Owner, I can import tickets from an issue tracker. These issues get into the Idea Pool, so I can decide if a specific bug or Feature Request get into the Product Backlog, or will be developed/fixed in a different way
+
as a Product Owner, I can request the beginning of the next Sprint for my Product
+
as a Scrum Master of a Team, I can start the next Sprint of a Product
+
as the Product Owner and Scrum Master together we can decide to cancel the current Sprint of a Product, and add the reason of the cancellation
+
as Team members, we can divide Sprint Backlog items into tasks, predicting the required time and resources for each task
+
as Team members, we can discuss how a specific User Story will be developed using the chat board dedicated to that User Story
+
as a Team member, I can update the status of User Stories in the active Sprint Backlog I am assigned to
+
as the Product Owner or Team member I can see statistics and charts about my Product's past and current Sprints
+
as the Team, we can send back unclear Ideas to their authors to clarify things
+
as the Team, we can estimate a Product Backlog item as Extremely Difficult. Such items may get back to the author of that idea to be broken down into smaller tasks, or, if we decide, we can achieve the same
+{% endblock %}
diff --git a/src/OpenScrum/InfoBundle/Resources/views/en/faq.html.twig b/src/OpenScrum/InfoBundle/Resources/views/en/faq.html.twig
new file mode 100644
index 0000000..afe27a0
--- /dev/null
+++ b/src/OpenScrum/InfoBundle/Resources/views/en/faq.html.twig
@@ -0,0 +1,31 @@
+{% extends '::base.html.twig' %}
+{% block body %}
+
+ The Product Owner will add some for sure, as he has the whole picture in his head. Of course, the Product Owner may change the Product Settings to the Team members can add their own Ideas, or, if the Product itself is for the public, it can be set up so every registered user can add items to the Idea Pool.
+
+
+
An issue tracker
+ OpenScrum.org can import bugs and features from issue trackers. This will create special user stories, which later can be revised or deleted from the Product Backlog. However, be warned that by definition, the bugs imported this way will only be fixed at the end of the next Sprint, so a better approach to this would be to fix bugs between two Sprints, or to dedicate some developers who will not work on the next Sprint, but will fix bugs instead.
+
+
+
+
How long a Sprint should be?
+
By definition, a Sprint is a time frame between one week and a month. To decide the best value, you should ask yourself the question "How do I want to see the next version of my Product, and what does my Team say, how long does it take to develop it?".
+
You can set a default Sprint length on the Product's configuration page. This value can be changed at the beginning of each Sprint based on the items you want to see in the Sprint Backlog.
+
+
Do I have to use this site? I don't think my Product can be kept secret here...
+
The Products you register on OpenScrum.org are private by default. This means that only you, your Team(s), and in case of emergency, our site administrators can see them. However, if you work on a top secret project, but you still want to track the development process with OpenScrum, you can buy the whole source code and run it on your own infrastructure.
+
Buying OpenScrum will give you a one year read only access to our Git repository, so you will get all the patches and new features during that period.
+
+
What can I do if the development of an item in the Idea Pool takes longer than the maximum Sprint length?
+
The maximum length of a Sprint is one month. If the Team says developing a specific idea would be longer than a month, the person who added the Idea will be notified and asked to break down the Idea into smaller Ideas. If he does not do it, the Idea will get inactive. Of course, the Product Owner or the Team may split it into smaller parts without involving the original requestor.
+
+
Should I communicate with my Team as a Product Owner?
+
This is a decision you and your Team should make together. Some Teams don't like to be disturbed during the development, others can afford the time and human resources to inform their principals. However, OpenScrum.org provides a neat status page on which the Product Owner can follow the progress of the Sprint Backlog items, which should generally be enough for the average Product Owner.
+{% endblock %}
diff --git a/src/OpenScrum/InfoBundle/Resources/views/en/index.html.twig b/src/OpenScrum/InfoBundle/Resources/views/en/index.html.twig
new file mode 100644
index 0000000..bef7f76
--- /dev/null
+++ b/src/OpenScrum/InfoBundle/Resources/views/en/index.html.twig
@@ -0,0 +1,5 @@
+{% extends '::base.html.twig' %}
+{% block body %}
+
Welcome to OpenScrum.org!
+
OpenScrum.org is a web based tool to help development teams to develop using the Scrum methodology.
+{% endblock %}
diff --git a/src/OpenScrum/InfoBundle/Resources/views/en/terms.html.twig b/src/OpenScrum/InfoBundle/Resources/views/en/terms.html.twig
new file mode 100644
index 0000000..3941685
--- /dev/null
+++ b/src/OpenScrum/InfoBundle/Resources/views/en/terms.html.twig
@@ -0,0 +1,64 @@
+{% extends '::base.html.twig' %}
+{% block body %}
+
Terms and Definitions
+
+
Lifetime of a project
+
The Product is registered by the Product Owner, its Idea Pool is filled with Ideas, they get approved by the Product Owner and their difficulties get estimated by the Team, or get rejected by one of the parties. Approved and estimated Ideas move into the Product Backlog as User Stories, where they are priorized by the Product Owner. Meanwhile, the Product Owner and the Team choose a member of the Team, and promote her/him to the role of Scrum Master.
+
When there are enough Ideas in the Idea Pool, the Product Owner and the Team gather in a Sprint Planning meeting to plan the next Sprint. During this time, the chosen User Stories get moved to the Sprint Backlog. After this, the development of these User Stories begin. Every day, the Team gathers for a Daily Scrum, to discuss what was done on the previous day, and what will be done on the next day.
+
At the end of the Sprint, the Team and the Product Owner gathers for the Sprint Review, to check if the User Stories are developed successfully. User Stories are checked one by one, and the Product Owner decides if they are Done or not. Done items are then moved into the increment, others are revised if necessary, and put back to the Product Backlog. After this, the increment is added to the Product, and the new version is released, if the Product Owner approves it.
+
After this, the Team stays together, and holds the Sprint Retrospective to discuss the whole Sprint, and decide if they have to do things different in the next Sprint.
+
+
Roles
+
+
Product Owner
+
The representative person of the Product's owning company, or the owner himself. By definition he is never part of the Team, so he is unable to join his own Team, unless the Product is marked Incompatible. In this case, the Product will not be fully conform with the Scrum rules.
+
+
Team
+
The Team is the person, or group of persons who actually work on the Product.
+
+
Scrum Master
+
A dedicated member of the Team, who does most of the administrative tasks here on OpenScrum.org, and does the communication between the Product Owner and the Team. He can be, and usually is a member of the Team.
+
+
Events
+
+
Spring Planning
+
+
+
+
+
+
Daily Scrum
+
+
+
Sprint Review
+
+
+
Sprint Retrospective
+
+
+
Objects
+
+
Product
+
The Product is something that can be developed incrementally. Most of the time it will be a software. Each Product has a Product Owner, an Idea Pool, and at least one Team.
+
+
Idea Pool
+
+
+
Idea
+
+
+
Product Backlog
+
+
+
User Story
+
A User Story is what the name suggests: a story, written by the possible users of your Product. It should be short, while expressing the idea as briefly as possible.
+
Want to see the User Stories written during the creation of this site? Check our User Stories page!
These are the User Stories that inspired us during the creation of the site.
+
+
As the Site Owner...
+
+
... I want unregistered users to access the information pages and public Products only
+
... I can decide if I want to allow anyone to register
+
+
+
As a Registered User...
+
+
... I am able to log in to the site using my chosen username and password
+
+
+
As a Product Owner...
+
+
... I can register my company providing a contact e-mail address, and optionally uploading a brief description of it
+
... I can create a new Product on behalf of my company
+
... I can create advertisement about my product to find developers for my Team
+
... I can invite developers to my Team
+
... I can choose a possible Scrum Master from my Team
+
... I can set who can add items to my Product's Idea Pool: me, the Team, or anyone
+
... I can see the difficulty or development time estimated by the Team
+
... I can promote one of the Team members to Scrum Master
+
... I can see if my Product has an active Sprint
+
+
+
As a Team Member...
+
+
... I can vote with a plus or minus on the chosen Scrum Master
+
... I can estimate the difficulty or required time for each item in the Idea Pool
+
... I can put a positive or negative vote on the promoted Scrum Master. If enough positive votes are gathered, the promoted member will become the Scrum Master. If enough negtive votes are gathered, the selected person will automatically be demoted, and the Product Owner has to promote again
+
+
+
As a Scrum Master...
+
+
... I can enable or disable Product Owner access to sprint details
+
+
+
As a Product Owner or Team Member...
+
+
... as a possible Product Owner or Team member I can register myself by choosing a username and password, providing a contact e-mail address, and optionally uploding my CV with references and some details about myself
+• as a Product Owner or Team member I can vote with a plus or a minus on the Idea Pool items depending on the Product's settings
+
+
+
As a Product Owner, Team Member or regular Registered User...
+
+
... I can add items to the Product's Idea Pool depending on the Product's settings
+
... I can add my ideas to a Product's Idea Pool
+
+
+
Unsorted and needs-to-be-revised items
+
+
as a team member, I can see the backlog of each products, and can vote for the difficulty of each story
+
as a product owner or customer, I can see the idea pool, and can accept or decline the ideas in them. If I accept them, they automatically get into the product backlog
+
as a product owner or customer, I can define a business value for each item in the product backlog, thus accepting them from my side
+
as a team member, I can vote for the difficulty of each user story in the product backlog or the idea pool with an optional reason, thus accepting them from my side
+
as a product owner, I can import tickets from ticketing systems. Bugs get into the product backlog, feature requests go to the idea pool
+
as a product owner, I can start a new sprint for my product
+
as a team member, I can help the product owner in creating a new speint, by dividing the user stories into tasks, predicting an hour requirements for each one
+
as a product owner or customer, I can edit user stories with high difficulty, so it breaks into smaller tasks, or I clear some things
+
as a team, we can agree on how we will solve a task, and we can add and modify these details to an open task anytime
+
as the scrum master, product owner, and optionally as the customer, I can see statistics and charts about my ongoing sprint
+
+{% endblock body %}
diff --git a/web/favicon.ico b/web/favicon.ico
index 8648036..95b77e7 100644
Binary files a/web/favicon.ico and b/web/favicon.ico differ
diff --git a/web/images/favicon.png b/web/images/favicon.png
new file mode 100644
index 0000000..d1b4b1e
Binary files /dev/null and b/web/images/favicon.png differ
diff --git a/web/images/logo.png b/web/images/logo.png
new file mode 100644
index 0000000..00a3be2
Binary files /dev/null and b/web/images/logo.png differ
diff --git a/web/skins/default/css/mobile.css b/web/skins/default/css/mobile.css
new file mode 100644
index 0000000..8a2dc02
--- /dev/null
+++ b/web/skins/default/css/mobile.css
@@ -0,0 +1,3 @@
+body {
+ background-color: #ff0;
+}
 }}){kind=logo}