This document discusses Eugene Veselov's professional experience in project management, software development, and business process optimization over 7+ years. It also provides summaries of the lifecycle stages a software feature may go through, including genesis, adolescence, maturity, and death. Risks associated with internal features and integrating third party systems are outlined as well.

1. Eugene Veselov, veselov@ua.fm
http://ua.linkedin.com/in/eugeneveselov

2.  Goal : to make the World better :-)
Results and team oriented Project/Program/Resource Manager
with rich experience in various fields and platform includes
System Analysis, Design and Application Development.
Professional Profile
7+ years experience in project management.
1+ years successful experience in crisis management
2 years in general management
Business process optimization experience
Involved in all phases of software development lifecycle.
Worked at Magento (an Ebay company), Softserve, Softline, Ciklum

4.  During Genesis stage an idea is turned into the working
software
 When the feature is firstly released there are many things to
do to have the feature used by the customers: observe
possible defects, train your support people, perform right
marketing, and obtain customers feedback. We call this stage
Adolescence.
 Mature feature is a feature that exists in the product for long
time and is well knows by the customers. However maturity
doesn’t mean that the feature isn’t being changed according to
marked demands.
 Normal death for the feature is its termination due to the end
of the parent product life

5. • Extended genesis
Adolescence • Age-related
• Infant death changes
• Adoption to the • Age-related-death
• Transition to maturity
adolescence • Normal death
• Abnormal
termination
Genesis Maturity

6.  Extended genesis – performed analysis during
this phase shows that more than planned effort for
the implementation are needed or there are other
reasons (like business / marketing etc) to put off
the feature until next release of the product
 Infant death – after having done preliminary
analysis it is obvious that the feature isn’t needed
for the product or the company can’t afford its
development.
 Transition to adolescence – the feature grows up
to the next level of maturity, usually this means
assembling the feature into the product

7.  Adoption to the mature life – on this step
we fit the feature and all relevant materials to
the real market demands
 Abnormal feature termination –
comparatively rare case when it is urgently
needed to remove the feature from the
product (i.e. because of dangerous
vulnerability)
 Transition to the mature stage

8.  Age-related changes – changes which are
caused by market demands, competitor activities,
analysis of customer experience or feedback and
etc.
 Age-related-death – extracting the feature from
the scope of the current product when the feature
becomes obsolete. (Example giving up support of
integration with a 3rd part component which is not
supported any more by its vendor)
 Normal death – death due to the end of parent’s
product life

9. Internal feature – means that idea of the
feature comes from the inside
many fathers – means that there are too
 Too
many contributors and no rules regarding
management of their efforts
 Change requests anytime – having team
inside mother company is very often a flag for
management to produce more change
requests and avoid standard development
processes

10. Integration with 3rd party system/component – means we have to
integrate our product with another product inside|/outside the
company. Often idea and product management comes from outside
the company
 Program management absence/ Conflict of interests – I hope I
haven’t to comment this
 Interface /API changes at uncomfortable time – When having an
integration with a 3rd party company product we have to keep in mind
that that can give up supporting their product or release a new
version at a time which is suitable for them not for you
 3rd party system temporal unavailability - you could face up 3rd party
component unavailability at any time, usually during YOUR release.
 Low level of documentation – No Comments there

11. Questions ?
 Eugene Veselov, veselov@ua.fm
 http://ua.linkedin.com/in/eugeneveselov