Les collègues qui font de la gestion de projet régulièrement avec tout le formalisme, c'est quoi le logiciel open-source de gestion de projet qui va faire pleurer MS Project tellement il est beau, efficace et parfait ? #opensource#projectmanagement
@AAMfP@jenkstom thanks for telling me about Logseq, it wasn't on my radar! but looking over their website I saw it involved coding in its usage, to make "queries", and it gave me pause. did I understand that correctly?
#TechnicalWriting#ProjectManagement#SoftwareDocumentation: "Why is it essential to establish a clear documentation workflow? How can developers, project managers (PMs), and techwriters work closely together without being a bottleneck? You may be familiar with these issues or looking for a better solution to make the customer and internal (in-house) documentation workflows more efficient.
The development of our workflow spanned about 4 to 5 years, during which we achieved smaller goals and had to adjust our plans along the way.
The actual implementation took 3 to 6 months, but this is surely not its final form. Our work environment and industry are always changing, so we need to keep experimenting to adapt quickly. Now, after reflecting on our progress and making adjustments, we've brought everything together in a more organized way. Even though we had the components ready, it still took a lot of effort to complete the whole picture."
#TechnicalWriting#ProjectManagement#SoftwareDocumentation: "Why is it essential to establish a clear documentation workflow? How can developers, project managers (PMs), and techwriters work closely together without being a bottleneck? You may be familiar with these issues or looking for a better solution to make the customer and internal (in-house) documentation workflows more efficient.
The development of our workflow spanned about 4 to 5 years, during which we achieved smaller goals and had to adjust our plans along the way.
The actual implementation took 3 to 6 months, but this is surely not its final form. Our work environment and industry are always changing, so we need to keep experimenting to adapt quickly. Now, after reflecting on our progress and making adjustments, we've brought everything together in a more organized way. Even though we had the components ready, it still took a lot of effort to complete the whole picture."
🤩 Exciting announcement: #Favorite#projects are (almost) here! With our release of OpenProject 14.1 next week, users will be able to add projects to their ⭐ favorites.
We recently released OpenProject 14.0.1!
The release contains several bug fixes and we recommend updating. Thanks again to our amazing Community for reporting bugs and helping us with fixes! 💙
Read more: https://openproject.org/docs/release-notes/14-0-1/
Are you thinking about switching from #Jira to #OpenProject? 🔄 Then you might want to read the story of 'Was hab' ich?', a German NGO in the #healthcare sector.
How did they migrate from Jira to OpenProject? And how well did the employees cope with this change?
"This is another variation of the High-Tech Illusion: the belief that software developers do easily automated work. Their principal work is human communication to organize the user's expressions of needs into formal procedure. That work will be necessary no matter how we change the life cycle."
BTW, we went "the hard way" and picked the sourcehut todo service as a bug tracker and project management tool for RDE, Ares, Arei and neighboring projects.
It's very bare-bone, but we could implement cross-project milestones via labels, it's already have basic filtering and searching and integrates nicely with email and git.
Will be developing the rest of the functionality as we go. Probably via API or by upstreaming patches to sourcehut.
We've just released #OpenProject 14.0! 🚀🎉 We are introducing a consistent progress reporting across work package hierarchies.
Among other updates, project attributes are now listed on the project overview page. The Meetings module has been updated and there have been improvements on file storages.
How do i explain to someone that daily standups are for devs to just keep up to date with whats going on and where they need help
And not a ridged meeting for documenting work done yesturday, todays work and blockers, so the scrum master can report back to upermanagement so they can audit and micromanage the team.
its not that i hate scrum, its i hate people that dont understand it and try to follow the letter of the law vs the spirit.