You are previewing PHP Team Development.
O'Reilly logo
PHP Team Development

Book Description

Easy and effective team work using MVC, agile development, source control, testing, bug tracking, and more

  • Work more effectively as a team by breaking up complex PHP projects into manageable sub-parts

  • Develop code that is much easier to maintain with source control, agile principles, and project tracking

  • Apply techniques related to process models, collaboration among team members, and continuous long-term improvement

  • A precise guide with examples to illustrate practical benefits

In Detail

Given the nature of the business environment today, organizations that want to build value-added enterprise PHP applications need a team of PHP people rather than an individual. You've got a team! What next? Customizing such applications to meet with organizational objectives and maintaining these applications over time can be quite a tedious task for your team with so many people involved.

In this book, you will explore how you can break up complex PHP projects into simple sub-parts that multiple team members can work on. The book highlights the use of the MVC pattern for separating concerns in the application and agile principles to deliver code that works. You will learn to blend the simplicity and power of PHP with evolving software engineering principles and tools to easily develop code that is easy to maintain. With this book in hand, you know how to avoid getting muddled up while working in a team and achieve success on your project with effective team work.

Organizations choose PHP as the preferred language for complex web applications because it is battle tested, hardened over time, and proven to work. Thus, chances of the software project you are involved with being PHP-based, are very high. Soon, you will need to explore the technical as well as non-technical aspects that are important to achieve success in PHP team projects of this kind. This book starts by explaining the need for teams working on complex software projects. You learn how you can divide the complexity of PHP projects with the help of the MVC pattern and the use of frameworks. It then discusses the need for a process and how you can choose the right process. It teaches you how to use agile principles to deliver working software for customers, and how to make sure that the team collaborates effectively. Towards the end, the book emphasizes continuous improvement in process and product as well as the people involved. You learn how to ensure that your team is open to change and user feedback, and has the right mindset about quality and other project-related aspects.

Table of Contents

  1. PHP Team Development
  2. Credits
  3. About the Author
  4. About the Reviewers
  5. Preface
    1. What this book covers
    2. What you need for this book
    3. Who this book is for
    4. Conventions
    5. Reader feedback
    6. Customer support
      1. Errata
      2. Piracy
      3. Questions
  6. 1. Software is Complex
    1. Need for teams
    2. Software engineering principles to help
      1. Use a process
      2. Divide and conquer
        1. Guarantee reuse
        2. Guarantee integration
        3. Prevent regression
      3. Vertical versus horizontal division
      4. Continuous integration
      5. Patterns as solutions
      6. Process for success
    3. Tools
      1. Source code control
      2. Continuous builds
      3. Issue tracking
      4. Communication
    4. Summary
  7. 2. MVC and Software Teams
    1. Software design patterns
    2. MVC pattern
      1. Intent
      2. Motivation
      3. Solution
        1. Model
        2. View
        3. Controller
      4. How MVC can help
        1. MVC helps with change
    3. Implementing MVC with a team
      1. Aspects of the presentation layer (view)
      2. The overall team distribution
    4. Integration challenges
    5. Summary
  8. 3. Dealing with Complexity
    1. Frameworks to simplify complexity
      1. How can frameworks help?
      2. Expectations from frameworks
        1. Simplicity
        2. Size of the framework
        3. Performance
        4. Security
        5. Separate HTML from PHP
        6. AJAX support
        7. No restrictions
        8. Object-oriented versus functional
        9. Code quality of the project
        10. Enforce best practices
        11. Configuration needs
        12. Internationalization
        13. Documentation
        14. Community
        15. Commercial support
        16. License
        17. Vendor locking
        18. Availability with hosting
        19. Some more points to ponder
      3. Team success with frameworks
      4. Technical feasibility study of the framework
      5. PHP Frameworks
        1. Limb
        2. phpDrone
        3. ZNF
        4. ATK
        5. Akelos
        6. CakePHP
        7. CodeIgniter
        8. Zend Framework
        9. PHP Work
        10. Symfony
    2. KISS—beyond frameworks
      1. Beyond frameworks
      2. People are complex
        1. Avoid NIH
      3. Innovation
      4. Embrace change
      5. Simplicity is a mindset
    3. Summary
  9. 4. The Process Matters
    1. Process and product
    2. Ignoring the process
    3. Process must be respected
    4. From no process to some process
    5. Process helps not hinder
    6. Simple process for PHP projects
      1. User requirements
      2. Modeling what the users want
        1. Data modeling
        2. Business modeling
      3. User activity analysis
      4. Designs and implementing the data layer
      5. Designs and implementing the business layer
      6. Design and implementation of the user interface
    7. Summary
  10. 5. Agile Works Best
    1. Introducing agile philosophy
      1. Agile values
      2. Agile principles
      3. Individuals and interactions
      4. Working software over comprehensive documentation
      5. Customer collaboration
      6. Responding to change
      7. Customizing agile to our needs
    2. Common fears for developers
      1. Producing the wrong product
      2. Product of inferior quality
      3. Getting late to complete the project
      4. Too much work in too little time
    3. Traits of agile team members
      1. Competence
      2. Common focus
      3. Collaboration
      4. Decision-making ability
      5. Fuzzy-problem solving ability
      6. Mutual trust and respect
    4. What is agility
      1. Characteristics of an agile process
      2. Principles of agility
    5. Extreme Programming (XP)
      1. XP planning
      2. XP design
      3. XP coding
      4. XP testing
    6. Advantages of agile development process
    7. Team agility
    8. Agile process models
      1. Adaptive Software Development
      2. Dynamic Systems Development Method
        1. Dynamic Systems Development Method's life cycle
      3. Scrum
        1. Backlog
        2. Sprints
        3. Scrum meetings
        4. Demos
      4. Feature Driven Development
      5. Agile Modeling
    9. Agile for the PHP team
      1. Pair programming
      2. Sustainable working style
      3. Information-driven workspace
      4. Fixing the process
      5. Sitting together
      6. Ubiquitous language
      7. Stand-up meetings
      8. Demonstrate the iteration outcome
    10. Summary
  11. 6. Ways of Collaboration
      1. Team work is challenging
        1. Team members make assumptions
      2. Making integration possible
    1. Source control
    2. Bug control
    3. Configuration management
    4. Tools for communication and collaboration
      1. Tracking tools
    5. Summary
  12. 7. Continuous Improvement
    1. Dealing with change in PHP applications
    2. Ensuring process effectiveness
      1. Ensure you are improving
    3. Evolving PHP applications
    4. People development
    5. Teams and success
      1. Managing the team
      2. Leadership
      3. Quality focus
      4. Constant monitoring
      5. The team is human
    6. Summary