“Greg Krupkin is an innovative and passionate leader who delivers mission critical value to his customers with excellence and the highest degree of professionalism. Whether brainstorming, complex solutioning, managing through uncertain environments, or delivering outstanding services, Greg leads teams with talented precision and an impactful customer focus. Greg is an awesome collaborative leader, who can take any team to the next level of excellence.”
Gregory Krupkin
Owings Mills, Maryland, United States
3K followers
500+ connections
About
please review recommendations from colleagues in the "Recommendation" section down in…
Contributions
-
What is the best way to develop and maintain project management documentation for engineering projects?
just remember your project output will match the communication on your project. Good collaboration and communication must include the investment of time. Time spent together. Talking, meeting, working together. Being together. In Person if at all possible. Any attempts to use tools or process to enhance collaboration and communication will fail. Just remember, Conway's Law. :)
-
What is the best way to develop and maintain project management documentation for engineering projects?
use whatever the development team is using. I can't stress this enough. Yes, you will need to Learn new tools. At Redhat we built and collaborated on plenty of documents using Git and it worked just fine. Do not use Sharepoint. :)
-
What is the best way to develop and maintain project management documentation for engineering projects?
In my experience the successful high performing teams all work closely together and the collaboration and communication usually matches the output of documentation. Some thoughts; 1) only use the tools the dev team is using. Store and version documentation in Git or whatever the team is using for VCS. If you've ever tried to get a developer to go look in SharePoint, you will know why I suggest this. Yes the PM will have to learn a new tool, so what. Developers learn new tools all the time. 2) become part of the team. Treat your documentation like part of the project. If you follow agile, make some component of the documentation a deliverable and part of the sprint. Documentation is not different than the output of the engineering project.
Experience
Education
Licenses & Certifications
Projects
-
AWS cloud migration for CSRA
-
Led migration of business applications to AWS to execute a corporate split of commercial and federal business into 2 distinct entities. Project was completed in 3 months against overwhelming odds.
Languages
-
English
Native or bilingual proficiency
-
Russian
Native or bilingual proficiency
Recommendations received
13 people have recommended Gregory
Join now to viewOther similar profiles
Explore collaborative articles
We’re unlocking community knowledge in a new way. Experts add insights directly into each article, started with the help of AI.
Explore More