Please log in to watch this conference skillscast.
Software Architecture and Software Project Management both areas are very close to my heart. Both have equivalent importance for the success of a software project and product and they both have interconnecting goals too. As an integral part of Software Architecture, goal would be to have a successful design, it’s proper implementation and sustainability for a longer period of time. As an integral part of Software Project Management, though the area of operation would differ, goal would always be a successful completion and delivery of the project / product. Scope, Time and Quality remains a common factor to both of them. However, Software Architecture goes beyond to just the completion of software development. In ideal situation, Software Architect and Project Manager are 2 different roles which are good to have in a software firm. However often these roles are merged with a new role namely Technical Manager / Solution Architect / Tech Consultant. With my personal experience of being a Manager and wearing a hat of Architect (as and when required), writing design documents for the product and also managing the team schedule, considering both the managerial as well as technical aspects, I would like to share: • How indirectly various important attributes of Software Architecture were implemented. • Challenges that come up when you play both roles. • How important it is for an organization to have both as different roles? Benefits and challenges associated with it. In addition, with this session I will also talk about: What are the aspects of both the areas which would jointly bring out what I would like to call S3 - A Successful and Sustainable Software?
YOU MAY ALSO LIKE: