Confirmed users
1,021
edits
Services/Meetings/2012-04-03: Difference between revisions
Jump to navigation
Jump to search
→Kilamanjaro
| Line 144: | Line 144: | ||
= Marketing = | = Marketing = | ||
= Roundtable = | = Roundtable = | ||
== | == Kilimanjaro == | ||
<i>Summary of discussion</i> | |||
There is some concern that with the use of trains and the constant flow of features, that there is a lack of "impact" for new releases. This can be compounded by the fact that there may be little coordination between teams when rolling out features. Kilimanjaro is an attempt to focus product and development on key features that can be turned into major, marketable items. Kilimanjaro allows us to voice to ourselves and the community what we're working on and why it matters. | |||
In order to meet that, we need to make sure that the elements of Sagrada (and all other projects) are properly productized. A goal should be that in 6 months time, we can get a fully understood and clearly spec'd project like Apps in the Cloud and be able to provide a set of tools that will allow that project to be viable to an audience of 10K within weeks. (With the ability to scale higher later, once hardware and other ops elements are made available.) | |||
The work we need to do now is to think about our projects as products and make sure that other folks who are unfamiliar with them have very low bars in order to use them effectively. | |||
== 2012Q1 Goals == | == 2012Q1 Goals == | ||
== 2012Q2 Goals == | == 2012Q2 Goals == | ||