The Key steps for a successful Software Project Management | Part 1

The Key steps for a successful Software Project Management | Part 1

As part of our software development pathway and the Level 6 “New Zealand Diploma in Software Development”, Techtorium is implementing a Capstone Project using methodologies and best practices of professional project management for all our software students. The aim – To prepare students for their first roles in the New Zealand IT industry. The Capstone Project ensures that our learners develop the overall professional skills required to be successful in their careers. Combing their technical ability with their leadership and communication skills will improve the graduate’s employment opportunities.

Using Agile software development methodology, each software team has until November to complete their projects. This tight deadline leaves little room for error so their Techtorium mentors provided some guidelines to produce a real-world, functional software product:

1.Why Using Agile methodology?

The Manifesto for Agile Software Development is based on twelve principles:

  1. Customer satisfaction by early and continuous delivery of valuable software
  2. Welcome changing requirements, even in late development
  3. Working software is delivered frequently (weeks rather than months)
  4. Close, daily cooperation between business people and developers
  5. Projects are built around motivated individuals, who should be trusted
  6. Face-to-face conversation is the best form of communication (co-location)
  7. Working software is the primary measure of progress
  8. Sustainable development, able to maintain a constant pace
  9. Continuous attention to technical excellence and good design
  10. Simplicity—the art of maximizing the amount of work not done—is essential
  11. Best architectures, requirements, and designs emerge from self-organizing teams
  12. Regularly, the team reflects on how to become more effective, and adjusts accordingly


2.Structure your Team

  • The Product Owner: This person represents the stakeholders and has the vision of the final product. The development team will refer to the Product Owner to validate or cancel features. Typically, the Product Owner could be an entrepreneur, a member of the marketing team or the business analyst of a larger company but they do not code.
    In the context of Techtorium Capstone Project, our teams of students were asked to approach potential Product Owners in need of a software, website, web or mobile app. Their Product Owners range from being a relative, a charity or a sport club.
  • The Scrum Master: Scrum is a process framework part of the Agile software development methodology. Its principles rely on transparency, inspection and adaptation. The Scrum Master is the leader of the team and has an overview of the project and is guiding the team work. The Scrum Master may or may not have code depending on the software development team size
    Our Techtorium Capstone teams are only composed of 7 members; therefore, the Scrum Master is a year two Software student and will also code. This gives a fantastic opportunity for our soon-to-be graduates to hone their leadership skills.
  • Lead Developer: The most experienced developer will lead the development team and supporting the junior developers. Together they will code, test and debug repeatedly.

Want to study Software Development?

Techtorium offers Software Development Courses:

Our Entry course:
Level 5 New Zealand Diploma in Information Systems 

which pathways to the second year of
Level 6 New Zealand Diploma in Software Development 


Stay tuned for the Part 2!