Nowadays, when everyone tries to maximize results while reducing the resources allocated for the project, it is a huge advantage to have an on hand methodology that can help you follow this path. You would probably agree that it is important to realize what the main goal you are willing to deliver is at the beginning of each project. Getting the whole picture of what is involved in the process of planning and delivering the project to the customer will help you stick to your primary goal- a project fulfilling its purpose. To ensure the success of your project, Kentico professionals developed a methodology that describes the project development cycle for Kentico CMS. Furthermore, it defines the various stages of development and points out important areas which specifically deserve your attention. The presentation will bring insight on the Deliver Now! Methodology. You will learn how the methodology can help you maximize the potential of Kentico CMS to make your project nothing else but a great success.

1. Kentico CMS Deliver Now! Methodology
Karol Jarkovsky (karolj@kentico.com)
Consultant, Kentico Software s.r.o.

2. Agenda
Project Management Facts
1/15
Project Failure
Project Success
Kentico Deliver Now!
Methodology Details

3. Project Management Facts
2/15
Initial planning
1 hour planning =
10 hours doing
Fail to plan
Impossible deadline
Murphy’s laws
Wrong decisions
Failure surprise
Job changing

4. Project Failure Causes
3/15
Ignoring viewing habits
of the customers
Fail to hit the market
Fail to study
competition
Quality of design
Lack of project plan
Building the web
project from scratch
Failing to consider
ongoing costs
Not delivering value for
money
Not meeting goals,
requirements, scope

5. Project Failure Statistics
4/15
Computer Associates
(UK & Ireland)
• 1/3 of all IT projects 10% to
20% over budget
Standish Group
CHAOS Report
• 46% of IT projects are challenged,
• People are more prepared to cancel projects,
Causes of failure according study:
• Incomplete Requirements - 13,1%,
• Lack of User Involvement - 12,4%,
• Changing Requirements & Spec - 8,7%,
• Lack of Planning - 8.1%,
The Boston Group
• One-in-four considered failure,
• 44% considered challenged

6. Project Success
5/15
Risk
Management
Outcome
Realization
Evaluation &
Closure
Resource
Management
Planning
& Scoping
Quality
Management
Governance
1

7. Kentico Deliver Now!
6/15
Ensure project success
Deliver project on time and within budget
Build reliable and maintainable project
Reduce project risk
Accomplish more work - reduce learning requirements
Know amount of work involved - ensure estimate resources
Know what to expect - identify skill set required

8. Project Failure Causes
7/15
Ignoring viewing habits
of the customers
Fail to hit the market
Fail to study
competition
Quality of design
Lack of project plan
Building the web
project from scratch
Failing to consider
ongoing costs
Not delivering value for
money
Not meeting goals,
requirements, scope

9. Requirements
Analysis &
Design
Development
Testing
Deployment
Website
Evaluation
Kentico
Deliver Now!
Methodology
Methodology Details
8/15

10. • Goals, weak or blind spots to be banished,
• Scalability and content sharing,
• Type of content,
• Security concerns,
• Web standards (accessibility and coding),
• The 3rd party applications and technologies,
• Content life-cycle,
• Multilingual support,
• Availability
Methodology Details
9/15
Requirements

11. Methodology Details
10/15
• Content tree architecture & design,
• URLs format and SEO impact,
• Navigation and Site map,
• Membership and Restricted areas,
• Website performance,
• Multilingual sites,
• Organizing media files,
• User contributions,
• Page templates
Analysis&Design

12. Methodology Details
11/15

13. Methodology Details
12/15
• Resources, development team roles,
• Team development environment setup,
• Design template processing,
• Page template inheritance,
• Static HTML to re-usable transformation,
•Custom functionality- doc types, modules, web parts,
• Security- authentication, live site, security threats approach,
• UI Personalization,
•Performance optimization- debugging, caching, output filters
Development

14. Methodology Details
13/15
• Functional testing,
• Site validation,
• Load testing- response time verification, use cases verification
Testing

15. Methodology Details
14/15
• Deployment options,
• Medium trust environment concerns,
• Content staging,
• Web farm support
Deployment

16. Questions
15/15

17. Questions