TZM Re-design—The Phoenix Project
- 1 Project Adminstration
- 2 Introduction to The Phoenix Project—TZM 2.0
- 3 Want to get in on it?
- 4 Project Current Status. What's Happening now?
- 5 Project Definition—First Milestone
- 6 Final Technical Specifications Milestone Two Mid August
- 7 Development & Programming
- 8 Deployment
- 9 Maintenance
- 10 Undivided tasks-Ling. Team
- 11 Original Project Source
Introduction to The Phoenix Project—TZM 2.0
--Boldhawk 01:16, 19 October 2011 (UTC)—The Philosophy is still the same; events and personnel may have changed, and the latest information can now be located at the Atrium site, where the Phoenix Project has been operating. Much has been updated, as we have progressed. The information in this wiki, therefore is remaining here for historical reference. All the development locations are the same, except the function of this wiki has changed.
Working dev location: This wiki is a documentation Repository. By popular demand, the Atrium Site is preferred for the collaboration on the development stage; thus, you may find it easier to chat and contribute ideas at that site: Atrium
Actual Programming site: When technical details have been finalized, and the project is broken down into programmable pieces, the PM under redline is used: Phoenix Project
The Phoenix Project was first posted in the International Forum, in a post written by Cluster, the international Web Master System Administrator, and edited by Federico , asking the public for suggestions, and prescribing the form of presentation: Designing TZM Web Site
Given the necessary background provided by the link, which is also the last article of this Page, under the heading: Original Source, this is the Project Management activity for the Phoenix Project, and this is the starting page for the project.
That provided a general description of the direction of the project. However, part of the project itself involves a more detailed definition of its scope. That would have to come from the understanding the needs of all stake holders, which would be generally spelled out in the "Brainstorming" section.
From the brainstorming section, we begin to glean a better picture of the overall project, which will be refined as the project moves forward. As of the end of June, 2011, the brainstorming information yields the following summary:
To create an all encompassing web site, with which will allow maximum free flow of information, easy to find, with features to accommodate a wide variety of projects and activities generated by teams and chapters. Technically, it points to the use of one or more platforms, with the ability to converged on the same web pages. Drupal and CMS are amongst the underlying systems. Open Atrium is but a small portion taking advantage of the Drupal facilities. Because of the wide variety of sources, and locations of ready or partially ready software and modules, two other key pieces of software will be considered: Web Site Integration and Content Management systems. The first, can gather information from any system anywhere, and make it appear in a web site, and the second, can manage the arrangement of the information thus gathered, all in a seamless system. This further allows user content management control, where he can, from a long list of components, create his own front page which contains what he needs and wants. Further analysis through the compilation phase of the project, will flesh out more precise elements.
Project Current Status. What's Happening now?
Final Technical Specifications Milestone Two Mid August
The completion of this milestone is achieve through the following actions:
- * 6.1 Project Definition Brainstorming—All Ideas Repository
- * 6.2 Submissions
- * 6.3 Requirement Compilations
This is the final date for screen shots and sample applications.
Person Responsible Collaborated supervised by David Zwolski
Project Definition Brainstorming—All Ideas Repository
From the above several sources, and whatever other sources are available, a compilation is made, from which a detail definition of the work to be done is developed. This group is also responsible for interfacing with Developer side, and server side activities to ensure their requirements are also included in the requirements compilation.
An important responsibility of this activity is to divide the compilations into related items and section suitable for developer assignments.
This group will also be required to set up various rules and parameters on templates, and web module presentation and language to be used on the web.
From the above compilations information, people can make their template submissions and screen shots. (See appropriate submission Section)
Comments and discussion here> Compilation Master and discussion
Person Responsible ____________________
The persons making the decision on how to divide the requirements in programmable morsels should be well versed in many systems, languages, platforms, etc., as they must make decisions which affect whether something can be done easily. A wrong choice may not make the task impossible, but it can make it difficult if assigned to a segment wherein it can't be done easily.
Person Responsible: _______________
After each testing plan for each of the applications or features have been passed without a hitch, the project is ready for Deployment. Sys Admin should write up a plan for such deployment, so in the event of problems, it can be rolled back, and fixed.
Post deployment, and continuing maintenance.
Undivided tasks-Ling. Team
Original Project Source
The detailed information below is to present a post in the International Forum, to a post written by Cluster, the international WebMaster System Administrator, asking the public for suggestions, and prescribing the form of presentation. This section is dedicated to Developer's contribution, and it can be as technical, as necessary. The section, "Users' and General Public Requirement" In the Users' Section, is for general public use; non-technical personnel.
It is for reference only. To follow the development process return to the main page: Phoenix Project