Throughout my career, I have developed skills using multiple methods and technologies in all aspects of software architecting and development. In this time, I have worked with company presidents, elected officials, a variety of co-workers and a multitude of people who have used the solutions I have designed and implemented. I have tried my best to create useful things and communicate with everyone I have worked with in a clear and meaningful way.During my career, I have managed projects with multiple contributors in varying roles; including co-workers, managers, department heads, company heads, elected officials, the public, vendors, and contractors. I have coordinated efforts by members of these diverse groups toward common goals and directed activities toward specific goals and milestones.As a project manager, I exercise the fundamental responsibility to make sure all the steps from inception to maintenance occur as successfully as they can. Much of my experience in project management has been in addition to me acting as the business analyst, system architect, developer, trainer, and maintainer on projects from start to finish. Through all of that, it has been my responsibility to keep the project on track, communicate project status with all involved parties at multiple levels of responsibility and authority, and to solve the problems with enough flexibility to adapt to changing conditions at every step.I am experienced in process analysis, including functional analysis of existing process tools and components that must be incorporated, supplemented, or replaced. I can take the business needs identified by the analysis and direct the identification and examination of the functional needs that are necessitated to successfully solve the problem. All of this must be documented and organized to be communicated to all interested parties, including users, stakeholders, management, decision making authorities, customers, vendors, and the public.The functional requirements coalesce into design elements for front end, back end, and at least an educated concept of the middleware components needed to develop a system. One lesson I have learned the hard way has made me believe requirements must be treated as a fixed point based on an agreement between the development team and the project stakeholders to keep scope creep in check. At the same time, I believe the system design must be viewed and managed as fluid enough to adapt to the implementation needs discovered as development progresses.