Hello!
Nicolas Ivulic
Central, New Jersey
As a Project Manager with over 19 years of experience, I have built and directed many cohesive teams of internal and external personnel. Alongside these teams, I have effectively executed projects within agencies and for B2B/B2C companies thereby achieving reliable and stable web applications.
Software skills
-
10 years -
10+ years -
6 years -
3 years -
3 years -
8 years -
10+ years -
8+ years -
4 years -
10+ years -
9 years -
3 years -
4 years -
7 years -
3 years -
2 years -
5 years -
1 years -
10+ years -
4 years -
4 years -
4 years -
4 years -
3 years -
7 years -
7 years -
3 years -
10+ years -
4 years -
7 years -
4 years -
4 years -
9 years -
8 years -
2 years -
10+ years -
8 years -
10 years -
8 years -
13 years -
3 years -
5 years -
3 years -
5 years -
10 years -
2 years -
2 years -
2 years
Sprint Candence
In “Managed Services” environments with Agile or Scrum methodologies, it’s very important to have well-structured release cadence because it not only pushes teams to release on schedule it also keeps ROI and traction under control, rather than only deploying when the full project is “done”. It’s easier to monitor and report work in pieces in order to have more visibility on change requests or dependencies. In general, it’s best to have three-week sprint schedule with a two-week release cycle.
Project Timeline
For every project, especially “implementation type” projects, my preference is to lay the project out in a Gantt style chart. This way it is easier to not only set stakeholders’ expectations but also identify risks, both of which are a critical part of every project. Once expectations are set and risks are identified, it creates a sense of urgency from “the other side” which assures dependencies are followed up on in calls and tickets.
Backlog Ticket Flow
Each team member has a responsibility to ensure that tickets are being advanced and assigned appropriately. The following backlog workflow allows a bird’s eye overview of everything while also keeping everything in order. First, a ticket starts at the bottom in the “Backlog” which is where the “New” and “On Hold” tickets are. Second, the ticket is moved up to “Grooming” meaning it needs to be worked on. The BA then grooms the ticket and formats it. Third, the ticket is moved to “Estimated” where the TL analyzes it, add comments, and provides an estimate. Then if the ticket is approved, it is added to next Sprint.
Replication Process
Sandboxes
Developers can have their own version of code
Each sandbox can have its own test data
Development
Testing of new code builds
Test data - replicated from Staging
Pre-production code build
Staging
Preview of content before it goes live
Merchandising
Live data - before replicated to Production
Production code build
Production
Live data - products, content, customers, orders
Production code build
Ticket Format
Get connected
Your message has been sent
Thanks for checking out my site and interest. I will get back to you within 6 hours.
Name:
Email:
Phone: